On Thu, 23 Oct 2003, Jonas Jacobsson wrote: > I'm trying to upgrade from 1.5.19 to 2.1.14 (debian testing) > but when the upgrade is complete and I try to login > to cyradm I get a segmentation fault. > > moria:/var/spool# cyradm --user root localhost > Password: > Segmentation fault > moria:/var/spool# cyradm localhost > Password: > Segmentation fault > moria:/var/spool# > > And i think this log entry is about that: > > Oct 23 09:28:30 moria cyrus/master[4432]: about to exec > /usr/lib/cyrus/bin/imapd > Oct 23 09:28:30 moria cyrus/imapd[4432]: accepted connection > Oct 23 09:28:30 moria cyrus/imapd[4432]: badlogin: moria[127.0.0.1] > DIGEST-MD5 [SASL(-13): user not found: no secret in database] > Oct 23 09:29:33 moria cyrus/imapd[4432]: Could not shut down > filedescriptor 0: Bad file descriptor > Oct 23 09:29:33 moria cyrus/imapd[4432]: Could not shut down > filedescriptor 1: Bad file descriptor > Oct 23 09:29:33 moria cyrus/imapd[4432]: Could not shut down > filedescriptor 2: Bad file descriptor
These log entries are normal when you are logging at DEBUG level. I believe they were removed in 2.1.15 because they are misleading. > How do I fix this? I'd try running "strace -o /tmp/trace cyradm --user root localhost". Then have a look at the trace file to see what is happening. One strong possibility is you have both libsasl7 (the old version) and libsasl2 (the new version) installed. In some configurations, cyrus will inadvertantly link to both versions which will cause segfaults. There is a note in the README.debian file for cyrus-common about this. You should be able to see this happening in the trace file easily. Andy