** Changed in: ejabberd (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346140
Title:
ldap connection failed / reason:emfile / ssl_esock issue
To man
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ejabberd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346140
Title:
ld
** Changed in: ejabberd (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/346140
Title:
ldap connection failed / reason:emfile / ssl_esock issue
To manag
** Also affects: ejabberd (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490059
Importance: Unknown
Status: Unknown
--
ldap connection failed / reason:emfile / ssl_esock issue
https://bugs.launchpad.net/bugs/346140
You received this bug notification because you are a m
Debian upstream fixed it in ejabberd_2.0.1-3, while my computer is running
ejabberd_2.0.1-2
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490059#84
Can we have this backported?
** Bug watch added: Debian Bug tracker #490059
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=490059
--
ldap c
As a workaround, I added this to my crontab:
@daily killall ssl_esock
I can reproduce this fairly constantly--it just takes a few days to show up.
Downgrading to the earlier version of ejabberd did not fix the problem.
--
ldap connection failed / reason:emfile / ssl_esock issue
https://bugs.laun
