Nagios Support Forum

This was address earlier from my other thread Check_HP_Blade_Chassis.

The following should resolve the kernel queue issue:

# service nagios stop
# service ndo2db stop
# killall -9 nagios
# killall -9 ndo2db
# rm -f /usr/local/nagios/var/ndo.sock
# rm -f /usr/local/nagios/var/ndo2db.lock
# for i in `ipcs -q | grep nagios |awk '{print $2}'`; do ipcrm -q $i; done
# service ndo2db start
# service nagios start

Were you experiencing anything odd with the server? If so, that may resolve that. If it doesn't resolve whatever weirdness you were seeing, could you let us know what that is?

Also, you are posting in the general forum. Since you are a customer, you should post in the customer forum. The reason for this is that the SLA applies to the customer forum. I can move this thread to the customer portion of the forum, if you have access to it.

Until I get the permission on customer support please keep all the communication on here.

One other thing could you please let me know how do you find out the kernel queue issue?

Thanks,

ipcs -q is the basic command. It should just list one. If you just use ipcs, then you will get more information, but the other information is not useful for this particular issue.

I'm still seeing this output is it gone be any issue?

[root@nagiosxi ~]# ipcs -q

------ Message Queues --------
key msqid owner perms used-bytes messages
0x1f000002 1343488 nagios 600 0 0

ponnpr7 wrote:I'm still seeing this output is it gone be any issue?

[root@nagiosxi ~]# ipcs -q

------ Message Queues --------
key msqid owner perms used-bytes messages
0x1f000002 1343488 nagios 600 0 0

This looks normal

Thanks.