ClusterControl 1.6 -> 1.7 update: HTTP/1.0 500 Internal Server Error
After upgrading from ClusterControl 1.6 to 1.7, every couple of minutes an [HTTP/1.0 500 Internal Server Error] pops up in the upper right hand corner of the dashboard. Has anyone had this issue before, and if yes, how did you correct it?
-
Hi Jmodran,
Can you check the error logs specified here https://support.severalnines.com/hc/en-us/articles/212426183-ClusterControl-Logs-and-enabling-debug.
-
Hi,
Also, can you confirm which PHP version do you have?
$ php -v
And please, try to remove the cache content:
$ rm -f <webroot>/clustercontrol/app/
tmp/cache/models/*
$ rm -f <webroot>/clustercontrol/app/tmp/cache/persistent/*
$ rm -f <webroot>/clustercontrol/app/tmp/cache/views/*
$ rm -f <webroot>/clustercontrol/app/tmp/sessions/* Restart the cmon service and try again:
$ service cmon restart
-
Regarding PHP version: on the ClusterControl server:
$ php -v
PHP 5.3.3 (cli) (built: Mar 22 2017 12:27:09)Ran the 'rm' commands, restarted the 'cmon' service, and now cannot log in: Username or password is incorrect
Regarding the logs: I would like to upload them. Shall I open a ticket now that I cannot log in?
-
Hi Jmodran,
Can you file a new ticket on this please. Kindly do the following that I have noted to you in ticket #5081 i.e.
netstat -tnvlp46and send the log files specified on this post https://support.severalnines.com/hc/en-us/articles/212426183-ClusterControl-Logs-and-enabling-debug.
Thank you.
Please sign in to leave a comment.
Comments
6 comments