RADIUS Monitoring tool

Matthew Newton mcn4 at leicester.ac.uk
Wed Feb 25 23:24:27 CET 2015


On Wed, Feb 25, 2015 at 01:44:05PM -0500, Arran Cudbard-Bell wrote:
> 
> > On 25 Feb 2015, at 12:29, A.L.M.Buxey at lboro.ac.uk wrote:
> > 
> > we use NAGIOS and have some local eapol_test scripts
> > formonitor/alerts and use'monit' to check status of the radius
> > process and restart it when dead
> 
> You don't need a monitoring solution.

What planet are you visiting from? ;-)

Maybe this would be ok, though:

  sql {
  	fail = 1
  }
  if (fail) {
  	do_not_respond
    send_admin_emails_until_this_broken_mess_is_fixed
  }

> Do that for all modules critical to authentication.

It fixes the problem of NASes hanging onto a RADIUS server that's
broken, sure. But doesn't help you know that you need to fix it!

OTOH, anything but monit. My experiences has been along the lines
of "is that service running? Oh great, let's restart it just in
case." Hence replaced by a very small shell script!

Cheers,

Matthew


-- 
Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>


More information about the Freeradius-Users mailing list