Monitoring Engine Process 15 minute delayed start?

[ockmeyer]

Nagios XI is exhibiting some strange behavior. After writing the files, verifying the configuration, and restarting (CCM --> Tools --> Write Config Files) I get no errors.

But, when I look at the Monitoring Engine Process it shows the Process State as stopped (before.gif) and it stays that way for 15 minutes. Once the Process State starts running it shows that it has been running for those 15 minutes (after.gif).

If the Monitoring Engine has indeed been running, then why might the interface show it down for 15 minutes?

When I tail /var/log/messages I get several of the following:
Dec 5 11:10:08 SERVER ndo2db: Error: queue send error, retrying...
Dec 5 11:10:36 SERVER ndo2db: Message sent to queue

I'm running Nagios XI 2012R1.2

[mguthrie]

We've seen this issue on some installs with past releases. Here's the solution for it.
http://support.nagios.com/wiki/index.ph ... 3.x_Issues

[ockmeyer]

I already had all the settings except the kernel.msgmni = 256000 line, so I added it and tried again. It still takes 15 minutes for the process to show as started.

Any other ideas?

[mguthrie]

Can you post the output from:

Code: Select all

sysctl -p

[ockmeyer]

# sysctl -p
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 1
net.ipv4.conf.default.accept_source_route = 0
kernel.sysrq = 0
kernel.core_uses_pid = 1
net.ipv4.tcp_syncookies = 1
error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key
error: "net.bridge.bridge-nf-call-iptables" is an unknown key
error: "net.bridge.bridge-nf-call-arptables" is an unknown key
kernel.msgmnb = 131072000
kernel.msgmax = 131072000
kernel.shmmax = 4294967295
kernel.shmall = 268435456
kernel.msgmni = 256000

[mguthrie]

How large is your installation - How many hosts+services do you have on this install?

[ockmeyer]

976 Hosts, 5390 Services and expected to grow to probably twice that size.

[mguthrie]

Hmmm....does this issue persist after a reboot? Do the sysctl settings get preserved through a reboot?

[ockmeyer]

Yes the problem persists even after a reboot. The sysctl settings are are retained.

[mguthrie]

Lets try bumping up those memory limits a bit more and see if that takes care of the issue. Update the /etc/sysctl.conf file with the following values:

Code: Select all

kernel.msgmnb = 4294967295
kernel.msgmax = 4294967295
kernel.shmmax = 4294967295
kernel.shmall = 268435456