Solved When is the nginx error 53300 too many clients error going to be resolved?

[us1]

Despite all the updates, patches, etc., the Debian installs of 3cx continue to periodically require a reboot because the auto backups will fail to run with the dreaded error:

3CX Phone System tried to backup but failed due to the following reason(s):
System.Exception: Error creating backup ---> System.AggregateException: One or more errors occurred. (53300: sorry, too many clients already) ---> Npgsql.PostgresException: 53300: sorry, too many clients already

Any idea when this will be resolved? This occurs on all of 8 of my Debian 3cx installs (all v15.5.whatever). I understand it is nginx throwing the error, but certainly there is a way to resolve this. I really don't want to have to schedule a weekly reboot to keep this from happening. I prefer to keep reboots to only when absolutely required for maximum up-time and just general good practice.

 

[Sopock]

Maybe they can't reproduce it?

It appear that some component of 3CX may not be closing connections after some operation(s) and eventually the concurrent connection count is exceeded.

SELECT * FROM pg_stat_activity

 

[Matt Waechter]

I have had several servers do this recently; only fix is to bounce the server. It's happening to on prem. and cloud servers.

 

[StefanW]

SP2 will solve this and is something which might only occurs after 50 days runtime on linux...
So please restart once more the DB service and by before the next occasion SP2 will be there

 

[us1]

SP2 will solve this and is something which might only occurs after 50 days runtime on linux...
So please restart once more the DB service and by before the next occasion SP2 will be there

Thank you for the update!