The UI login page will not come up after a possible system crash or reboot. The redis service may not come up if the database is corrupted, which will prevent you from logging in to the GUI via a browser. In recent versions it is also called the redis-ui service. It is possible that the actual postgres database is also corrupted.
This could be caused by a power failure while the database is being updated by the application.
Possible symptoms are:
The GUI will not be available
From /var/log/messages:
Apr 30 12:54:46 servername httpd: PHP Warning: _cake_core_ cache was unable to write 'page_titles_eng' to Redis cache in /gui/lib/Cake/Cache/Cache.php on line 309
When redis is restarted, it does not come back up:
service redis restart
Check the redis process:
ps -ef | grep redis
redis 4159 1 0 10:55 ? 00:00:08 /usr/sbin/redis-server /etc/redis.conf
root 9523 9477 0 12:29 pts/0 00:00:00 grep redis
Check the redis log:
tail /var/log/redis.log
[28710] 01 May 10:11:00 * Server started, Redis version 2.2.9
[28710] 01 May 10:11:00 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
[28710] 01 May 10:11:00 # Short read or OOM loading DB. Unrecoverable error, aborting now.
[28784] 01 May 10:11:22 * Server started, Redis version 2.2.9
[28784] 01 May 10:11:22 # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
[28784] 01 May 10:11:22 # Short read or OOM loading DB. Unrecoverable error, aborting now.
Cannot start redis client:
redis-cli
Could not connect to Redis at 127.0.0.1:6379: Connection refused
To rebuild the redis-ui database, run the following commands while logged in as root from the CLI:
Attempt to refresh the GUI login page to confirm that it is accessible again. If you are still having errors, make sure the postgresql service is up and running:
service postgresql status
If it says failed or is not running, contact technical support for further assistance.