Hello, 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 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 Mon Apr 11 02:41:33 2016 : Auth: (62) Login OK: [xxxxxx] (from client xxxxxxx port 0) 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. My settings I think are related, and if I forgot some, please kindly ask and ye shall receive. radiusd.conf extract - start_servers = 5 max_servers = 32 min_spare_servers = 10 max_spare_servers = 15 max_requests_per_server = 0 auto_limit_acct = no from sql mod start = ${thread[pool].start_servers} # Minimum number of connections to keep open min = ${thread[pool].min_spare_servers} max = ${thread[pool].max_servers} spare = ${thread[pool].max_spare_servers} uses = 0 retry_delay = 30 lifetime = 0 idle_timeout = 90 We do not have a very busy radius, its for VPN and its rare everyone logs in at once, we have currently two access servers, but soon will have one on other states, so could be five in total by mid year. Are my radiusd,c.onf settings overkill and this is why the logs fill up with these errors? Would anyone have more suitable settings advice? Thank you. Lozza