Re: kolab-saslauthd crashes

On 2013-01-21 19:55, Mat Cantin wrote:
> Greetings,
> 
> Out of nowhere, users on one of my Kolab 3 servers stopped being able
> to login. I managed to figure out that it has something to do with the
> kolab-saslauthd service from the roundcube logs. Restarting the
> kolab-saslauthd service seems to temporarily fix the problem but I've
> been unable to find the cause.
> 
> My investigation have brought up two questions:
> 1. Where are the logs for the kolab-saslauthd service located?

kolab-saslauthd logs to /var/log/kolab/pykolab.log

> 2. The /var/log/messages log file get 2 of these errors every minute.
> Could this have something to do with the problem?
> imap[24259]: unable to open Berkeley db /etc/sasldb2: No such file or
> directory
> 

This is unrelated, and, IIRC, has to do with Cyrus SASL's libsasldb 
(when dlopen()'ed) directly attempting to open its database 
(/etc/sasldb2/) and logging any failure to do so.

> Anyone else running into these problems?

I've heard of the problem before, but I've not been able to reproduce 
the circumstances under which it happens.

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).

Kind regards,

Jeroen van Meeuwen

-- 
Systems Architect, Kolab Systems AG

e: vanmeeuwen at kolabsys.com
m: +44 74 2516 3817
w: http://www.kolabsys.com

pgp: 9342 BF08