Re: cyrus-imapd-2.4.16-14 (was: Re: kolab 3.0 on wheezy x86_64: latest cyrus update)

On 2012-11-08 06:24, Jochen Hein wrote:
> When updating I get:
>
> cyrus-imapd (2.4.16-14) wird eingerichtet ...
> Creating/updating cyrus user account...
> Der Benutzer »cyrus« ist bereits ein Mitglied der Gruppe »sasl«.
> Der Benutzer »cyrus« ist bereits ein Mitglied der Gruppe »ssl-cert«.
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/saslauthd/__init__.py", line
>   114, in run
>     self.do_saslauthd()
>   File "/usr/lib/python2.7/dist-packages/saslauthd/__init__.py", line
>   170, in do_saslauthd
>     (clientsocket, address) = s.accept()
>   File "/usr/lib/python2.7/socket.py", line 202, in accept
> Traceback (most recent call last):
>   File "/usr/lib/python2.7/dist-packages/wallace/__init__.py", line 
> 225,
>   in do_wallace
>     pair = s.accept()
>   File "/usr/lib/python2.7/socket.py", line 202, in accept
>     sock, addr = self._sock.accept()
> error: [Errno 4] Interrupted system call
>     sock, addr = self._sock.accept()
> error: [Errno 4] Interrupted system call
> Traceback occurred, please report a bug at 
> http://bugzilla.kolabsys.com
>
> I've restarted saslauthd and dpkg-reconfigure finished without 
> errors.
> So I'll see why saslauthd keeps disappearing.
>

These tracebacks are rather strange - both kolab-saslauthd *and* 
wallace experience an interrupted system call (upon cyrus-imapd 
update?)?

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

_______________________________________________
Kolab-devel mailing list
[email protected]
https://www.intevation.de/mailman/listinfo/kolab-devel