buffered-sql detail

[Gabriel Blanchard]

On 5-Aug-09, at 1:18 PM, Gabriel Blanchard wrote:
> Alright well it appears to be working now. I did need to use 2.17 as
> you pointed out. 2.1.6 did not log with the exact same config.
>
>
I may have found a problem with the detail server. While I was  
rebooting the SQL server that Freeradius connects to, it stopped  
responding to any new radius query.
I thought that the point of the detail/buffered-sql server was to  
decouple the accounting logging from everything else. My auth config  
does not use SQL (local users file) so it should not lock.

Thu Aug  6 10:42:24 2009 : Error: rlm_sql_unixodbc: SQL down 08S01  
[unixODBC][FreeTDS][SQL Server]Write to SQL Server failed.
Thu Aug  6 10:42:24 2009 : Info: rlm_sql_unixodbc: rlm_sql will  
attempt to reconnect
Thu Aug  6 10:42:24 2009 : Debug: rlm_sql (tsisql02): Attempting to  
connect rlm_sql_unixodbc #12
<--- 1 minute delay, during that time radius was not responding.
Thu Aug  6 10:43:41 2009 : Error: rlm_sql_unixodbc: SQL down 08S01  
[unixODBC][FreeTDS][SQL Server]Server is unavailable or does not exist.
Thu Aug  6 10:43:41 2009 : Error: rlm_sql_unixodbc: Connection failed
Thu Aug  6 10:43:41 2009 : Error: rlm_sql (tsisql02): Failed to  
connect DB handle #12
Thu Aug  6 10:43:41 2009 : Error: rlm_sql (tsisql02): reconnect  
failed, database down?
Thu Aug  6 10:43:41 2009 : Error: [tsisql02] Couldn't update SQL  
accounting ALIVE record -
Thu Aug  6 10:43:41 2009 : Debug: rlm_sql (tsisql02): Released sql  
socket id: 12
Thu Aug  6 10:43:41 2009 : Info: ++[tsisql02] returns fail

I'm assuming that sql_init_socket may need to have some kind of  
timeout. Or at least initializing a socket shouldn't lock up the  
entire server.