(RADIATOR) SessionDatabase failover problems

[Ken McKittrick]

Hello

We're having a problem with the SessionDatabase failover function. Our 
setup is 3 radius servers using 2 MySQL database servers. If the 
primary database server is "wedged" (like the hard drive is full), the 
SessionDatabase function <doesn't> timeout and failover to the backup 
database server. Radius just sits there and doesn't process radius 
packets or log or anything. Actually stopping the mysql database does 
clean things up a bit.

So the SessionDatabase handles "down" sql database servers fine, but 
not "wedged" ones. I know you're not supposed to let a Database servers 
filesystem fill up.

What can I do for Radiator to handle this more gracefully?

Thanks
Ken McKittrick
ISP Engineer
USADatanet

--
Archive at http://www.open.com.au/archives/radiator/
Announcements on radiator-announce at open.com.au
To unsubscribe, email 'majordomo at open.com.au' with
'unsubscribe radiator' in the body of the message.