Page 1 of 1

nagios.lock not found

Posted: Thu Jul 05, 2012 4:15 am
by Flava
Hi All,

I am getting seeing a lot of error in /var/log/messages

Code: Select all

 10:11:09 localhost ndo2db: Message sent to queue
Jul  5 10:11:09 localhost ndo2db: Error: queue send error, retrying...
Jul  5 10:11:10 localhost ndo2db: Message sent to queue
Jul  5 10:11:10 localhost ndo2db: Error: queue send error, retrying...
Jul  5 10:11:11 localhost ndo2db: Message sent to queue
Jul  5 10:11:11 localhost ndo2db: Error: queue send error, retrying...
Jul  5 10:11:12 localhost ndo2db: Message sent to queue
Jul  5 10:11:12 localhost ndo2db: Error: queue send error, retrying...
Jul  5 10:11:13 localhost ndo2db: Message sent to queue
Jul  5 10:11:13 localhost ndo2db: Error: queue send error, retrying...
Also I have noticed, at times when I apply configuration either from the config wizard or configuration manager Nagios daemon is not running as the system health status reports it cannot find 'nagios.lock' under the XI System Component Status. I am having to manually start the daemon each time, and when I add new services, I have to manually reload the config "/etc/init.d/nagios reload". There is a lag between applying config and webpage refreshing. I have cleared local cache, and tried different browsers, issue still persists.

Anyone experiencing this issue.

Re: nagios.lock not found

Posted: Thu Jul 05, 2012 11:43 am
by scottwilkerson
With all these queue send errors I believe the problem may be related to this
http://support.nagios.com/wiki/index.ph ... 3.x_Issues

What version of XI are you running?

Re: nagios.lock not found

Posted: Mon Jul 09, 2012 5:08 am
by Flava
I am using Nagiosxi 3.2

Re: nagios.lock not found

Posted: Mon Jul 09, 2012 7:55 am
by scottwilkerson
Can I have you run

Code: Select all

service ndo2db stop
service nagios stop
killall -9 ndo2db
killall -9 nagios
service ndo2db start
service nagios start

Re: nagios.lock not found

Posted: Mon Jul 09, 2012 8:10 am
by Flava
I have updated /etc/sysctl.conf with settings below and rebooted the servers. it seems to be a bit more stable now.

Code: Select all

# Controls the maximum size of a message, in bytes
 kernel.msgmnb = 131072000
 
 # Controls the default maxmimum size of a mesage queue
 kernel.msgmax = 131072000
 
 # Controls the maximum shared segment size, in bytes
 kernel.shmmax = 4294967295
 
 # Controls the maximum number of shared memory segments, in pages
 kernel.shmall = 268435456