El Miércoles, 27 de Febrero de 2008, Henrique de Moraes Holschuh escribió:
> On Wed, 27 Feb 2008, Daniel Estévez Sánchez wrote:
> > In relation with this two bug reports:
> >
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418615
> > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418615
> No
On Wed, 27 Feb 2008, Daniel Estévez Sánchez wrote:
> In relation with this two bug reports:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418615
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418615
>
> I have found a way to solve the problem. The issue seems libnss-ldap crashing
> wi
In relation with this two bug reports:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418615
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=418615
I have found a way to solve the problem. The issue seems libnss-ldap crashing
wierdly when permissions on /etc/libnss-ldap.conf are set to 600. S
On Wed, 12 Dec 2007, Rico Barth wrote:
> We recently updated from libnss-ldap_251-7.5_ia64 to
> libnss-ldap_251-7.5etch1_ia64. Now the error re-occurs. However, after
> downgrading to libnss-ldap_251-7.5_ia64 the error still occurs. Now the
> interesting part: before upgrading we've had no proble
Hi Henrique!
We recently updated from libnss-ldap_251-7.5_ia64 to
libnss-ldap_251-7.5etch1_ia64. Now the error re-occurs. However, after
downgrading to libnss-ldap_251-7.5_ia64 the error still occurs. Now
the interesting part: before upgrading we've had no problems for a few
months (see some
On Thu, 20 Sep 2007, Hans van Kranenburg wrote:
> I upgraded a box to Etch yesterday, and following was a complaint from a
> user that she got errors about a connection dropped by the IMAP server
> right after a ldap-user login in squirrelmail.
cyrus 2.1 cannot deal with LDAP group lookups without
I upgraded a box to Etch yesterday, and following was a complaint from a
user that she got errors about a connection dropped by the IMAP server
right after a ldap-user login in squirrelmail.
The logs show:
Sep 20 23:16:51 office cyrus/imapd[11411]: accepted connection
Sep 20 23:16:51 office cyrus
Hi Henrique!
On Wed, 13 Jun 2007, Henrique de Moraes Holschuh wrote:
Yuck. It is not the regular SASL problems I know of, then. It might be a
bug in nscd too.
yes, this is what I think.
Signal 6 is SIGABRT. This is *way* too weird. Cyrus doesn't use abort(),
AFAIK. It never dies with
On Wed, 13 Jun 2007, Rico Barth wrote:
> Well, we tried to reproduce this failure and sent strace output but we
> couldn't reproduce it. It seems there's a relation between nscd
> and the server crashes. As I wrote my first reply to this bug all
Yuck. It is not the regular SASL problems I know
Hi Henrique!
On Mon, 11 Jun 2007, Henrique de Moraes Holschuh wrote:
On Mon, 11 Jun 2007, Rico Barth wrote:
all works fine. But we need ldap group support and this workaround is not
suitable for us.
Well, I need an strace of the crash. See the cyrus21 documentation on how
to get one.
And,
On Mon, 11 Jun 2007, Rico Barth wrote:
> all works fine. But we need ldap group support and this workaround is not
> suitable for us.
Well, I need an strace of the crash. See the cyrus21 documentation on how
to get one.
And, if it is what I think it is, there is no fix (libsasl going berserk).
Hi,
we have same problem. After mailserver change from Debian/etch on hppa to
Debian/etch on ia64 there is still the same problem. On hppa cyrus, sasl
and pam worked fine.
our /etc/nsswitch.conf:
...
passwd: files ldap
group:files ldap
shadow: files ldap
...
If I ch
12 matches
Mail list logo
