[Kolab-devel] kolab-saslauthd crashes
mat at cantinbrothers.ca
Thu Feb 14 04:22:09 CET 2013
I just wanted to follow up on this issue. It would appear that the
dirsrv service seems to "run out" of fds and shuts down until the dirsrv
is restarted. I've managed to increase the number of open fds from 1024
to 8000something which effectively reduces the crashes to once a week
instead of once a day, but just to make sure I've set up a cron with the
following script to run once a day every night, obviously not ideal.
If someone else has a better idea/solution, please let me know.
On 2013-01-23 11:35, Cantin, Mat wrote:
> I Finally found something useful: the slapd logs! In
> /var/log/dirsrv/slapd-compname/errors this error comes up:
> - Not listening for new connections - too many fds open
> So that's something. Now to figure out why that's happening on a
> that only 5 people are using...
> On 23.01.2013 11:17, Cantin, Mat wrote:
>> On 22.01.2013 03:45, Jeroen van Meeuwen (Kolab Systems) wrote:
>>> Really the only things kolab-saslauthd interacts with are
>>> /var/run/saslauthd/mux (an AF_UNIX socket), and LDAP (and it should
>>> automatically reconnect should the connection be lost).
>> I rebooted the server and the problem seemed to resolve itself...
>> this morning. I'm not really sure how to troubleshoot this. The
>> kolab-saslauthd service is running and not reporting any errors, but
>> none of the services that use it to authenticate can connect.
>> the service always fixes it, but only for a few minutes. I may just
>> reboot this server again to get things going, but this is a show
>> on a production server.
>> Kolab-devel mailing list
>> Kolab-devel at kolab.org
> Kolab-devel mailing list
> Kolab-devel at kolab.org
More information about the devel