[check_radius] Return Code of 137 is out of Bounds

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Marcel Mitsuto Fucatu Sugano
> Sent: Thursday, October 27, 2005 9:03 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] [check_radius] Return Code of 137 is out of
Bounds
> 
> Hi,
> 
> Well, I've setup a check_radius, installed everything (libs, etc.)
> configured radiusclient.conf and servers files, everything is running
> fine, the plugin reports "Auth OK", and if the service or the process
> stops, it alarms as expected. Until something I am missing occurs, and
> suddenly, the plugin begins to report "Return Code of 137 is out of
> bounds". As I've said, everything is running fine until something i am
> missing. Has anyone seen something like this behaviour at all?

What OS is involved? There's this FAQ that might be relevant but less
likely if it works sometimes and not others --

http://www.nagios.org/faqs/viewfaq.php?faq_id=17

Another possibility is that the plugin is receiving a kill -9 (SIGKILL;
128+9=137) while executing.

How's load on the server when this starts happening? Do you have any
processes that kill others for any reason?

When this starts happening, can you run the plugin by hand as the nagios
user as it's specified in your command definition to try to replicate
it? You should echo the exit code after running it by using 'echo $?'.

--
Marc






-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.
Get Certified Today * Register for a JBoss Training Course
Free Certification Exam for All Training Attendees Through End of 2005
Visit http://www.jboss.com/services/certification for more information
_______________________________________________
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