radrelay (mode) from cvs head

[Michael Griego]

On Oct 9, 2006, at 8:01 AM, Peter Nixon wrote:

> In multi threaded mode we constantly get:
>
> Mon Oct  9 15:48:46 2006 : Info: rlm_sql (sql-acct): There are no  
> DB handles
> to use! skipped 0, tried to connect 0
> Mon Oct  9 15:48:46 2006 : Info: rlm_sql (sql-acct): There are no  
> DB handles
> to use! skipped 0, tried to connect 0
> Mon Oct  9 15:48:46 2006 : Info: rlm_sql (sql-acct): There are no  
> DB handles
> to use! skipped 0, tried to connect 0


I just recently started switching from a MySQL backend to a  
PostgreSQL backend, and I'm getting these as well now.  Something,  
IMO, seems to be up with the PGSQL module code as I don't recall  
having this problem with the MySQL backend.  The symptoms at the  
moment are the server will leak memory like crazy, and I'll start  
getting the above when enough memory has been leaked that the disk  
starts going crazy swapping pages in and out, causing the PGSQL  
processes to stay in an iowait state until they can get a shot at the  
disk.

I have 2 SQL modules, one for autz, which is running against a Slony  
slave/replica database that FR only ever performs SELECTs on, and ane  
for accounting.  I start seeing the above against my autz database.   
I upped the number of SQL sockets for that module to 10, but it  
didn't really do anything since the real problem seems to be the  
leak, and running out of sockets is only really a symptom brought on  
by disk activity.  MySQL only ever had the default 5 sockets, and it  
had no problem keeping up.  The tables are, of course, properly  
indexed and tested for query speed.

Like I said, my current suspicion is something in the  
rlm_sql_postgresql module code, maybe a per-query leak, but I'm not  
sure.

Oh, and this is all with the CVS HEAD.

--Mike