I'm seeing the same thing here with 1.1.1.
I have 2 servers with identical hardware/software configs.
Both servers "hang" at the same time.
stopping/starting the daemon doesn't resolve the issue, rebooting the box
does.
I was assuming it had something to do with the sql module because that is
where it paused (see: sql hangs, was (conflicts/duplicates need))
----- Original Message -----
From: "King, Michael" <[EMAIL PROTECTED]>
To: "FreeRadius users mailing list" <freeradius-users@lists.freeradius.org>
Sent: Thursday, March 23, 2006 9:24 AM
Subject: Version 1.1.1 stops responding
So I built 1.1.1 on Debian.
After a period of so many hours (variable) it stops responding.
(Sometimes 2hours, sometimes 16hours)
Now here's where it get's weird, (and makes me suspect it might not be
freeRADIUS at the root cause)
If I stop and restart the freeRADIUS service, it continues to ignore
RADIUS packets.
But if I restart the server (hard reboot) it works fine. Till it stops
responding again.
Obviously this is not enough information to help you diagnose the
problem. How do I gather that information?
The box is a 233 Pentium with 64 megs of ram. Has about 15 AP's, with
around 100 users (not simultaneous, maybe 30 simultaneous)
So what's the suggested way of gathering more info? Running debug mode
piping to a text file?
-
List info/subscribe/unsubscribe? See
http://www.freeradius.org/list/users.html
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
