Port 50000 not open in Systems Insight Manager

[Jose Manuel Maldonado]

Hi All,

I have been searching the forums and I only came up to a solution telling to recheck / change the password of the user starting the hpsim service if it had been changed in the AD / local accounts. Sorry if this has been posted before

This problem started happening when I restarted the hpsim service (taking care of all its dependencies).

The problem here is, all the services related to SIM are up and running with no problems (at least no problems listed in the Event Viewer) but netstat does not show up the port 50000 (nor 280) listening.

I have tried several times to restart these services, changing the log in accounts for these services, rebooting the server... nothing seems to work.

Please advice.

Thanks for any support!

[Jose Manuel Maldonado]

By the way, HP SIM is V5.0 and the server is a BL40p.

Thanks again!

[James ~ Happy Dude]

Jose,
In the server.xml file (located in the jboss\server\hpsim\deploy\jbossweb-tomcat50.sar
directory), there are two occurences of 50000 port.

enableLookups="false" redirectPort="50000" acceptCount="10" debug="0"
connectionTimeout="60000" />


For the second port entry,

secure="true" maxThreads="200" minSpareThreads="10" maxSpareThreads="25"
enableLookups="false" acceptCount="10" debug="5" URIEncoding="utf-8"
useBodyEncodingForURI="true" clientAuth="false"
keystoreFile="C:\bullwinkle\target\Windows\stage\SIM\config\certstor\hp.keystore"
keystorePass="removed" sslProtocol="TLS" />

Make sure, the port # have not been changed;

Refer to the Understanding HP SIM 5.0 Security white paper at http://h18013.www1.hp.com/
products/servers/management/hpsim/infolibrary.html for a list of ports in use.

James.

[Jose Manuel Maldonado]

Hi James, thanks for your fast response

Unfortunately the port seems to be correct in the server.xml. This is the second occurrence:




Here is the result of executing netstat:

TCP 0.0.0.0:50008 0.0.0.0:0 LISTENING 2844

TCP 0.0.0.0:50009 0.0.0.0:0 LISTENING 2844

TCP 0.0.0.0:50013 0.0.0.0:0 LISTENING 2844

TCP 0.0.0.0:50014 0.0.0.0:0 LISTENING 2844

TCP 0.0.0.0:50015 0.0.0.0:0 LISTENING 2844

I see in the server.xml file that there are three other entries for ports 50001, 5002 and 50003 which are not open neither.

Any ideas ?

Thanks!

[James ~ Happy Dude]

Do you have Partition Manager installed on this server Jose ? If So, Which version ?

James.

[James ~ Happy Dude]

Also Refer:
http://docs.hp.com/en/418812-001/ch11s01.html

Regards

[Jose Manuel Maldonado]

No, Partition Manager is not installed in this server.

Thanks for the link, I already checked that document and the troubleshooting guide.

Thanks.
Jose.

[James ~ Happy Dude]

Did You fail to make appropriate port number entries in the wbemportlist.xml file:
On Linux and HP-UX:
/etc/opt/mx/config/identification

On Windows:
C:\program files\hp\systems insight manager\config\identification

The folders listed above are the default folders and should be used unless you have changed the installation folder location.
________________________________
I am running out of ideas now !
;)

[James ~ Happy Dude]

The file seems CORRECT Jose, & I was expecting this.
I am out of solutions; But will try searching again... this morning.

[Jose Manuel Maldonado]

Ok, thanks for your efforts!

If we don't come up to any solution I guess I will have to reinstall it...

This is annoying, I didn't make any changes in the configuration appart from creating a new user and restarting the services.

I have been looking thoroughly the event viewer again and found these entries... maybe they can clarify something

214 entries fixed in TABLE noticeXMLData
15 entries fixed in TABLE SecurityNoticesData
1 entries fixed in TABLE deviceAssocObjects
5 entries fixed in TABLE SIM_NodeEntitlement
ERROR: TABLE noticeXMLData KEY noticeId may contain 214 entrie(s) not in table notices KEY noticeId
ERROR: TABLE SecurityNoticesData KEY noticeId may contain 15 entrie(s) not in table notices KEY noticeId
ERROR: TABLE deviceAssocObjects KEY NodeId may contain 1 entrie(s) not in table devices KEY nodeLuid
ERROR: TABLE SIM_NodeEntitlement KEY NodeId may contain 5 entrie(s) not in table devices KEY nodeLuid
mxdomainmgr(error): Received an remote exception doing lookup to RMI registry.

[Jose Manuel Maldonado]

Hi again,

I have been looking through the SIM logs and I have found this errors (attached file).
There are lots of exceptions like this one:

22 oct 2007 09:36:30,448 ERROR [MxStartup] Starting failed com.hp.mx:service=MxStartup
java.lang.NullPointerException
at com.hp.mx.core.collectionmanager.MxCollectionManager.getMemberObjectName(MxCollectionManager.java:4129)
at com.hp.mx.core.collectionmanager.MxCollectionManager.getMemberObjectList(MxCollectionManager.java:2264)
at com.hp.mx.core.collectionmanager.MxCollectionManager.getCollectionsForObject(MxCollectionManager.java:3140)
at com.hp.mx.core.controllers.MxCollectionController.getCollectionsForObject(MxCollectionController.java:4469)
at com.hp.mx.core.querymanager.QueryManager.initializeQueries(QueryManager.java:260)
at com.hp.mx.core.controllers.MxQueryController.initializeQueries(MxQueryController.java:6525)
at com.hp.mx.config.MxInit.setup(MxInit.java:87)
at com.hp.mx.core.daemon.MxSecureRMIImpl.startupHPSIMCore(MxSecureRMIImpl.java:242)
at com.hp.mx.jboss.MxStartup.startService(Unknown Source)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy16.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:415)
at org.jboss.system.ServiceController.start(ServiceController.java:437)
at org.jboss.system.ServiceController.start(ServiceController.java:437)
at org.jboss.system.ServiceController.start(ServiceController.java:437)
at org.jboss.system.ServiceController.start(ServiceController.java:437)
at org.jboss.system.ServiceController.start(ServiceController.java:437)
at org.jboss.system.ServiceController.start(ServiceController.java:437)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy8.deploy(Unknown Source)
at org.jboss.deployment.scanner.URLDeploymentScanner.deploy(URLDeploymentScanner.java:304)
at org.jboss.deployment.scanner.URLDeploymentScanner.scan(URLDeploymentScanner.java:478)
at org.jboss.deployment.scanner.AbstractDeploymentScanner$ScannerThread.doScan(AbstractDeploymentScanner.java:201)
at org.jboss.deployment.scanner.AbstractDeploymentScanner.startService(AbstractDeploymentScanner.java:274)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:271)
at org.jboss.system.ServiceMBeanSupport.jbossInternalLifecycle(ServiceMBeanSupport.java:221)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.system.ServiceController$ServiceProxy.invoke(ServiceController.java:899)
at $Proxy0.start(Unknown Source)
at org.jboss.system.ServiceController.start(ServiceController.java:415)
at sun.reflect.GeneratedMethodAccessor5.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy4.start(Unknown Source)
at org.jboss.deployment.SARDeployer.start(SARDeployer.java:251)
at org.jboss.deployment.MainDeployer.start(MainDeployer.java:829)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:641)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:604)
at org.jboss.deployment.MainDeployer.deploy(MainDeployer.java:588)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.jboss.mx.server.ReflectedDispatcher.dispatch(ReflectedDispatcher.java:60)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:62)
at org.jboss.mx.server.Invocation.dispatch(Invocation.java:54)
at org.jboss.mx.server.Invocation.invoke(Invocation.java:82)
at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:198)
at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:473)
at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:176)
at $Proxy5.deploy(Unknown Source)
at org.jboss.system.server.ServerImpl.doStart(ServerImpl.java:407)
at org.jboss.system.server.ServerImpl.start(ServerImpl.java:311)
at org.jboss.Main.boot(Main.java:191)
at org.jboss.Main$1.run(Main.java:480)
at java.lang.Thread.run(Unknown Source)

This seems serious...

Thanks!

[James ~ Happy Dude]

Strange !
Rest assured, It doesn't seem to be a Database issue;

Is there a Proxy/Firewall ?

[Jose Manuel Maldonado]

No, there are no strange items in the LAN.

Furthermore, at the bottom of the log I found this:
22 oct 2007 09:37:11,689 ERROR [URLDeploymentScanner] Incomplete Deployment listing:
Packages waiting for a deployer:
org.jboss.deployment.DeploymentInfo@19a4435f { url=file:/C:/Program Files/HP/Systems Insight Manager/jboss/server/hpsim/deploy/jboss-net.sar/jboss-net.war/ }
deployer: null
status: Starting
state: INIT_WAITING_DEPLOYER
watch: file:/C:/Program Files/HP/Systems Insight Manager/jboss/server/hpsim/deploy/jboss-net.sar/jboss-net.war/
lastDeployed: 1193038535361
lastModified: 1179443904746
mbe(......cropped......)

This "waiting for a deployer... deployer:null" does head you towards something ?

[Jose Manuel Maldonado]

And by the way, just to ensure it is not a database issue, I have run mxconfigrepo -c and it exits with no errors found...

:(

[James ~ Happy Dude]

Hello Jose,
If you have a Backup for the SIM Database, try resetting the SIM by using the command:

mxconfigrepo -a


James.

[Jose Manuel Maldonado]

Hi James,

finally I have decided to reinstall both the server and SIM, hope this works.

I have a database backup but unfortunately it is old enough not to make sense restoring it, I will be more careful nex time.

Also, I am keeping the disks from the old installation (the corrupt one) to make some troubleshooting if I have the time, including the database restore to see if that resolves the problem and let you know.

I am sure this is not the best answer to the problem, but we are in a hurry since we have an important meeting to discuss SIM in a few days.

Thanks for your support and effort!

Best Regards,
Jose.

[James ~ Happy Dude]

I would agree with you Jose;

However, requesting you not to close this thread & see If someone else has an idea on how -to;

Perhaps it will help us in future.
Cheers !
James.