Nagios Support Forum

Good morning all,

I had completed an update from the previous minor to the latest minor version and we have clients showing offline that are online. The simple resolution would probably be to login to the machine and restart the NPCA service. Currently all our clients are in a passive configuration. I would like to know if there is a resolution to fix this rather than having to login to individual machines to restart the services. I have left the clients in the original state since the upgrade so they have been reporting offline for a couple days. I will PM the agent the profile.


PLEASE, do not post any client names or IPs in the posting as security is very important to our clients.

Have a great day,
Joseph S.

Please go to Admin > Inbound Transfers and make sure the NRDP token is correct and then click the Update Settings button and see if that resolves it.

Good evening Sean,

I was able to resolve it as in the past by restarting the nagios xi service on the machine itself and my manager didnt want me to look into further unfortunately. Would there be a quick reasoning why most of the clients would connect passively to the service without the need to login and restart the service while these select few required this to reconnect?

Thank you again,
Joseph S.

When you say this:

restarting the nagios xi service

Do mean that to resolve it you only needed to restart the nagios service?

Were you seeing errors in your /usr/local/nagios/var/nagios.log?

Please PM or that file (or the archives file for that day from /usr/local/nagios/var/archives) so I can see what nagios was logging.

Please PM me a copy of your profile.zip as well.

I'm wondering if for some reason the /usr/local/nagios/var/rw/nagios.cmd wasn't a pipe file or something. If you see it occur again, get the output of these commands before resolving:

Hey Sean,

I have PM'ed you the requested info minus a profile since I had to resolve it at the time. Unfortunately it is not currently showing an issue but periodically occur with our fleet of a host going down and requiring a service restart on the endpoint to get the system to talk to xi again.

We will refer the the client in the example as "The Client" as our client would not like to be named as their computer name reveals information about them. Sorry coming back to this so late as it was re-visited and acknowledged that a second look at this is actually needed.

Thanks again,
Joseph S.

I'm not really seeing the reason from the logs, I would need the apache logs to see if I can see anything in there (the profile contains the logs)

Are you saying you needed to restart the service on the sending system (not the xi server)?

Good morning Sean,

I have an example we can use this morning. This happened over night and this client isnt as sensitive as the previous example. The client name is US - AEDR-KM-01.

I will PM you the profile.

Please answer this:

Are you saying you needed to restart the service on the sending system (not the xi server)?

Or is it something you have to do on the xi server?

Good morning,

To resolve the issue, we have to restart the NCPA service on the endpoint to get the client talking to Nagios xi server again.

Do you have any further questions? Can we lock this topic and mark it as resolved? Thanks!