We had a similar problem, with radius dying every night. The problem was that our db backup script was tying up mysql (missing "-q" or something) and radiator was hanging trying to execute it's queries.
I'm going to guess that this is what's happening with both of your systems, though maybe not on the backup as it was with ours. I would look at your mysql setup. Can you beef up your mysql setup? -Peter Utku Er wrote: > I have nearly the same problem... I am using radiator 3.0 on linux 2.4.7-10, >redhat 7.2 with freetds to connect to SQL database on win2000.. It works fine but it >goes down without any error messages... 20-30 times a day. I have trace 4 open in my >config. I see every kind of packet coming and going but it does not write anything to >the log before it goes down... I wrote a script to restart it AND it mails me the >latest 100 lines of log before it starts it again... I search every one of that mails >and I see it only get stuck with the SQL queries... I debug also the SQL and see some >requests are delayed for 1 (max 1.4) seconds... > -- Peter Moody Systems Administrator [EMAIL PROTECTED] :wq === Archive at http://www.open.com.au/archives/radiator/ Announcements on [EMAIL PROTECTED] To unsubscribe, email '[EMAIL PROTECTED]' with 'unsubscribe radiator' in the body of the message.
