(RADIATOR) no timeout on database query

Nick Rogness nick at rogness.net
Tue Jan 22 11:18:22 CST 2008

On 1/21/08, Ruud Besseling <ruudb at kpn.net> wrote:
> Hello,
> We use a mysql database to save all accounting data. Normally when the
> database is not available the insert query
> times out, the data is saved in a local file and radiator is ready for
> the next request.
> However, when the network interface of the database server is going down
> unexpectedly, the timeout does not occur
> and radiator hangs.
> Has anyone experienced the same problems and -more important- does
> anyone have a solution?
> We are using Radiator 3.13, MySQL 5.0.41, DBI 1.6 and DBD 4.005
> We use several servers and on each server there are several accounting
> radius processes running.


I have experienced this same problem for years with Radiator including and
upto 3.13 with Mysql5.0 and MySQL5.1.  If the database server goes away or
takes time to complete in the middle of a SQL execution statement, the
server hangs (blocks) and the socket queue fills up.  My advise to you is,
don't let it happen.  A significant amount of tuning needs to be done if you
are dealing with a lot of Radius requests.

I do not know how much Hugh and crew can do to help you out as I think it is
probably a limitation of Perl DBI/DBD.

Haven't tried this in v4.0 yet.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20080122/de2b222f/attachment.html>

More information about the radiator mailing list