[Bug 346140] [NEW] ldap connection failed / reason:emfile / ssl_esock issue

[Aaron C. de Bruyn]

Public bug reported:

I upgraded to the ejabberd package in universe (2.0.1-2~hardy1)

After running for a few days, I get this in my ejabberd.log:

=ERROR REPORT==== 2009-03-14 08:53:17 ===
W(<0.364.0>:eldap:566) : LDAP server closed the connection: lv-server.smiles.local:636
In State: active

=INFO REPORT==== 2009-03-14 08:53:17 ===
I(<0.364.0>:eldap:898) : LDAP connection on lv-server.smiles.local:636

=ERROR REPORT==== 2009-03-14 08:57:17 ===
W(<0.278.0>:eldap:566) : LDAP server closed the connection: lv-server.smiles.local:636
In State: active

The next two lines repeat until I kill the ssl_esock process, then
things start working normally again:

=INFO REPORT==== 2009-03-14 08:57:17 ===
I(<0.278.0>:eldap:898) : LDAP connection on lv-server.smiles.local:636

=ERROR REPORT==== 2009-03-14 08:57:17 ===
E(<0.278.0>:eldap:915) : LDAP connection failed on lv-server.smiles.local:636
Reason: emfile


This appears to be due ssl_esock using up more and more connections when the Windows AD/LDAP server closes the connection.
More and more sockets are used up, eventually they are unable to allocate more.

** Affects: ejabberd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
ldap connection failed / reason:emfile / ssl_esock issue
https://bugs.launchpad.net/bugs/346140
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs