Tomcat4 appears to still be running in production after upgrade to Access Manager 3.1

  • 7006136
  • 26-May-2010
  • 26-Apr-2012

Environment

Novell Access Manager 3.1 Linux Access Gateway
Novell Access Manager 3.1 SSLVPN Server

Situation

When upgrading from 3.1.1 IR3 to 3.1.2, the output from the lagupgrade.sh says tomcat4 is found and then there is output saying it is removed from the runlevel. The original LAG install was done on Access Manager 3.0 and upgraded to 3.1.1 IR3 over time.

On some of the LAGs in the cluster, tomcat4 was not removed from the runlevel. We did a chkconfig and found tomcat4 and tomcat5 were both still set in the runlevel.

After the upgrade clustering issues were visible where jgroups could not get the 7801 port. The 'ps aux |grep java' command output  displayed tomcat4. Killing the tomcat4 process freed up the tcp 7801 tcp port.

On the lag upgrades that went smoothly and we found that these machines had an empty tomcat4 directory. We also found that /etc/init.d/novell-tomcat4 didn't exist.

Steps to reproduce:

1) you will have to install an old version of lag that has tomcat4.
2) upgrade to 3.1.2
3) After the upgrade run ps aux |grep java to see if tomcat4 is running.
4) run chkconfig to see if tomcat4 is on.

Resolution

Run 'rpm -e novell-tomcat4 --nodeps --noscripts' on the LAG to remove the reference to tomcat4.

Additional Information

Issue is -- Uninstall of novell-tomcat4 rpm failed [ rpm -e novell-tomcat4 --nodeps ].

Uninstall failed because of pre-uninstall script failure of novell-tomcat4 rpm.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.