The periodic maintenance test of the Postgres database failure might indicate that the Postgres service might not be running.
To troubleshoot the database failure, you must perform the troubleshooting steps for Avaya Breeze® platform and System Manager. You must have root user privileges to perform the troubleshooting steps on System Manager.
Procedure
Perform the following steps for Avaya Breeze® platform:
On the System ManagerHome page, under Elements, select Avaya Breeze® platform.
Select System Tools and Monitoring > Maintenance Tests.
Select the affected Avaya Breeze® platform instance from the Select Target list.
Select the Test Postgres database sanity test.
Click Execute Selected Tests.
If the test passes, clear the alarm. The problem no longer exists, and you do not need to continue with this procedure.
If the test fails, establish an SSH connection to the Avaya Breeze® platform instance using either the craft login (Avaya) or an established customer login.
Run the statapp command to verify the status of postgres-db.
If the status of postgres-db is Down, run the command restart postgres-db and wait for the Postgres service to restart.
If the status of postgres-db is Partially UP, wait for the status to change to Up.
Run the statapp command to verify the status of postgres-db.
Run the Test Postgres database sanity test again.
If the test still fails, reboot the Avaya Breeze® platform server using the Shutdown System > Reboot option on the Avaya Breeze® platform Server Administration page.
Perform the following steps for System Manager:
On the System ManagerHome page, under Elements, select Session Manager.
Select System Tools and Monitoring > Maintenance Tests.
Select System Manager from the Select Target list.
Select the Test Postgres database sanity test.
Click Execute Selected Tests.
If the test passes, clear the alarm. The problem no longer exists, and you do not need to continue with this procedure.
Run the systemctl status postgresql command to verify the Postgres service is running.
If the Postgres service is up, the problem no longer exists and you do not need to continue with this procedure.
If the services is down, run the systemctl restart postgresql command.
Wait for the Postgres service to restart.
Run the systemctl status postgresql command to verify the Postgres service is running.
If the Postgres service is still down, check the available disk space in the /var partition.
