Distributed nagios system

[John Longland]

-----Original Message-----
From: nagios-users-bounces at lists.sourceforge.net
[mailto:nagios-users-bounces at lists.sourceforge.net]On Behalf Of Bryan
Loniewski
Sent: 27 September 2006 21:39
To: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Distributed nagios system


> Message: 3
> Date: Wed, 27 Sep 2006 11:11:23 +0200
> From: John Longland <jlongland at grintek.com>
> Subject: [Nagios-users] Distributed nagios system
> To: "'nagios-users at lists.sourceforge.net'"
>       <nagios-users at lists.sourceforge.net>
> Message-ID:
>       <510595ECCFAEFC44941F5EDA4324F275011F9B84 at gtmail.Grintel.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi all !!
>
> I've had to implement a distributed systemand I have gone through some
docs
> I found on sourceforge.
>
> I'll briefly mention what I have done:
>
> slave nagios
> 1. Installed the nsca pack
> 2. put send_nsca.cfg  -> /etc
> 3. modified entry for ocsp_sommand in nagios,cfg
> 4. enabled obesess over services
> 5. enable_notifications set to 0
> 6. Defined a command called submit_check_result in my minimal.cfg
> 7. Written submit_check_result script and placed it in ../libexec
>
> server side:
> 1. Installed nsca pack
> 2. nsca,cfg -> /usr/local/nagios/etc
> 3. active service checks 1 for services checked from main nagios
>      set to 0 for service checked from slave nagios
> 4. externetl commands checks enabled
> 5. passive service checks enabled
> 6. nsca -> /usr/local/nagios/bin
> 7. check existance of  /usr/local/nagios/var/rw/nagios.cmd
> 8. wrote nsca script in  /etc/xinetd.d
> 9. added entry in /etc/services  called NSCA
> 10. restarted xinetd
>
>
> Problem.
> When I send info from slave to main nagios by hand, it is sent and
> reported by the main nagios, correctly.
> When I remove /usr/local/nagios/libexec/submit_check_result, I get an
error
> indicating that the slave
>    nagios is trying to execute a non-existing script.
> When I re-instate the submit_check_result script, nothing happens. No
error
> in any log.
> I do not see any attempt on the network ( tcpdump) that the slave is
trying
> to contact the main
> nagios.
> I have also added a little echo statement in the submit_check_result
script
> that writes to a file.

A few questions:

What version of nagios are you running? 
When you added the echo statement was IT the only thing in the script?
or did you leave the rest of the script intact? 
What are the permissions of the directories, files of where your 
submit_check_result script is? 
Did you try running the script by hand as the user nagios runs under?

PS: Give an example of what your submit_check_result script looks like.

Hi Bryan !!!

Thanks for your mail. 

I have since dicovered that the problem was the permissions of
my send_nsca.cfg file !! For completeness:
Version of nagios is 2.4
The echo statement was simply added with all other statements intact
The permissions of the script files are readable and executable
by anyone. It is owned by nagios:nagios.
As I said above, I slipped up with not checking the send_nsca.cfg file !!!

Thanks for your time, Bryan. Much appreciated !!!!
John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20060928/2c4e4eaf/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
-------------- 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