Bug (??) with radius monitoring
"Overes, Carol" <[email protected]> Mon, 16 Dec 2002 10:30:58 +0100
| Newsgroups | gmane.network.netsaint.user |
|---|---|
| Message-ID | <[email protected]> |
All, At this moment I'm monitoring several hosts and services via Netsaint. One of these host is a radius server. Setup: ======= My Netsaint Central Server requests a radius check to a NRPE Server. This NRPE Server forwards this request to the NRPE on the Radius Server. On the Radius Server, a script (not the plugin) "check_radius" is started. The output is returned to the NRPE Server, and then returned to the Netsaint Central Server. Problem: ========= At this moment it works fine for a host called radius1. I have monitor a new radius, called radius2, and this host has the same setup as the radius1. Radius2 uses even the same command as the radius1 for the host and service check. If the Netsaint Central Server initiates a service checke for the radius2, I receive the following error: NRPE: Command 'check_radius_ids_192.168.1.2' not defined Even if I start this command form the prompt of the Netsaint Central Server, it doesn't work. But if I start the command from the NRPE Server towards the radius2, it works. So, this error comes from the NRPE Server, but I have checked the config and this is fine. And this is exact the same setup as radius1, which works fine. Also, I have configured a command for the host check (check_alive_ias). I get a error on this command for the radius2: NRPE: Command 'check_alive_ias_192.168.1.2' not defined If this command is started from the prompt of the Netsaint Central Server, it works. After every adjustment, I have restarted the daemons, but that didn't help. Question: ========== Can somebody shine a light on this story ? I think that this looks like a bug. I have sent the configuration of my servers. BTW: My check interval looks very long, but I have set the interval_length to one second. Regards, Carol Configuration: =============== Netsaint Central Server ++++++++++++++++++++++++ host[radius1]=radius-server 1;192.168.1.1;;check_alive_ias;3;3600;24x7;1;1;1; host[radius2]=radius-server 2;192.168.1.2;;check_alive_ias;3;3600;24x7;1;1;1; service[radius1]=RADIUS;0;24x7;3;600;60;ops-pager;3600;24x7;1;1;1;;check_rad ius_ids service[radius2]=RADIUS;0;24x7;3;600;60;ops-pager;3600;24x7;1;1;1;;check_rad ius_ids serviceescalation[radius1;RADIUS]=2-0;ops-pager,do-service-ias serviceescalation[radius2;RADIUS]=2-0;ops-pager,do-service-ias serviceescalation[radius1;RADIUS]=3-0;service-teamleaders serviceescalation[radius2;RADIUS]=3-0;service-teamleaders command[check_alive_ias]=/opt/APPnetsaint006/libexec/check_nrpe 10.27.211.37 -c check_alive_$HOSTADDRESS$ -to 30 command[check_radius_ids]=/opt/APPnetsaint006/libexec/check_nrpe 10.27.211.37 -c check_radius_ids_$HOSTADDRESS$ -to 30 NRPE Server ++++++++++++ # radius1 command[check_alive_192.168.1.1]=/opt/APPnetsaint/libexec/check_ping 192.168.1.1 100 100 5000.0 5000.0 -p 1 command[check_radius_ids_192.168.1.1]=/opt/APPnetsaint/libexec/check_nrpe 192.168.1.1 -c check_radius -to 30 # radius2 command[check_alive_192.168.1.2]=/opt/APPnetsaint/libexec/check_ping 192.168.1.2 100 100 5000.0 5000.0 -p 1 command[check_radius_ids_192.168.1.2]=/opt/APPnetsaint/libexec/check_nrpe 192.168.1.2 -c check_radius -to 30 NRPE Radius1 +++++++++++++ command[check_radius]=/opt/APPnetsaint/libexec/check_radius NRPE Radius2 +++++++++++++ command[check_radius]=/opt/APPnetsaint/libexec/check_radius ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/