Bug#393513: process 23446 exited, signaled to death by 6

[Benjamin Seidenberg]

reassign 393513 libnss-ldap
thanks

Ian Tester wrote:
> Package: Cyrus-imapd-2.2
> Version: 2.2.13-8
>
> Almost two weeks ago I started getting this error when trying to log into
> my Cyrus 2.1 IMAP server. I have an LDAP setup to centralise user
> accounts on my small family network. Thankfully this server is only used
> by myself. I use saslauthd for authentication, configured to use my LDAP
> directory.
>
> In the process of trying to find the problem I upgraded to the 2.2
> packages in an attempt to fix it, which is why I'm submitting it here. The
> problem remains the same.
>
> Today I found the reference to bug #145766 in README.Debian.gz. I rebuilt
> the openldap2 package with --without-cyrus-sasl and installed the libldap2
> package, but this did not seem to fix things. I found that simply removing
> the 'ldap' entries in nsswitch.conf fixed the problem. So it seems to be
> a problem with libnss-ldap. But without LDAP I couldn't log in to that
> machine (I use it for a few things) and Postfix started bouncing my email
> because it couldn't find my user account. So this is a totally unworkable
> solution. Please help me!
>
> Thanks,
> bye
>   
Based on your description of the problem and the timeline involved, I 
believe this is a bug in libnss-ldap and am reassigning it accordingly. 
On 2006-10-3, libnss-ldap 251-5.2 migrated to testing, which would be 
the point where you started experiencing problems.

In the future, please try to include the appropriate information in your 
bug reports, such as the version of debian you are using, the version of 
all the packages involved, your kernel and so forth. Using the reportbug 
utility will do this for you automatically.
Also, please make sure your bugs are filed against the appropriate 
packages. If you had a working cyrus 2.1 configuration that stopped 
working, filing a bug against cyrus 2.2 is not productive. Look at the 
dpkg logs to see what packages were updated around the time the problem 
occured and use that to trace the problem.

Best of luck in resolving your situation.
Benjamin
Debian Cyrus Packaging Team