Ldapmavis-mt doesn’t try to open new session to ldap server after inactivity about event-driven-servers HOT 7 CLOSED

Hi Sandy,

alas, it will take a while to add resilience to this. Threading complicates things :-/

Cheers,

Marc

from event-driven-servers.

Hi Sandy,

I've added some recovery code in 6edb2e1.

Cheers,

Marc

from event-driven-servers.

Hi Marc,

I just tried testing this, unfortunately it now doesn’t try to reach out to LDAPS hosts even on first attempt.

I rolled back to previous commit 004679e and LDAPS is working again

from event-driven-servers.

Hi Sandy,

mea culpa ... looks like I didn't test the latest code correctly (wrong binary). The lastest commit should fix this issue.

Thanks,

Marc

from event-driven-servers.

Hi Marc,

Checking latest shows LDAPS is working again, thanks! Still seeing the original behaviour though; if I leave the tacacs server with no client activity until the TCP sessions with LDAPS all timeout (5 mins in my case) and then retry an auth, tacacs server is not trying to reach out to LDAPS

Cheers
Sandy

from event-driven-servers.

Hi Sandy,

e4f7ff3 removes the shared LDAP connection and uses a dedicated one for each thread, so connection timeouts should no longer cause issues.

Cheers,

Marc

from event-driven-servers.

That’s fixed it! Nice! Thank you Marc

from event-driven-servers.