VxRail: Falha na inicialização dos serviços PSQL do VxRail Manager

Ao tentar acessar o banco de dados PSQL no VxRail Manager, ocorre uma falha ao fazer log-in com o erro:

vxrm:/home/mystic # psql -U postgres mysticmanager
psql: could not connect to server: No such file or directory
        Is the server running locally and accepting
        connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?

Verificando o status do serviço, ele estava inativo:

vxrm:/home/mystic # systemctl -l status postgresql
* postgresql.service - PostgreSQL database server
   Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2019-05-30 07:27:04 UTC; 21min ago
  Process: 1280 ExecStart=/usr/lib/postgresql-init start (code=exited, status=1/FAILURE)

May 30 07:27:03 vxrm systemd[1]: Starting PostgreSQL database server...
May 30 07:27:03 vxrm postgresql-init[1280]: 2019-05-30 07:27:03 GMT [1447]: [1-1] user=,db= FATAL:  could not write lock file "postmaster.pid": No space left on device
May 30 07:27:04 vxrm postgresql-init[1280]: pg_ctl: could not start server
May 30 07:27:04 vxrm postgresql-init[1280]: Examine the log output.
May 30 07:27:04 vxrm systemd[1]: postgresql.service: Control process exited, code=exited status=1
May 30 07:27:04 vxrm systemd[1]: Failed to start PostgreSQL database server.
May 30 07:27:04 vxrm systemd[1]: postgresql.service: Unit entered failed state.
May 30 07:27:04 vxrm systemd[1]: postgresql.service: Failed with result 'exit-code'.

O serviço estava fora do ar, pois não havia mais espaço. Para verificar isso, execute df -h

vxrm:/home/mystic # df -h
Filesystem                  Size  Used Avail Use% Mounted on
devtmpfs                    3.9G     0  3.9G   0% /dev
tmpfs                       3.9G     0  3.9G   0% /dev/shm
tmpfs                       3.9G  8.8M  3.9G   1% /run
tmpfs                       3.9G     0  3.9G   0% /sys/fs/cgroup
/dev/sda3                    16G   16G     0 100% /
/dev/sda1                   124M   35M   84M  30% /boot
/dev/mapper/data_vg-store1  2.0G  3.1M  1.9G   1% /data/store1
/dev/mapper/data_vg-store2   14G   36M   13G   1% /data/store2
tmpfs                       799M     0  799M   0% /run/user/493
tmpfs                       799M     0  799M   0% /run/user/1000

Havia pacotes de log antigos do VxRail armazenados em cache no /tmp/mystic/dc.

• Exclua pacotes de logs antigos do VxRail Manager para liberar espaço. Os pacotes estão localizados em /tmp/mystic/dc
• Reinicie a VM do VxRail Manager para reiniciar todos os serviços com falha