check_radius

[nagios at acmecargo.com]

For future reference (archival reasons) I had to do the following to get 
this to work:

1. edit my /etc/radiusclient/radiusclient.conf file to show the appropriate 
authserver. If you do not have a /etc/radiusclient directory, you will need 
to install the radiusclient and libraries (which you probably already did 
if you got the check_radius plugin to install in the first place.

2. add the following to the checkcommands.cfg file:

# 'check_radius' command definition
define command{
         command_name    check_radius
         command_line    $USER1$/check_radius -H 209.208.xxx.xxx -F 
/etc/radiusclient/radiusclient.conf -u username at domain.dom -p userpass -P 
1812 -t 10
         }

I'm sure you could just pull in the ARGs from the services.cfg file but 
this worked fine for me.

3. then of course add the check in the services.cfg file.

I was able to run the
check_radius -H 209.208.xxx.xxx -F /etc/radiusclient/radiusclient.conf -u 
username at domain.dom -p userpass -P 1812
command from the command line with the result "Auth OK". Even though it 
seems the -P (port) option isn't required, if you don't add it, you will 
get fussed at.

Dylan


At 07:49 PM 9/4/2003, you wrote:

>nagios at acmecargo.com wrote:
>
> > I'm having trouble getting the check_radius to work. The
> > following is --help:
> >
> > check_radius -H host -F config_file -u username -p
> > password'              [-P port] [-t timeout] [-r retries] [-e expect]
> >
> > Is the ' after password a typo?
>
>If there is only one, yeah. You should probably put quotes around the whole
>password though. Otherwise, you'll run into trouble with passwords that
>contain characters which are recognized as special by the shell.
>
>
> > What about the blank space before the port option?
>
>That will likely work with or without the space.
>
>
> > The help makes it sound like the config_file is
> > optional but when I try to manually invoke the
> > command without the config_file, it doesn't work
> > and comes back saying "Config file error".
>
>It's a common convention to show optional arguments in square brackets (such
>as [-P port] above) and to show mandatory options without any brackets.
>Based on that, I'd say that the "-F config_file" argument is mandatory
>according to the documentation you pasted above.
>
>-j
>--
>Jeremy Madea
>Senior Systems Engineer
>MDL Information Systems



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
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