Fix the issue related to the systems logs not being shipped to Elasticsearch or GCS archive

Summary

Per the Slack conversation - https://gitlab.slack.com/archives/C02K0JTKAHJ/p1690275509603809 it was identified that there are a few DB servers whose systems logs are not being shipped anywhere (Elastic search or GCS archive).

A known solution is to restart the VMs.

Some of the servers whose system logs are missing are:

  • patroni-main-2004-108-db-gprd.c.gitlab-production.internal
  • patroni-registry-v14-01-db-gprd.c.gitlab-production.internal
  • patroni-registry-v14-02-db-gprd.c.gitlab-production.internal
  • patroni-registry-v14-03-db-gprd.c.gitlab-production.internal

Acceptance criteria

  • Restart the VMs and confirm that the system logs are shipped as expected to Elastic search and GCS archive
    • patroni-main-2004-108-db-gprd.c.gitlab-production.internal
    • patroni-registry-v14-01-db-gprd.c.gitlab-production.internal
    • patroni-registry-v14-02-db-gprd.c.gitlab-production.internal
    • patroni-registry-v14-03-db-gprd.c.gitlab-production.internal
Edited by Biren Shah