<div><span class="gmail_quote">On 1/21/08, <b class="gmail_sendername">Ruud Besseling</b> <<a href="mailto:firstname.lastname@example.org">email@example.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hello,<br><br>We use a mysql database to save all accounting data. Normally when the<br>database is not available the insert query
<br>times out, the data is saved in a local file and radiator is ready for<br>the next request.<br><br>However, when the network interface of the database server is going down<br>unexpectedly, the timeout does not occur<br>
and radiator hangs.<br><br>Has anyone experienced the same problems and -more important- does<br>anyone have a solution?<br><br><br>We are using Radiator 3.13, MySQL 5.0.41, DBI 1.6 and DBD 4.005<br>We use several servers and on each server there are several accounting
<br>radius processes running.</blockquote>
<div>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.
<div>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.</div>
<div>Haven't tried this in v4.0 yet.</div>