BUG REPORT: Problems with web interface (Tomcat) after the update of Symantec Encryption Management Server (formerly PGP Universal Server)
|Article:TECH149248|||||Created: 2009-01-13|||||Updated: 2013-04-29|||||Article URL http://www.symantec.com/docs/TECH149248|
After installing the update for PGP Universal Server or Symantec Encryption Management Server you receive an error instead of the login screen tp the Administration Console in your web browser. Or you may notice that some icons are missing off of certain pages on the Administration Console.
You may see one of these or similar:
HTTP Status 404 - /omc/GetLoginScreen.uevent
type Status report
description The requested resource(/omc/GetLoginScreen.uevent) is not available.
HTTP Status 404 - /omc/GetUpdatesScreen.event
type Status report
description The requested resource (/omc/GetUpdatesScreen.event) is not available.
Symantec Encryption Management Server 3.3.0 (formerly PGP Universal Server 3.2.1.x or later)
This is due to missing files in the /var/tomcat folder after the update was applied to the server. Port 22(SSH), 80 (HTTP), and 443(HTTPS) may be blocked by a firewall.
The issue is resolved by recreating the missing omc folder on the server via the command line. To recreate the folder, you must access the server via a secure SSH client.
After accessing the server via SSH, use the following to recreate the missing folder.
Caution: Before making this type of change through the command line you should ensure that you have a current backup on your Symantec Encryption Management Server (formerly PGP Universal Server) and have tested the backup to ensure that it will restore correctly before proceeding. Failure to delete the correct directory may cause your Symantec Encryption Management Server to not work right and require you to reinstall the Symantec Encryption Management Server and restore from the backup.
Type the following at the command line prompt:
1. pgpsysconf --stop tomcat
2. rm -rf /var/tomcat/webapps/omc
3. rm -rf /var/tomcat/work/Catalina/localhost/omc
4. pgpsysconf --start tomcat
5. pgpsysconf --apache
These commands will force the Tomcat servlet to unpack a fresh copy of the omc web application. It should take less than 30 seconds for the Tomcat servlet to discover the missing omc folder and recreate it.
Accessing the server via command line for read-only purposes (such as to view settings, services, logs, processes, disk space, query the database, etc) is supported. However, performing configuration modifications or customizations via the command line may void your PGP Support agreement.
You should not establish root access to your server unless directed to do so by Symantec Technical Support or Symantec Engineering.
Usability: PUP update to 3.2.x gives a 404 error for OMC and won't load the admin page
Article URL http://www.symantec.com/docs/TECH149248