Each time we reboot a server with this application, the component service 'NETMAN' will inidicate it is down. We have updated the recovery settings to restart the connection, but Orion still indicates the service down.
lcoultress2--
If you don't get a timely answer from the community, open a support ticket.
M
Im getting the same thing. The service is running on the server but shows down in Orion. Restarting the service causes Orion to detect the service is up.
Here are a couple of troubleshooting steps that might help narrow down the cause. If you test this component monitor manually what is the result/status? If you create a new template using the Find Processes, Services & Performance Counters for this service when it's shown as "Down" in the template what status does it return when the services are listed vs when it's being monitored after it's applied to the node?
I am getting same thing, I can see the service is up and running but it fails if I run a test against that component. My workaround is to RDP into the server, run a test which will complete successfully and then poll that component.to update node. Should not need to do this workaround, I think I will open a support ticket with SW.
That sounds like a good idea. Please post the results/findings of your case here once it's closed. They may be beneficial to other members of the community. Thanks!
We just started usion Orion a few months ago and have been seeing this issue happening on some of our terminal servers. I've followed the same procedure as misoto by logging into the server and in the next polling cycle, the alert clears. Were you able to get a resolution from SW on how to resolve this without having to do that workaround?
Have you tried enabling the "Restart a Service" alert in the Advanced Alert Manager? This should restart the service if SAM believes it to be down.
I was going to set that up next, but wanted to check and see if there was any other solution before going forward with this.
Thanks for your input
