Hi all,
However any comments/experience/suggestions to the cause of DB handles
dying are welcome!
== mea culpa! just to make clear: I was using slightly hacked rlm_sql.c
and I did not release the socket when returning from the function...
Milan Holub
holub (at) thenet (dot) ch
Hi Alan,
On Wed, May 16, 2007 at 03:38:27PM +0200, Milan Holub wrote:
== only during (re)-start I'm getting following message:
ERROR: Cannot find a configuration entry for module sql_restart.
== with latest CVS head the garbage ERROR message is no more present
thanks:)
Milan Holub
holub (at)
Hi all,
with cvs head from May 10 I've observed following behaviour(which is
actually hard to debug):
Configuration:
* FreeRADIUS Version 2.0.0-pre0, for host i386-pc-linux-gnu, built on May
10 2007 at 13:56:28
* mysql Ver 14.7 Distrib 4.1.8, for pc-linux-gnu (i386)
* Linux 2.4.26 ,
Hi all,
On Wed, May 16, 2007 at 02:05:09PM +0200, Milan Holub wrote:
Currently the only thing which helps is to restart freeradius. It
creates the DB handles again and works fine for another several hours up to
days...
I have following nasty workaround which react on rlm_sql module
Milan Holub wrote:
...
Then every occurence of sql module call I've replaced by following
configurable failover section:
See the virtual modules in radiusd.conf. You can put that entry
there as group sql_restart. Then, replace sql in
authorize/accounting with sql_restart.
It's a little
Hi Alan,
On Wed, May 16, 2007 at 02:50:27PM +0200, Alan Dekok wrote:
See the virtual modules in radiusd.conf. You can put that entry
there as group sql_restart. Then, replace sql in
authorize/accounting with sql_restart.
It's a little simpler...
== thanks for the tip, it's working and
6 matches
Mail list logo