Re: kolab-saslauthd crashes
"Cantin, Mat" <[email protected]>
| Newsgroups | gmane.comp.kde.devel.kolab,gmane.comp.kde.kolab.devel |
|---|---|
| Message-ID | <[email protected]> |
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 server that only 5 people are using... Mat 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... > until > 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. > Restarting > 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 > stopper > on a production server. > > Thanks. > Mat > > _______________________________________________ > Kolab-devel mailing list > [email protected] > https://www.intevation.de/mailman/listinfo/kolab-devel