2.1.11 inexplicable crash
Hello, After upgrading to FreeRadius version 2.1.11 on RHEL6, I am seeing the following in radius.log right before the process terminates: Wed Sep 28 11:16:12 2011 : Error: Child PID 30242 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:12 2011 : Error: Child PID 30243 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:12 2011 : Error: Child PID 30244 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30245 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Info: Signalled to terminate Wed Sep 28 11:16:13 2011 : Info: Exiting normally. Wed Sep 28 11:16:13 2011 : Error: Child PID 30246 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Request 179116 has been waiting in the processing queue for 8 seconds. Check that all databases are running properly! Wed Sep 28 11:16:13 2011 : Error: Child PID 30247 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30251 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30252 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30249 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30253 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30255 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30250 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30248 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:13 2011 : Error: Child PID 30254 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:14 2011 : Error: Child PID 30257 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:14 2011 : Error: Child PID 30256 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:14 2011 : Error: Child PID 30258 is taking too much time: forcing failure and killing child. Wed Sep 28 11:16:14 2011 : Error: Child PID 30259 is taking too much time: forcing failure and killing child. The radiusd process ends, and I can't find anything to explain this. I've restarted the service with -X and will report back if I see anything suspicious. In the meantime, has anyone else seen this? Thanks, Dave -- View this message in context: http://freeradius.1045715.n5.nabble.com/2-1-11-inexplicable-crash-tp4849607p... Sent from the FreeRadius - User mailing list archive at Nabble.com.
DaveA wrote:
After upgrading to FreeRadius version 2.1.11 on RHEL6, I am seeing the following in radius.log right before the process terminates: ... Wed Sep 28 11:16:13 2011 : Error: Request 179116 has been waiting in the processing queue for 8 seconds. Check that all databases are running properly!
FIX THAT. Nothing else will solve the problem. You are sending the server more packets than it can handle. Alan DeKok.
Hi Alan, Thanks for your fast response. By server, do you mean FreeRadius or the back end? Dave -- View this message in context: http://freeradius.1045715.n5.nabble.com/2-1-11-inexplicable-crash-tp4849607p... Sent from the FreeRadius - User mailing list archive at Nabble.com.
Not enough. The log saying database and you saying server doesn't help me either. This single server uses different databases depending on the request. Currently ldap, AD and flat files. Nothing has changed except the version I'm using. Dave -- View this message in context: http://freeradius.1045715.n5.nabble.com/2-1-11-inexplicable-crash-tp4849607p... Sent from the FreeRadius - User mailing list archive at Nabble.com.
DaveA wrote:
Not enough. The log saying database and you saying server doesn't help me either.
I suppose words like "server" and "database" aren't clear enough.
This single server uses different databases depending on the request. Currently ldap, AD and flat files. Nothing has changed except the version I'm using.
Then the solution is obvious, isn't it? Alan DeKok.
The solution was to reduce the amount of logging and add another CPU to the VM. Thanks. -- View this message in context: http://freeradius.1045715.n5.nabble.com/2-1-11-inexplicable-crash-tp4849607p... Sent from the FreeRadius - User mailing list archive at Nabble.com.
participants (2)
-
Alan DeKok -
DaveA