The CLI is currently not available on primary CPM
Article ID: 167869
Updated On:
Products
XOS
Issue/Introduction
The CLI is currently not available on primary CPMIn some situations, CLI might be not accessible after login on primary CPM:
Failed to open database
The CLI is currently not available.
sh-2.05a$
Below messages are seen in /var/log/messages:
Jun 28 06:40:01 bdp-0a-scp1 cli: [E] cb_db_open() connection request failed for DB running-config.ErrorMsg = could not connect to server: No such file or directory ^IIs the server running locally and accepting ^Iconnections on Unix domain socket "/tmp/.s.PGSQL.5432"?
Jun 28 06:40:01 bdp-0a-scp1 cli: [A] Failed to connect to database.
Jun 28 06:40:01 bdp-0a-scp1 cli: [F] no database connection
Failed to open database
The CLI is currently not available.
sh-2.05a$
Below messages are seen in /var/log/messages:
Jun 28 06:40:01 bdp-0a-scp1 cli: [E] cb_db_open() connection request failed for DB running-config.ErrorMsg = could not connect to server: No such file or directory ^IIs the server running locally and accepting ^Iconnections on Unix domain socket "/tmp/.s.PGSQL.5432"?
Jun 28 06:40:01 bdp-0a-scp1 cli: [A] Failed to connect to database.
Jun 28 06:40:01 bdp-0a-scp1 cli: [F] no database connection
Resolution
There are two options to resolve this condition:
1 - Restart PostgreSQL database
# service postgresql restart
If it doesn't help, reboot the CPM:
2 - Restart CPM from Linux as root user
# reboot
1 - Restart PostgreSQL database
# service postgresql restart
If it doesn't help, reboot the CPM:
2 - Restart CPM from Linux as root user
# reboot
Workaround
N/AFeedback
Yes
No
Powered by
