Nagios Support Forum

1. OS CentOS 6.4 64bit with SELinux set to permissive
2. Nagios installed and working except for the below issue related to installing Nagvis.
3. Nagvis working accept for the data connection on the port.
4. I am using MK-Livestatus as my backend
5. Both Nagio and Nagvis are members of group ‘nagios’

Here is a quick explanation of where I am in the process:


I ran:
service nagios status
Return: nagios dead but subsys locked
service nagios stop // Just to be sure
I removed the following files:
/usr/local/nagios/var/nagios.lock
/var/lock/subsys/nagios
I ran:
service iptables stop
In file “nagios.cfg” I have the following:
event_broker_options=-1
broker_module=/usr/local/lib/mk-livestatus/livestatus.o /usr/local/nagios/var/rw/live
Both ../livestatus.o and ../rw/ exist under group:nagios ownership
Also ../rw is where nagios.cmd pipe is located
I run:
service nagios start
Return:Started Nagios
service nagios status
Return:nagios dead but subsys locked
In the nagios.log file I am getting:
Error: Could not load module ‘/usr/local/lib/mk-livestatus/livestatus.o’ -> /usr/local/lib/ mk-livestatus/livestatus.o: undefined symbol: last command_check

I am sure I am missing something basic and incorrect here but I cannot see it. Your help and time are greatly appreciated.

Are you running core 4? There have been a number of issues reported that vanilla livestatus is having problems with core 4 at this time.

Yes I am. Should I just roll back to 3.x?

Resolved Thanks

Did you resolve it by rolling back to 3.5.1?

Yes, I replaced 4.0 with 3.5 and all is fine.

Is there away to know when the 4.0 fix has been made, other than simply watching and waiting for the fix-notes per release?

I would take a look through the tracker site and see if someone has added a bug report then follow that, if they have not I would open one for the devs to see:

tracker.nagios.org

Will do and THANKS for the help.