Issue with 6.1 and web interface

[noc at defenderhosting.com]

Hi everyone-

We recently picked up the upgrade on our 1950s/2950s from 5.5 to 6.1 via yum and noticed that the web interface does not work anymore.  Every other function seems to work just fine according to ITAssist.  It's still responding via SNMP queries, etc.  The web just does not respond.

I checked out one of the machines and found the below:

cat /var/log/dsm_om_connsvc32dIO.log
#
# An unexpected error has been detected by Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0xb7ef5a1b, pid=12469, tid=2895117200
#
# Java VM: Java HotSpot(TM) Client VM (11.0-b16 mixed mode linux-x86)
# Problematic frame:
# C [libomacs32.so.1+0x11a1b] GetIPAddrStrList+0x52
#
# An error report file with more information is saved as:
# //hs_err_pid12469.log
#
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#
3 2009] (12469) RunServer:worker waiting for shutdown message...
[Jul 8 12:43:23 2009] (12467) RunServer:parent process EXIT status(0)
[Jul 8 12:43:23 2009] (12468) RunServer:daemon waiting for shutdown signal...


whereas on a working server the log looks perfectly normal:

cat /var/log/dsm_om_connsvc32dIO.log
Servertec (R) Application/Web Server Version 1.12.0 09/04/2005 Open Source Release
Copyright (C) 1998-2005 Servertec. All rights reserved.

1324) ModuleAttach: starting the startserver thread
[Jun 24 00:35:19 2009] (21303) RunServer:daemon worker forked
[Jun 24 00:35:19 2009] (21303) RunServer:daemon waiting for worker init status
[Jun 24 00:35:19 2009] (21324) ModuleAttach: exit
[Jun 24 00:35:19 2009] (21324) RunServer: ModuleAttach success
[Jun 24 00:35:19 2009] (21324) RunServer:worker waiting for shutdown message...
[Jun 24 00:35:19 2009] (21303) RunServer:daemon waiting for shutdown signal...
[Jun 24 00:35:19 2009] (21114) RunServer:parent process EXIT status(0)


The packages installed on the working system are below:

 rpm -qa | grep srv
srvadmin-omauth-5.5.0-364.rhel5
srvadmin-iws-5.5.0-364
srvadmin-ipmi-5.5.0-364.rhel5
srvadmin-racadm5-5.5.0-364
srvadmin-racsvc-5.5.0-364
srvadmin-storage-5.5.0-364
srvadmin-hapi-5.5.0-364
srvadmin-rac4-components-5.5.0-364
srvadmin-base-5.5.0-364
srvadmin-omilcore-5.5.0-364
srvadmin-racadm4-5.5.0-364
srvadmin-cm-5.5.0-364
srvadmin-rac5-components-5.5.0-364
srvadmin-racdrsc4-5.5.0-364
srvadmin-diagnostics-5.5.0-364
srvadmin-rac4-5.5.0-364
srvadmin-deng-5.5.0-364
srvadmin-omacore-5.5.0-364
srvadmin-jre-5.5.0-364
srvadmin-odf-5.5.0-364
srvadmin-isvc-5.5.0-364
srvadmin-racdrsc5-5.5.0-364
srvadmin-webserver-5.5.0-364
srvadmin-storageservices-5.5.0-364
srvadmin-syscheck-5.5.0-364
srvadmin-old-5.5.0-364
srvadmin-omhip-5.5.0-364
srvadmin-rac5-5.5.0-364



and the packages on the non-working web interface system are below:

 rpm -qa | grep srvadmin
srvadmin-deng-6.1.0-648
srvadmin-omhip-6.1.0-648
srvadmin-jre-6.1.0-648
srvadmin-racdrsc4-6.1.0-648
srvadmin-storageservices-6.1.0-648
srvadmin-idracdrsc-6.1.0-648
srvadmin-wsmanclient-6.1.0-648.rhel5
srvadmin-all-6.1.0-648
srvadmin-hapi-6.1.0-648
srvadmin-syscheck-6.1.0-648
srvadmin-omacore-6.1.0-648
srvadmin-isvc-6.1.0-648
srvadmin-racadm4-6.1.0-648
srvadmin-cm-6.1.0-648
srvadmin-omauth-6.1.0-648.rhel5
srvadmin-rac4-components-6.1.0-648
srvadmin-storage-6.1.0-648
srvadmin-racadm5-6.1.0-648
srvadmin-rac4-6.1.0-648
srvadmin-idrac-components-6.1.0-648
srvadmin-idracadm-6.1.0-648
srvadmin-rac5-6.1.0-648
srvadmin-iws-6.1.0-648
srvadmin-standardAgent-6.1.0-648
srvadmin-omilcore-6.1.0-648
srvadmin-omcommon-6.1.0-648
srvadmin-rac5-components-6.1.0-648
srvadmin-racsvc-6.1.0-648
srvadmin-racdrsc5-6.1.0-648
srvadmin-base-6.1.0-648
srvadmin-idrac-6.1.0-648
srvadmin-webserver-6.1.0-648
srvadmin-ssa-6.1.0-648.rhel5



Has anyone ever run into this issue before, and if so, how did you resolve it?

Thanks!



Jon Wolberg
Systems Engineer
Virtacore Systems