I see this query timeout issue quite often. I have a 4 system sql replication ring though, so it just moves onto the next one and keeps humming. not sure what's causing the timeout though.
On 20/11/12 04:33 PM, Heikki Vatiainen wrote: > On 11/20/2012 02:27 PM, Ricardo Martinez wrote: >> Is there a way to mark the DB SQL as down in the configuration file, maybe >> with a PostHook? Or something like that? > Currently DB query timeout can not be trapped with a hook. Have you had > problems with the DB timing out queries while still allowing connections? > > I'd like to know how common this problem is. > > Thanks, > Heikki > > >> Regards, >> Ricardo.- >> >> -----Mensaje original----- >> De: Ricardo Martinez [mailto:rmarti...@redvoiss.net] >> Enviado el: lunes, 19 de noviembre de 2012 18:50 >> Para: 'Heikki Vatiainen'; 'radiator@open.com.au' >> Asunto: RE: [RADIATOR] SQL Timeout >> >> There is also other post about the same issue : >> >> http://www.open.com.au/pipermail/radiator/2011-April/017237.html >> >> >> >> -----Mensaje original----- >> De: Ricardo Martinez [mailto:rmarti...@redvoiss.net] Enviado el: lunes, 19 >> de noviembre de 2012 18:36 >> Para: 'Heikki Vatiainen'; 'radiator@open.com.au' >> Asunto: RE: [RADIATOR] SQL Timeout >> >> Is there another more safe way to do the BackOff. What I'm trying to do >> is when a SQLquery is Timeout by Radiator mark the server as "down" and do >> the next AuthBy Clause. >> I saw a pair of question about the same issue near 2002 : >> http://www.open.com.au/pipermail/radiator/2002-October/005289.html >> >> Please help me here. >> >> I'm using : >> Radiator 4.9 >> perl, v5.10.1 (*) built for x86_64-linux-thread-multi DBI : 1 .622 >> DBD:mysql 4.022 >> >> Regards, >> Ricardo.- >> >> >> -----Mensaje original----- >> De: radiator-boun...@open.com.au [mailto:radiator-boun...@open.com.au] En >> nombre de Heikki Vatiainen Enviado el: lunes, 19 de noviembre de 2012 >> 18:21 >> Para: radiator@open.com.au >> Asunto: Re: [RADIATOR] SQL Timeout >> >> On 11/19/2012 10:47 PM, Ricardo Martinez wrote: >> >>> Question : When it says ".Radiator will wait for when trying to >>> contact the SQL server." this means that a */select/* is a CONTACT??? >> Hello Ricardo, >> >> there is a contact before the select. The contact succeeds but the >> subsequent query (DELYREQ) times out. Since it was the query that returned >> error and not the contact just before it, FailureBackoffTime is not >> triggered. >> >>> So, I don't understand why the Radiator is not doing the Backoff. >> If you make the DB contact to block, for example using iptables to drop >> traffic destined to the DB, it will then time out the connection attempt. >> When this happens you will see it start the backoff timer. >> >> Thanks, >> Heikki >> >> -- >> Heikki Vatiainen<h...@open.com.au> >> >> Radiator: the most portable, flexible and configurable RADIUS server >> anywhere. SQL, proxy, DBM, files, LDAP, NIS+, password, NT, Emerald, >> Platypus, Freeside, TACACS+, PAM, external, Active Directory, EAP, TLS, >> TTLS, PEAP, TNC, WiMAX, RSA, Vasco, Yubikey, MOTP, HOTP, TOTP, DIAMETER >> etc. Full source on Unix, Windows, MacOSX, Solaris, VMS, NetWare etc. >> _______________________________________________ >> radiator mailing list >> radiator@open.com.au >> http://www.open.com.au/mailman/listinfo/radiator >> > _______________________________________________ radiator mailing list radiator@open.com.au http://www.open.com.au/mailman/listinfo/radiator
