Nagios Xi and CWP Pro problem

[Starburst]

I presume that you've tried a cron with

Code Select Expand

/etc/rc.d/init.d/nagios reload
or

Code Select Expand

/usr/local/nagios/bin/nagios -d /usr/local/nagios/etc/nagios.cfg
and set it to run after that cwp one has done it's thing.

Nagios is running on another box.
I tried restarting the nagios service on that box when I noticed this.
Nothing changed.

Again everything is reporting correctly, except the 2 CWPPro servers after the cron.daily runs.

Only fix right now, is to restart the server CWPPro is running on after the cron.daily runs.

Then all is back normal.

[ejsolutions]

Is Monit running on the CWP Pro ones? Something must be killing the nagios process/daemon..
I'd be looking at the cron logs on both server types, to try to identify the culprit.

[Starburst]

Saw the chat back & forth.

It could be something in that area that is proprietary, and this is fine not to disclose.

I don't see how this thread if off topic with a problem I've narrowed down to CWWPro though.

Maybe no one else has monitored processes running, which isn't a deal breaker for me to disable, if it comes to that.

[Starburst]

Is Monit running on the CWP Pro ones? Something must be killing the nagios process/daemon..
I'd be looking at the cron logs on both server types, to try to identify the culprit.

Nagios isn't running on the CWPPro server, Monit is (tried to disable it, no difference).
xinetd service is still running, wasn't killed.

Trying to restart xinetd service doesn't change anything.

[ejsolutions]

Do you have to open particular ports in the firewall for nagios?
You might want to check "iptables -L" before and after the problem occurs (the cwp cron task). If there is a difference then use /etc/csf/csfpost.sh to add in the missing entries. It may explain why you need a reboot for nagios to begin functioning again.

[Starburst]

Do you have to open particular ports in the firewall for nagios?
You might want to check "iptables -L" before and after the problem occurs (the cwp cron task). If there is a difference then use /etc/csf/csfpost.sh to add in the missing entries.

Nagios uses port 5666 and is open.
As Nagios is running fine 23 hr 55mins each day, and only stops after the cron.daily runs.
xinetd is still running, and restarting the service doesn't work.

And I don't feel like having to reboot servers each day after cron.daily runs.

Checked the logs files and don't see anything.

I'll just chaulk it up to that processes can't be monitored on CWPPro servers.

[Starburst]

Do you have to open particular ports in the firewall for nagios?
You might want to check "iptables -L" before and after the problem occurs (the cwp cron task). If there is a difference then use /etc/csf/csfpost.sh to add in the missing entries. It may explain why you need a reboot for nagios to begin functioning again.

Thanks for your help ejsolutions.

But I'm giving up on this bug for right now.

[ejsolutions]

Thanks for your help ejsolutions.

You're welcome.
Good luck.

[Sandeep]

we've enterprise grade nagios monitoring for our clients and they doesn't have any such issues, check the /var/log/messages and nagios log for the issues.