new connection problem

[Alan DeKok]

On Jan 15, 2026, at 8:26 AM, Can Paçacı <pacaci at servisnet.com.tr> wrote:
> Are you sure it's the database?

  I've been doing this since 1997.  I think I know a little bit about these issues.

  If you're going to ask questions on this list, it would be polite to not argue with the answers.

> I couldn't find any errors/warnings in the database logs for that time period. I also couldn't find anything wrong in the database report.

  That doesn't matter.  The database likely won't log anything if queries are taking 100ms instead of 2ms.  But FreeRADIUS will notice, and it will complain.

  So looking at the database logs doesn't help.  If FreeRADIUS is complaining, then there IS a real problem.  FreeRADIUS doesn't invent random error messages.

  Why do I say this?

  When things are OK, FreeRADIUS sends a small number of queries to the database, and it gets responses quickly.  So you don't see the "sql max connections" error message.

  When the load goes up a lot, FreeRADIUS sends many queries to the database, which overloads it.  So the responses take a long time.  Which means that FreeRADIUS needs to open more connections.  And then you see the "sql max connections" error.

  Since the database is overloaded, increasing the "SQL max connections" configuration won't make the database any faster.  The ONLY solutions here are:

* decrease the number of packets that the server receives
* make the database faster
* stop using the database when the server is overloaded

  Pick one solution, or all of them.

  What isn't a solution is to ignore the advice you get here, and look for some other random solution.  It won't work.  Doing anything else will be just a waste of time.

> I am attaching all relevant radiusd full logs related. Is the "max connection limit" value in the logs below the same max sql pool parameter you're referring to?

  Yes... they all refer to "sql" and "max", so they are all about the "max" connection limit for the "sql" module.

  Alan DeKok.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: Message signed with OpenPGP
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20260115/c3ac57ff/attachment-0001.sig>