Re: FW: Help! Cistron major failure in production! (fwd)

I have had similar problems in the past like this. First place I normally look is at things that have changed. In your case the users file, configs What I would try is building a basic users file from scratch. One that you know will defently work see what happens from there. I found once that a profile that had a syntax error and managed to stuff the rest of them up. The radius server had failed to tell me that there was a syntax error and continued on its way denying every user it could. I bascaully put in a DEFAULT profile and worked backwards until I found the problem. This was using Merit Radius mind you, infact the free one :-) Give it a try, it might shed some light on your problem. Simon Allard (Senior Tool Monkey) IHUG Ph (09) 358-5067 Email: simon.allard(a)staff.ihug.co.nz "There is no spoon"

Anyone had any experience with cistron radius? I'm suffering some sort of major magic weridy problem, if anyone has any ideas.

--- Matt Camp

---------- Forwarded message ---------- Date: Wed, 25 Jul 2001 17:24:51 +1200 (NZST) From: Matt Camp To: cistron-radius(a)lists.cistron.nl Subject: Help! Cistron major failure in production!

I run a network of 4 cistron 1.6.3 servers on FreeBSD machines.

This afternoon, all 4 of them stopped responding. Its as like the radiusd process isn't running. Neither our lucent NAS gear, radtest, or the various people who have proxys pointed at our servers get any response at all.

The server logs, and console when running in -xxx mode show that the server starts, and then is just waiting for connections.

Every 5 minutes, i propagate a new raddb/users file out from a central host. This system has worked fine for around 18 months now.

On _ONE_ of the servers, if i restart it (totally. Kill and restart radiusd), the log shows "Wed Jul 25 17:21:38 2001: Info: Starting - reading configuration files ...", then there is nothing for approximately 4 minutes, after which it appears to process all the requests that have been sent to it during that time. (of course, most of them actually fail in reality since the NAS has long since dropped the call).

Then it will run fine, up until it detects a new users file, and reloads the config files, at which point its back into total non-responsiveness until i manually restart it.

This only works on one server. The other 3 don't come back at all, even after a restart.

ANd they're all on the same config. (Which i rsync to them after making a change)

radtest tests from localhost which normally work fine just act exactly as if the radiusd process isn't even running.

I've tried everything i can think of, including the microsoft approach of power-cycling all machines involved. Load averages are normal, disk space is fine. Heaps of memory available.

File descriptor loads seem ok, in that there are only around 100 or so connections to each box in total. (for the other services they run)

Any ideas? This is urgent... I've got thousands customers who can't log in right now.

--- Matt Camp

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

--------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog