rlm_sql logging results

[Alan DeKok]

On Apr 14, 2016, at 10:41 PM, Laura Steynes <laura.steynes72 at gmail.com> wrote:
> I am new-ish to freeradius, sort of stumped with resolving this -
> 
> When a user goes to log on the logs start with
> 
> Mon Apr 11 02:41:33 2016 : Info: rlm_sql (sql): Closing connection (131):
> Hit idle_timeout, was idle for 3600 seconds

  If you don't want that message, change idle_timeout.  Set it to zero so that idle connections are never closed.

> Mon Apr 11 02:41:33 2016 : Warning: rlm_sql (sql): You probably need to
> lower "min"
> Mon Apr 11 02:41:33 2016 : Info: rlm_sql (sql): Closing connection (132):
> Hit idle_timeout, was idle for 3600 seconds
> Mon Apr 11 02:41:33 2016 : Info: rlm_sql (sql): Opening additional
> connection (133), 1 of 32 pending slots used
> Mon Apr 11 02:41:33 2016 : Info: rlm_sql (sql): 0 of 1 connections in use.
> Need more spares
> Mon Apr 11 02:41:33 2016 : Info: rlm_sql (sql): Opening additional
> connection (134), 1 of 31 pending slots used

  The rest of those messages are all a result of the bad setting for idle_timeout.

> now I have lowered min,  I lowered it to several values including yet this
> still logs.
> I have tried more spares, more start/max servers, less servers, nothing I
> do seems to make this thing happy and my boss does not like seeing logs
> fill up with error type messages because he sees it as my failures, and
> rightly so I guess.

  Why not change idle_timeout?

> Are my radiusd,c.onf settings overkill and this is why the logs fill up
> with these errors?

  Because you set idle_timeout incorrectly.  Juts set it to zero.

  Alan DeKok.