"Cluster details cannot be retrieved. Please check the CMON process status (service cmon status). Also, ensure the dcps.apis token matches the rpc_key in /etc/cmon.cnf." when accessing the Clusters page.
"Unable to connect to 127.0.0.1:9500" on AJAX refresh
Pre-existing cluster is showing with UNKNOWN status.
This occurred after an instance of disk space exhaustion on the controller, which has since been resolved.
- Cmon services are running; No errors in service status output.
- MySQL service is running and I can connect to the cmon and dcps schema as root. Can export both these schemas without an error, so doubt MySQL corruption is the issue.
- Have checked that token in the cmon database matches the rpc_key in /etc/cmon.cnf
- Have checked that the RPC_TOKEN in /var/www/html/clustercontrol/bootstrap.php matches the rpc_key in /etc/cmon.cnf
- Have explicitly set the cmon bind-address to be 127.0.0.1 and the Internal IP of the server. (Per another thread)
- Have checked time an timezone settings to ensure NTP was running correctly. (Per another thread)
Observations of Interest
- Flicking through the Cluster Control webapp shows that there are no Operational Reports or Scheduled Backup jobs despite there being some in the database. Not sure if this is because components aren't working, or if it gets this information from the database directly?
Errors in Logs (Probably unrelated):
- (ERROR) Skip configuration '/etc/cmon.d/cmon_1.cnf', error: Duplicated clusterid (0) in file '/etc/cmon.d/cmon_1.cnf'
- 2020-06-26T06:26:02.636644Z 0 [ERROR] Function 'auth_socket' already exists
- 2020-06-26T06:26:02.636660Z 0 [Warning] Couldn't load plugin named 'auth_socket' with soname 'auth_socket.so'.
- Ubuntu 18.04 LTS
- Controller: 184.108.40.20696
- Frontend: 220.127.116.1176-#1bd5f8
Any advice on things to check would be appreciated; Thanks!
Please sign in to leave a comment.