Insight Remote Support
1753937 Members
10102 Online
108811 Solutions
New Discussion

several servers in status "not-polling

 
IT Systemmanagement
Occasional Contributor

several servers in status "not-polling

Hello,

I´ve got several machines in the "not-polling" status. Even the following commands could not bring them back to polling:

/opt/hpservices/RemoteSupport/bin/reconnectToServer
/sbin/init.d/hpservices stop/start
/sbin/init.d/rstemsListener stop/start

What else could be the problem?

Thanks in advance,

Frank Grote
2 REPLIES 2
Frank Alden Smith
Trusted Contributor

Re: several servers in status "not-polling

Frank,

Are you able to browse from these servers to the ISEE Content Server, or (if you have one deployed) the SPOP? If you are supported by the Americas ISEE Content Server you should be able to reach: http://isee.americas.hp.com/mots/motserv

If the servers in question do not support a browser you will need the java application checkcon.class to perform the equivalent test.

Take care,
frank
All knowing is doing.
Liem Nguyen
Honored Contributor

Re: several servers in status "not-polling

Hi Frank,

After running /opt/hpservices/RemoteSupport/bin/reconnectToServer, do you see a new incident on the SPOP? If you do, the Polling status should be changed within 30 minutes.

If you don't see the incident, then most likely there is a communication broken between your ISEE Servers and the SPOP.

Make sure:
1. There is only ONE mad daemon running (ps -ef |grep mad).
2. Send another test:
/opt/hpservices/RemoteSupport/bin/iseeConnectivityTest.sh
3. Check Open Incidents on the SPOP.
4. If you don't see the incident, check /opt/hpservices/log/mad.log for possible error.

NOTE: Polling Adapter on the SPOP is updated every 30 minutes, if you see the new incident, then Polling should be updated in the next 30 minutes.

Hope this helps,