Re: Status Tab Errors

630 views
Skip to first unread message

Tomas Edwardsson

unread,
May 9, 2013, 12:42:23 PM5/9/13
to ada...@googlegroups.com
You probably went through almost the whole install steps. You have to go through the

Using the Status View part as well. I noticed one error we still haven't fixed. The first step in that section needs to look something like

yum install -y pnp4nagios mk-livestatus --enablerepo=ok-testing

Try that out.


On Thu, May 9, 2013 at 4:08 PM, RJ DeVries <thealum...@gmail.com> wrote:
Hello, I just stood up a new Nagios box with Adagios and am getting the follow error when trying to access the status tab.  I am still new to Linux, so any help would be appreciated.  Thanks.
ParserError: 'Could not find path to livestatus socket file. Please specify one or make sure livestatus broker_module is loaded'
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/adagios/status/views.py", line 54, in wrapper
    return fn(*args,**kwargs)
  File "/usr/lib/python2.6/site-packages/adagios/status/views.py", line 681, in status_index
    c = adagios.status.utils.get_statistics(request)
  File "/usr/lib/python2.6/site-packages/adagios/status/utils.py", line 193, in get_statistics
    l = livestatus(request)
  File "/usr/lib/python2.6/site-packages/adagios/status/utils.py", line 23, in livestatus
    livestatus = pynag.Parsers.mk_livestatus(nagios_cfg_file=adagios.settings.nagios_config, authuser=authuser)
  File "/usr/lib/python2.6/site-packages/pynag/Parsers/__init__.py", line 1423, in __init__
    raise ParserError("Could not find path to livestatus socket file. Please specify one or make sure livestatus broker_module is loaded")
ParserError: 'Could not find path to livestatus socket file. Please specify one or make sure livestatus broker_module is loaded'

--
You received this message because you are subscribed to the Google Groups "adagios" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adagios+u...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

RJ DeVries

unread,
May 9, 2013, 1:13:58 PM5/9/13
to ada...@googlegroups.com
Alright, did that.  Now I am getting a slightly different error:
ParserError: "[Errno 2] No such file or directory while connecting to '/var/spool/nagios/cmd/livestatus'. Make sure nagios is running and mk_livestatus loaded."
Traceback (most recent call last):
  File "/usr/lib/python2.6/site-packages/adagios/status/views.py", line 54, in wrapper
    return fn(*args,**kwargs)
  File "/usr/lib/python2.6/site-packages/adagios/status/views.py", line 681, in status_index
    c = adagios.status.utils.get_statistics(request)
  File "/usr/lib/python2.6/site-packages/adagios/status/utils.py", line 195, in get_statistics
    c['service_totals'] = l.query('GET services', 'Stats: state = 0', 'Stats: state = 1', 'Stats: state = 2','Stats: state = 3',columns=False)
  File "/usr/lib/python2.6/site-packages/pynag/Parsers/__init__.py", line 1507, in query
    s = self._get_socket()
  File "/usr/lib/python2.6/site-packages/pynag/Parsers/__init__.py", line 1463, in _get_socket
    % (e, self.livestatus_socket_path)
ParserError: "[Errno 2] No such file or directory while connecting to '/var/spool/nagios/cmd/livestatus'. Make sure nagios is running and mk_livestatus loaded."

Tomas Edwardsson

unread,
May 9, 2013, 1:22:09 PM5/9/13
to ada...@googlegroups.com
I still think something is missing, did you go through the whole bit in http://adagios.org/#using-the-status-view ?

pynag config --append "broker_module=/usr/lib64/nagios/brokers/npcdmod.o config_file=/etc/pnp4nagios/npcd.cfg"
pynag config --append "broker_module=/usr/lib64/mk-livestatus/livestatus.o /var/spool/nagios/cmd/livestatus"
pynag config --set "process_performance_data=1"

# Add nagios to apache group so it has permissions to pnp4nagios's session files
usermod -G apache nagios

# We need to restart both apache and nagios so new changes take effect
service nagios restart
service httpd restart
service npcd restart
chkconfig npcd on

You should be flying after that.

---
Tommi

RJ

unread,
May 9, 2013, 5:01:55 PM5/9/13
to ada...@googlegroups.com
Alright, I had done that but had a typo in the config.  One more unrelated issue.  When I try and delete a contact group, I get this error.  Thanks for your help!
Warning! [Errno 13] Permission denied: '/usr/share/okconfig/templates/hp/eva/groups.cfg'

Tomas Edwardsson

unread,
May 9, 2013, 5:14:49 PM5/9/13
to ada...@googlegroups.com
Right now there is no way to remove the "built-in okconfig groups". There are 2, eva-contacts and proliant-contacts. I have filed a question on how/if we want to deal with it.

https://github.com/opinkerfi/okconfig/issues/33

If you can live with it being there, it shouldn't cause you any problems.

---
Tommi

Tony B

unread,
Aug 18, 2015, 7:36:09 PM8/18/15
to adagios
I have exactly the same error as RJ.  I have now installed from scratch on CentOS7, then, thinking that the OS may be the problem, I started from fresh on CentOS6.7.  Exactly the same error in both cases.  I have tried running the lines that you detail below, but it basically says I've made no changes and still gives me the error.  I have verified that Nagios itself is running fine.  Obviously I'm missing something simple.  Any thoughts?

T

Páll Sigurðsson

unread,
Aug 20, 2015, 4:15:30 AM8/20/15
to ada...@googlegroups.com
Can you paste the traceback to confirm that it is identical to the one mentioned previously ?

Also, please verify if:
* The file /usr/lib64/mk-livestatus/livestatus.o exists (path could be different on centos7)
* The file /var/spool/nagios/cmd/livestatus exists
* That nagios is running, if it is not running, take a look at error messages in nagios.log to determine root cause.


For more options, visit https://groups.google.com/d/optout.

Tony B

unread,
Aug 20, 2015, 2:06:26 PM8/20/15
to ada...@googlegroups.com
I can't, actually, as I no longer have the VM that had the error.  I ended up completely rebuilding the machine, and set it up with one minor change in my install.  I installed nagios and nagios-plugins-all from standard repos, rather than ok-release, then installed adagios, mk-livestatus and okconfig from ok-release.  Not sure why, but it now works.  Presumably there is a bug in the version that's on ok-release.

Thanks for your response, though.

--
You received this message because you are subscribed to a topic in the Google Groups "adagios" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/adagios/AKfWPqb9rxM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to adagios+u...@googlegroups.com.

Nick M

unread,
Jan 29, 2016, 4:09:24 PM1/29/16
to adagios
I'm getting the same error with the status tab. I have the livestatus.o where you mentioned and nagios is running, but as for /var/spool/nagios/cmd/livestatus that doesn't exist.  Followed the install guide here: https://github.com/opinkerfi/adagios/wiki/Install-guide and installed it on Centos 7.  This is the traceback:
Traceback (most recent call last):

 
File "/usr/lib/python2.7/site-packages/adagios/views.py", line 43, in wrapper
    result
= view_func(request, *args, **kwargs)
 
File "/usr/lib/python2.7/site-packages/adagios/status/views.py", line 650, in status_index
    c
= adagios.status.utils.get_statistics(request)
 
File "/usr/lib/python2.7/site-packages/adagios/status/utils.py", line 454, in get_statistics
   
*arguments
 
File "/usr/lib/python2.7/site-packages/pynag/Parsers/livestatus.py", line 1116, in get_services
   
return self.query('GET services', *args, **kwargs)
 
File "/usr/lib/python2.7/site-packages/pynag/Parsers/multisite.py", line 80, in query
    query_result
= backend_instance.query(query, *args, **kwargs)
 
File "/usr/lib/python2.7/site-packages/pynag/Parsers/livestatus.py", line 973, in query
    livestatus_response
= self.write(livestatus_query.get_query())
 
File "/usr/lib/python2.7/site-packages/pynag/Parsers/livestatus.py", line 820, in write
    livestatus_socket
= self._get_socket()
 
File "/usr/lib/python2.7/site-packages/pynag/Parsers/livestatus.py", line 804, in _get_socket
   
raise ParserError(msg % (e, self.livestatus_socket_path))

ParserError: "[Errno 2] No such file or directory while connecting to '/var/spool/nagios/cmd/livestatus'. Make sure nagios is running and mk_livestatus loaded."

In the nagios.log file, I notice this:
[1454100262] Error: Could not load module '/usr/lib64/mk-livestatus/livestatus.o' -> /usr/lib64/mk-livestatus/livestatus.o: undefined symbol: last_command_check
[1454100262] Error: Failed to load module '/usr/lib64/mk-livestatus/livestatus.o'.
[1454100262] Error: Module '/usr/lib64/nagios/brokers/npcdmod.o' is using an old or unspecified version of the event broker API.  Module will be unloaded.
[1454100262] Event broker module '/usr/lib64/nagios/brokers/npcdmod.o' deinitialized successfully.
[1454100262] Error: Failed to load module '/usr/lib64/nagios/brokers/npcdmod.o'.
[1454100262] Error: Module loading failed. Aborting.

Páll Sigurðsson

unread,
Jan 31, 2016, 9:04:50 AM1/31/16
to ada...@googlegroups.com
Nick, seems like the versions of mklivestatus and pnp4nagios that you have installed are both incompatible with the version of nagios you have installed. 

Adagios relies on both of these to be working (livestatus for status information and pnp4nagios for graphs), but otherwise there is not a whole we can do from adagios perspective, other than get the dependencies up and running.

Start by checking mklivestatus documentations on supported versions, I haven't looked at it for months, but last time I knew, they only supported nagios3 and did not plan to support nagios4 because it didn't provide a lot of new features except the api breakage. 

arthur sherman

unread,
Mar 12, 2016, 6:17:21 PM3/12/16
to adagios
i'm also getting this error but w/ failure to load livestatus.o in nagios.log
i'm running on debian 8 (jessie).
on a previous successful install during june-15, i used the op5 fork of mk-livestatus.
it seems to have disappeared though. on the op5 site, there r references to it, but access attemps to the page
yields:
Not Found

this is rather discouraging.
anyone know of a way around this?
-ams
Reply all
Reply to author
Forward
0 new messages