Troubleshooting tasks
This table describes the common error messages that are related to Cisco ONP installation and the workarounds:
Warning Message or Error |
Probable Reason for the Error |
Workaround |
---|---|---|
Non-Responsive user interface |
The Server is not reachable. Or The internet connectivity is not stable. |
Check whether cnp and onp_frontend containers are running using this command:
If the containers are not up, Restart Cisco ONP. Or Check whether the internet connectivity is fine and log in to Cisco ONP again. |
PostgresDb container is not starting within stipulated time Exiting. |
Server disk space has exhausted. |
|
After successful installation, not able to log in to Cisco ONP with default username and password (admin/cisco123) |
Check whether any special characters are used in the Cisco ONP database username or password during installation. |
Uninstall and reinstall Cisco ONP. Make sure that only alphanumeric characters are used in the database username or password. |
Cisco ONP keeps on reverting to the login page after logging in. |
Old browser cache may not be cleaned up. |
Clear browser cache, relaunch browser and log in again. |
CONP 5.2 PostgresDB volume (/var/lib/postgresdb_cnp) is not present. Data Migration Not Possible. Exiting CONP installation. Re-try CONP 24.3.1 installation without data migration option. |
PostgresDB is not present. |
Terminate installation using Ctrl+C and reinstall Cisco ONP without data migration option. |
Error response from daemon : This node is not swarm manger. Use "docker swarm init"or "docker swarm join" to connect this node to swarm and try again. |
Server is not in Swarm mode. |
|