Page 1 of 1

Re: [Nagios-devel] NRPE gives wrong exit codes

Posted: Mon Sep 07, 2009 4:59 pm
by Guest
2009/9/7 Ciro Iriarte :
> 2009/9/7 Hiren Patel :
>>>>> Versions:
>>>>>
>>>>> check_nrpe (from openSUSE Build Service)
>>>>> --------------
>>>>> NRPE Plugin for Nagios
>>>>> Copyright (c) 1999-2008 Ethan Galstad ([email protected])
>>>>> Version: 2.12
>>>>> Last Modified: 03-10-2008
>>>>> License: GPL v2 with exemptions (-l for more info)
>>>>> SSL/TLS Available: Anonymous DH Mode, OpenSSL 0.9.6 or higher require=
d
>>>>> -------------
>>>>>
>>>>> remote NRPE agent (compiled from source)
>>>>> -------------
>>>>> spmon:~ # /usr/lib/nagios/plugins/check_nrpe -H solaris
>>>>> NRPE v2.12
>>>>> ------------
>>>>>
>>>>> Any ideas?, I have a truss capture of the daemon from a working
>>>>> execution and a non-working execution if anyone would like to check
>>>>> them (don't know if attachments are allowed)
>>>>>
>>>
>>> Debug is ON already, but all I get in the logs is the start/stop proces=
s:
>>>
>>> -------
>>> Sep =C2=A07 11:55:48 billbd2 nrpe[11796]: [ID 678021 daemon.notice] Cau=
ght
>>> SIGTERM - shutting down...
>>> Sep =C2=A07 11:55:48 billbd2 nrpe[11796]: [ID 915785 daemon.error] Cann=
ot
>>> remove pidfile '/var/run/nrpe.pid' - check your privileges.
>>> Sep =C2=A07 11:55:48 billbd2 nrpe[11796]: [ID 938771 daemon.notice] Dae=
mon shutdown
>>> Sep =C2=A07 11:55:52 billbd2 nrpe[23649]: [ID 601491 daemon.notice]
>>> Starting up daemon
>>> Sep =C2=A07 11:55:53 billbd2 nrpe[23649]: [ID 627629 daemon.notice]
>>> Warning: Daemon is configured to accept command arguments from
>>> clients!
>>> --------
>>>
>>
>> you have debug=3D1 in your config file? you ran the remote nrpe checks
>> after restarted in debug mode? it should print the command requested and
> Yes
>
>> the results of running the command.
> I don't see that either in the check_nrpe end or on the server logs.
>
>> you're running the 2.12 nrpe server right?
> Yes
>
>> how did you install the nrpe server on solaris, packages or compiled?
> Compiled.
>
>

Apparently is a Solaris service management bug, if I run it manually,
it works in each execution. Also there's another (less critical)
server with more current patches that works just fine.

Regards,


--=20
Ciro Iriarte
http://cyruspy.wordpress.com
--





This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]