Nagvis 1.5.1 installation question

[Kaplan, Andrew H.]

Hi there --

I am going through the motions of installing NagVis 1.5.1 onto our Nagios 3.1.2
server. I have completed the installation of the 
check_mk 1.1.6p1 software, and made sure to select the default settings for it.
When I run the install script for NagVis, all 
prerequisites are found, and I make sure to select mklivestatus as the Backend.
However, when the installer gets to the 
Livestatus Socket, it looks for it in the /usr/local/nagios/rw/live directory,
but says it is missing. 

The installer lists the valid socket formats, and asks me to enter the
MKLivestatus socket. I am not familiar with what that
would be, and whether or not check_mk should be started in daemon mode or in
some other way. 

Can someone provide some insight into this? Thanks.

 


The information in this e-mail is intended only for the person to whom it is
addressed. If you believe this e-mail was sent to you in error and the e-mail
contains patient information, please contact the Partners Compliance HelpLine at
http://www.partners.org/complianceline . If the e-mail was sent to you in error
but does not contain patient information, please contact the sender and properly
dispose of the e-mail.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100730/4a2ff392/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null