Log in to the CLI as root and confirm whether the postgres database is up and running:
If the database is not running, try to start the database by running:
service postgresql status
If the database cannot start, you need to find out what is taking up all of the space. Use the following commands to gather data:
service postgresql start
du -sh /var/log/*
du -sh /var/lib/pgsql/*
du -sh /var/log/audit/*
du -sh /var/log/csr-history/*
Often you can delete old log files to free up enough space to get the database running again. Directories that are typically safe to clean out are /var/log/audit/ and /var/log/csr-history/ If the space is being consumed in these log directories, after deleting the logs, try to start up the postgres database and attempt to log in again.
If all of the space is located in the /var/lib/pgsql directory structure, you will need to contact Blue Coat Support in order to receive direction on what tables in the database can be manually cleaned up.
If space is not an issue, look at permissions on /tmp. They should look like:
ls -ld /tmp drwxrwxrwt 7 root root 4096 2017-02-23 14:24 /tmp
To set /tmp permission properly run chmod a+rwxt /tmp
and check permissions again.
If either of these were the problem and have been resolved, running service postgresql start
will bring up postgres. Then attempt to view the UI login page from the browser.
To get more detail as to why postgres is not starting, you can run: bash -x /etc/init.d/postgresql start
Collect the output and send it to support and we can assist where needed.