This alarm indicates that there might be a problem with the connection to the database that contains the administration data for establishing call routes and users. The connection to the database is either disconnecting after a timeout period or is lost. During the connection failure, you cannot perform new administration tasks.
The possible causes include:
The database might not be running.
The connection to the database was lost or is experiencing timeouts between queries.
The user name or password that the system uses may not match the user name or password in the database.
The database process might not be running on the Avaya Breeze® platform instance or is on a different IP address than expected.
Solution
Procedure
Ensure the database process is running on the Avaya Breeze® platform instance by logging on to the Avaya Breeze® platform system and running any of the following commands:
Type statapp -s postgres-db.
The output should be similar to postgres-db 18/ 18 UP.
Type systemctl status postgres.
The output should be similar to:
Active: active (running) since Tue 2017-05-02 09:58:36 MDT …
Main PID: 29514 (postgres)
If none of these conditions are true, type start –s postgres-db.
Ensure there is a connection to the database. Verify that the connection is stable and is not experiencing outages
Ensure that the Avaya Breeze® platform instance is reachable by pinging the Avaya Breeze® platform instance from another machine that is capable of reaching the Avaya Breeze® platform instance.
