SPOP - "not-polling" messages

[MikeL_4]

The SPOP server is giving us messages on 5 of our 30+ servers that they are: "not-polling"

What could be causing this error on these servers, they are on the same network as several of the other servers that are polling, and the servers have been up for overa 100 days...

Is there a way to retry ? and capture an error log somewhere? or do I need to place a call to HP support since the SPOP server is owned by HP ??

[Liem Nguyen · Accepted solution]

Mike,

Most of the time, you can stop/start hpservices then send a test event and the polling status would be updated (within 20 minutes):
/opt/hpservices/RemoteSupport/bin/reconnectToServer

Let me know if this works.

[MikeL_4]

Liem, gets more interesting... I stopped hpservices so mad and no hpservices processes were running.

After restarting: /sbin/init.d/hpservices start the mad process remains running but the other services died off....

[MikeL_4]

[/root]: =>/sbin/init.d/hpservices status
hpservices is running
[/root]: =>ps -ef |grep mad
root 18101 1 0 10:07:15 ? 0:02 mad -u root -g bin
[/root]: =>ps -ef |grep hpserv
root 6765 6647 1 13:47:02 pts/tg 0:00 grep hpserv
[root]: =>

[Liem Nguyen]

Mike,

What are "other services"?

/sbin/init.d/hpservices should "only" stop/start mad process.
/sbin/init.d/rstemsListener should stop/start rstlistener

Those are the only two daemons for ISEE to work.
Does the polling status change after all?

Regards,

[MikeL_4]

Liem, Thanks, I thought hpservices started mad and the listener.... after starting the
rstemsListener everything is working fine....
Thanks again for bailing me out...

[MikeL_4]

Thanks