We have an environment running on PSMDB 7.0.11-6 and today I’ve found one of my servers went down due to very likely an issue with LDAP connectivity.
The log will be attached here, but my understanding is that the issue happened while authenticating users on LDAP servers (upon connection criation) but this one seems a bit different than the PSMDB-1418 and also I can see the commit 197ff4d49589e8b5a444b7ebc6f4d33b6f00105e is in this version.
Would you mind having a look in the logs and see if it is a possible bug?
Environment
None
Activity
Show:
Igor Solodovnikov February 5, 2025 at 7:35 PM
Sure, please create a PR.
Adamo tonete February 5, 2025 at 2:10 PM
Thanks , I have it working on MongoDB 4.2.2025 lol
Does it worth creating a PR to percona repos?
Igor Solodovnikov February 4, 2025 at 7:35 PM
Yes, even for v4.2. I cannot guarantee anything because v4.2 is not supported anymore and we don’t test its behavior. But as I wrote: if cherry-pick and build succeeded there is a good chance that it will work. I still recommend that you test it before going to production.
Adamo tonete February 4, 2025 at 4:23 PM
even for v4.2 ? I still stuck with this version at least until the end of this year.. and we heavily depend on LDAP and can’t afford downtime due to ldap timeout/unavailability
Igor Solodovnikov February 4, 2025 at 4:19 PM
If the cherry pick was merged successfully and you can build without errors then it should be safe.
Hi all,
We have an environment running on PSMDB 7.0.11-6 and today I’ve found one of my servers went down due to very likely an issue with LDAP connectivity.
The log will be attached here, but my understanding is that the issue happened while authenticating users on LDAP servers (upon connection criation) but this one seems a bit different than the PSMDB-1418 and also I can see the commit 197ff4d49589e8b5a444b7ebc6f4d33b6f00105e is in this version.
Would you mind having a look in the logs and see if it is a possible bug?