> Graeme Hinchliffe <[EMAIL PROTECTED]> wrote: > > The radiusd runs happily. mysqldump starts and radiusd complains > > about unresponsive children, the number of threads increases until > > the mysqldump finishes, at which point the number of threads begins > > to drop. The no of threads gets to about 20 (initial start value is > > 5).. at which point the daemon locks up and consumes lots of CPU. > > It has to be kill -9'd to stop and then restart. > > You're hitting a border case in the server, where it doesn't behave > well. Using huge amounts of CPU is bad, but when the MySQL db > disappears entirely (due to the mysqldump), you've guaranteed that the > server can't process any more requests.
It doesn't dissapear, just is unwritable, and perhaps slowed down. When I have been watching the logs as the process is run, I see authentication requests continuing, along with unresponcive child processes. When the dump finishes there is a burst of radacct data/errors and then the radiusd failes and goes into it's unresponsve state. -- ----- Graeme Hinchliffe (BSc) Core Team Member Zen Internet (http://www.zen.co.uk) ICQ 3842605 (link) Direct: 0845 058 9074 Main : 0845 058 9000 Fax : 0845 058 9005 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
