View Issue Details

IDProjectCategoryView StatusLast Update
0005319SOGoBackend Generalpublic2021-08-18 12:40
Reportertimonegk Assigned To 
Status newResolutionopen 
PlatformServerOSDebianOS Version9 (Stretch)
Product Version5.0.1 
Summary0005319: Problem with commit 6aca61d: Could not bind to the LDAP server

We are running SOGo with the LDAP authentication backend.
Since we have upgraded SOGo to 5.0.1, we experience an issue similar to
The error message is exactly the same as in the linked issue:

Could not bind to the LDAP server ldap://ldap:389 (389) using the bind DN: cn=sogo,dc=mydomain,dc=com
<NSException: 0x576dc613fa28> NAME:LDAPException REASON:operation bind failed: Can't contact LDAP server (0xFFFFFFFF) INFO:{"error_code" = "-1"; login = "cn=sogo,dc=mydomain,dc=de"; }

These lines appear hundreds of times at the same time until the LDAP server no longer accepts connections because it holds too many open files. Then, clients like DAVx5 or Evolution cannot login anymore. After a short time, SOGo recovers and everything works until the issue occurs the next time.

Bisecting the commit history showed that 6aca61d is the culprit, and indeed reverting it fixes the issue in SOGo 5.0.1 and 5.1.0.

Steps To Reproduce

Use SOGo with LDAP and wait a few minutes. Maybe the number of users is also important (we have around 1100) as I could not reproduce the issue in a test instance with a single user.





2021-05-16 14:28

reporter   ~0015266

The issue tracker seems to do automatic formatting when a tilde is involved, the number of users should say “we have approx. 1100”.



2021-08-18 08:28

reporter   ~0015425

Same here, SoGO 5.0.1 from Debian Bullseye, applying a patch reverting 6aca61d fixed it.

Issue History

Date Modified Username Field Change
2021-05-16 14:26 timonegk New Issue
2021-05-16 14:26 timonegk Tag Attached: ldap
2021-05-16 14:28 timonegk Note Added: 0015266
2021-05-17 15:20 francis Steps to Reproduce Updated
2021-08-18 08:28 woffs Note Added: 0015425