Connecting to the Director Web UI times out with no errors shown
When trying to load up the Web UI in your web browser, you don't get any error messages. After a long time the connection may simply time out and give you the generic browser "Page cannot be displayed" error. However, when trying to TELNET into port 8082 on the Director appliance, the connection is established successfully. A packet capture on the client workstation while attempting to access the Web UI in a browser would show a TCP connection established successfully on port 8082, but no data is sent from Director to the client.
I just upgraded to the latest SGME version 184.108.40.206, and can no longer dowload, or even find the User Interface client.
In the latest operating system for Director- SGME- 220.127.116.11- there is no download link for the User Interface client.
This issue may be caused by the primary Director hard drive partition running out of space, due to a large amount of auditing logs being stored on it.
To confirm if this is the case, log into the Director console (SSH) and run the following steps:
1: Getting access to the command line interface- CLI:
2: Check your DNS service on the Director appliance.
NOTE: Look at the "Avail" column for the "/dev/sda2" entry. If the amount of free space is 0 or very small (under 100MB) there may be issues with starting the services that provide the web UI.
To resolve the issue, you will need to clear out the audit logs with the following commands:
3: The later versions of SGME do not come with a downloadable client. We no longer provide the client off of our bluecoat.com website, because it automaticly downloads once you authenticate to the Director appliance. You merely need to go to https://<ip-address>:8082 and authenticate. For more details on the JAVA downloadble, see the CMG guide, or goto KB4260
NOTE1: The above commands will remove all your audit logs. The last command will reboot Director. After the reboot, the Web UI should be accessible again.
NOTE2: If you have a large amount of ProxySG appliances (over 40) and running daily backup jobs on them, it would be advisable to disable audit logging, since this issue may come up again. The command "no logging dump-contents" from the "config t" prompt will disable the creation of audit logs.
NOTE3: For other tips, and troubleshooting hints as to why you cannot access the User Interface console, see FAQ1007
NOTE4: For more details on other Command Line Interface ( CLI) commands, available, see KB4178
Rate this Page
Please take a moment to complete this form to help us better serve you.