On Wed, Feb 25, 2015 at 05:48:00PM -0500, Arran Cudbard-Bell wrote:
You just scrape the logs from the NAS looking for "can't contact RADIUS server messages" :)
Heh. I call that a monitoring solution :)
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!
Oh pfft. Monit works fine... ish.
Very much "ish". Maybe I just totally failed configuring it (for both RADIUS and DHCP servers), but my shell script has been a) much simpler and b) reliable. I'm all for that any day. I wasn't joking about monit deciding to restart (actually, stop) services just because it felt like it. I scrapped it when it couldn't cope with simple logic.
Munin is a fun one, i've had one hung RADIUS instance take down all monitoring for the box. I guess thats our fault though, for not implementing a read timeout in radmin.
Don't generally have a problem with munin itself. It's one of my first turn-to things for checking what a system was doing, and invariably useful. Always find the plugin collection a total mess, though. Again, that could just be me.
Suppose I should go and fix that *grumble*.
Maybe. A monitoring solution should be able to cope with that sort of thing. Matthew -- Matthew Newton, Ph.D. <mcn4@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@le.ac.uk>