Environment
Novell eDirectory 8.8 for Linux
Novell iManager
Novell Tomcat
Novell eDirectory
Novell Open Enterprise Server 2 (OES 2) Linux
Novell iManager
Novell Tomcat
Novell eDirectory
Novell Open Enterprise Server 2 (OES 2) Linux
Situation
* After reinstalling iManager, cannot access iManager, but iMonitor works fine
* After following KB 7005833, iManager still does not work.
* After reinstalling novell-tomcat5, iManager does not work
All the above give me the error "HTTP Status 503 - This application is not currently available" when access the iManager page
The output of /var/opt/novell/tomcat5/logs/catalina.out, shows the below error message:
May 19, 2010 14:11:01 PM org.apache.catalina.session.ManagerBase getDigest
SEVERE: Cannot find message associated with key managerBase.digest
java.security.NoSuchAlgorithmException: MD5 MessageDigest not available
Resolution
If iManager had been previously working, there would have been a valid java.security file. Search for the java.security file under security.backup and restore it to the security folder. The path of the security folder varies, depending on the java version on your machine. Example is as follows
/usr/lib/jvm/java-1_5_0-ibm/jre/lib/security
In case, the you do not have a backup folder for security and the contents of the java.security file is empty, add the following lines to the file. If the file is not empty make sure all of these lines are present and un-commented. Also note that the order of the lines in the file is relevant.
security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
security.provider.2=com.ibm.crypto.provider.IBMJCE
security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
security.provider.4=com.ibm.security.cert.IBMCertPath
security.provider.5=com.ibm.security.sasl.IBMSASL
security.provider.60=sun.security.provider.Sun
security.provider.61=com.sun.net.ssl.internal.ssl.Provider
Save the file and restart novell-tomcat5 (rcnovell-tomcat5 restart). Now iManager should work.
The version of java that iManager is using is not necessarily the only version or the default version of java on the server. Make sure you edit the java.security file for the version of java that iManager is using.
/usr/lib/jvm/java-1_5_0-ibm/jre/lib/security
In case, the you do not have a backup folder for security and the contents of the java.security file is empty, add the following lines to the file. If the file is not empty make sure all of these lines are present and un-commented. Also note that the order of the lines in the file is relevant.
security.provider.1=com.ibm.jsse2.IBMJSSEProvider2
security.provider.2=com.ibm.crypto.provider.IBMJCE
security.provider.3=com.ibm.security.jgss.IBMJGSSProvider
security.provider.4=com.ibm.security.cert.IBMCertPath
security.provider.5=com.ibm.security.sasl.IBMSASL
security.provider.60=sun.security.provider.Sun
security.provider.61=com.sun.net.ssl.internal.ssl.Provider
Save the file and restart novell-tomcat5 (rcnovell-tomcat5 restart). Now iManager should work.
The version of java that iManager is using is not necessarily the only version or the default version of java on the server. Make sure you edit the java.security file for the version of java that iManager is using.