- Community Home
- >
- Services
- >
- Insight Remote Support
- >
- several servers in status "not-polling
Insight Remote Support
1753821
Members
9502
Online
108805
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2005 01:25 AM
11-23-2005 01:25 AM
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
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-23-2005 11:32 PM
11-23-2005 11:32 PM
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
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-27-2005 10:44 PM
11-27-2005 10:44 PM
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,
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,
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP