<div>I´m testing Nagios NRPE and I´m finding serveral problems.</div> <div> </div> <div>I´m working with:</div> <div>- Nagios 2.9 on Solaris 9 (last CVS patch).</div> <div>- NRPE 2.8.1 on Solaris 8 (last CVS patch).</div> <div>- gcc 3.4.6</div> 1) When I try to start a daemon using NRPE, I receive the message "CHECK_NRPE: Socket timeout after 10 seconds.", although the service is started. > check_nrpe -H <remote_machine> -n -p 5666 -c start_daemon CHECK_NRPE: Socket timeout after 10 seconds. In the remote machine I have in the nrpe.cfg: command[start_daemon]=/usr/local/bin/sudo /usr/local/nagios/bin/teste_daemon My teste_daemon is: ---------------------------------------- #!/usr/bin/perl use POSIX; chroot("/usr/local/nagios/bin") or die "Couldn't chroot: $!"; $pid = fork; if ($pid) { print "OK\n"; exit 0; } die "Couldn't fork: $!" unless defined($pid); POSIX::setsid() or die "Can't start a new session: $!"; while (1) { sleep 10; } exit 0; ------------------------------------------- It seems that the NRPE waits an output message from the teste_daemon that does not come (?!). 2) When I try to check a process using the plugin "check_procs" via NRPE the number of process running is added by one. Example: > check_nrpe -H <remote_machine> -n -p 5666 -c check_daemon PROCS CRITICAL: 2 processes with args 'teste_daemon' In the nrpe.cfg, I have: command[check_daemon]=/usr/local/nagios/libexec/check_procs -c 1:1 -a teste_daemon But, when I run "check_procs -c 1:1 -a teste_daemon" on the remote machine, I have: PROCS OK: 1 process with args 'teste_daemon' The "solution" was to change the command to "check_procs -c 1:1 -p 1 -a teste_daemon", but it isn´t what I´m looking for. 3) I couldn´t configure NRPE to run with the inetd. It always answers with a SSL error message, even with the "-n" flag in both side. So I found several problems with NRPE that are difficulting my job. I was intending to put Nagios to monitoring more than 3500 machines but after this problems I don´t know if other people of my group will feel comfortable to use this tool. Thats is a pity, because I found Nagios a excellent monitoring tool, very flexible, but I don´t know if other people will buy the fight to change our actual tool to Nagios.