SUMMARY
This article explains some possible reasons why you cannot login to the Unitrends interface and their resolutions.
ISSUE
When a system boots there is a script file that is run that starts the Unitrends database. If the database is not running, then the UI will not be able to service the login request. One possible cause to check is to make sure that the DB is running.
Use an SSH client such as PuTTY to access the Unitrends system at the command line level.
Note: Ensure you have the OS password to access the Unitrends system’s command line. The OS password may differ from the password used to access the User Interface.
Run this command to see if the database is running:
ps ax | grep postgres | head -2
You should see something like this in the output if the DB is running:
[root@Recovery-10032 ~]# ps ax | grep postgres | head -2
766 ? Ss 0:00 postgres: postgres bpdb [local] idle
767 ? Ss 0:00 postgres: postgres bpdb [local] idle
If the DB is not running, you would see something like:
[root@Recovery-10032 ~]# ps ax | grep postgres | head -2
1592 pts/2 S+ 0:00 grep --color=auto postgres
To start the DB run this command:
/usr/bp/bin/start_db.sh