1.1.4 stops responding to requests

[Phil Allred]

Just a heads up:  In our production environment here at Brooklyn Law 
School, 1.1.4 stops responding to radius requests after a few hours.  We 
have used freeradius for some time (and love it) to authenticate 
wireless users to our ldap servers.  We use it with two different 
wireless systems, trapeeze and colubris, which each do 802.1x 
authentication to freeradius servers using PEAP and mschapv2.  We run it 
on three different servers.  When vista came along, we had to upgrade 
from 1.1.4 to 1.0.5.  We run Fedora Core 5 and Fedora Core 6 on these 
servers.  Because there is no 1.1.4 rpm out yet for Core 5 or Core 6,  
we built freeradius from source.  Since we are in  a production 
environment, we were careful to use non-overlapping directory structures 
when we compiled and installed 1.1.4 so that if there was a problem, we 
could quickly go back to the rpm. 

1.1.4 will run for a few hours and then either stop responding to 
requests or die.   There is no seg fault warning in any log file.  If I 
restart radius, it then begins answering again.  Since it is a 
production environment in which 300-500 users are connected at any given 
time, we were unable to simply turn on debugging and look for problems.  
Once we realized the problem we had to quickly revert to 1.0.5 for now 
and make our relatively few Vista users for a little longer.

I am going to try running it in debug mode over a weekend in a 
particular subset of the school's wireless network where not many users  
would be affected by a crash and see if I can collect any more 
information.  I will do it on a system that never had any earlier 
version of freeradius installed on it, just to be safe.  In the 
meantime, any advice would be appreciated.

Thanks,
Phil Allred