check_nagiosxiserver.php issue from NagiosXI

[rajasegar]

For the check_nagiosxiserver.php one:

It looks like the body and headers are empty from the debug output that you posted, the script uses curl to access the data, the http_code of 0 usually means that it had trouble connecting.

Back up your current /usr/local/nagios/libexec/check_nagiosxiserver.php, replace it with the one attached, force the check and then post the output from the XI interface.

Thank you

I was changing the worker configuration from 2 to 1 for another problem
https://support.nagios.com/forum/viewto ... 64#p157764

Suddenly the services became ok while nagios was restarting??
The strange thing is these checks are not using gearman.

[Box293]

I was changing the worker configuration from 2 to 1 for another problem
viewtopic.php?f=16&t=35138&p=157764#p157764

Suddenly the services became ok while nagios was restarting??
The strange thing is these checks are not using gearman.

Does changing it back make the problem re-occur.

[rajasegar]

I was changing the worker configuration from 2 to 1 for another problem
viewtopic.php?f=16&t=35138&p=157764#p157764

Suddenly the services became ok while nagios was restarting??
The strange thing is these checks are not using gearman.

Does changing it back make the problem re-occur.

I will check when there is a downtime.

[hsmith]

Let us know.

Thanks.

[rajasegar]

Let us know.

Thanks.

The checks is still ok after I changed the worker count back to 2.
So still no idea how this problem vanished.

[Box293]

Perhaps there were multiple nagios processes running?

[rajasegar]

Perhaps there were multiple nagios processes running?

Multiple nagios only impacting check_esx3 and check_nagiosxiserver.php?
Next time I will double check this.

[tmcdonald]

It's certainly possible, especially with checks that write temp files to maintain state between runs, or otherwise touch things outside of their own memory.

[rajasegar]

It's certainly possible, especially with checks that write temp files to maintain state between runs, or otherwise touch things outside of their own memory.

Ok. Wonder why nagios does not check before starting multiple instance. It would be easier this way.

Anyway please close this case.