NetXMS Agent not working after server restart
-
Hi,
Due to electricity work on the premises I had to shut down a couple of servers for the night.
After rebooting the servers the Status DCI of these servers (Win 2003 and n2003 R2) became green, however no Agent DCI’s readings were returnedA status poll gave the following error:
[22/11/11] Poll request accepted
[22/11/11] Starting status poll for node WebToPrint1
[22/11/11] Checking NetXMS agent connectivity
[22/11/11] NetXMS agent unreachable
[22/11/11] Current interface status is NORMAL
[22/11/11] Starting status poll on interface Lan1
[22/11/11] Starting ICMP ping
[22/11/11] Interface is NORMAL for 67 polls (1 poll required for status change)
[22/11/11] Interface status after poll is NORMAL
[22/11/11] Finished status poll on interface Lan1
[22/11/11] Node is connected
[22/11/11] Finished status poll for node WebToPrint1
[22/11/11] Node status after poll is NORMAL
[22/11/11] **** Poll completed successfully ****The event log on the Agent servers did not show any error. Restarting the agent service solved the problem.
- Is this an bug that NetXMS Agents do not start correctly upon server restart?
- Is it expected behavior for the NetXMS server not to report any problem if an Agent stops reporting while the Status is green, or is a separate Agent test needed?
Regards,
Dan
-
Hi!
It looks like a bug - agent should start after server restart. Is there anything interesting in agent's log?
Normally server should generate SYS_AGENT_UNREACHEABLE event if agent cannot be contacted. Please check that you have rule for generating alarm on this event.
Best regards,
Victor -
Hi,
In the Event Browser I Find SYS_AGENT_UNREACHEABLE for all servers that were shut downed.
Once the servers were restarted another SYS_AGENT_UNREACHEABLE was received, followed by SYS_AGENT_OK for the servers without issues.
I'm afraid the events on the Agent servers were overwritten since 22 November, as fas as I can remember there were no event to be seen.
For some reason the agent starts but cannot be detected after reboot by the server. Restarting the agent service later on solves the problem. Strange.Regards,
Dan
PS. I had no rule, just added one
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login