I have done backtraces before, but this one was a little more unusual for me. The last time I needed a backtrace, I was able to capture the daemon's full command line, then run it through GDB. In this case, I'm thinking the offending program is located at /usr/lib/dovecot/dovecot-auth, it is run by the dovecot daemon as needed, and then exits with a result (or, in this case, a crash) shortly after starting.
In this case, I stopped dovecot, sudo-ed into root, ran `ulimit -c unlimited`, ran dovecot manually, and had my IMAP client try a login. That caused dovecot-auth to die again (as expected), and dropped a core file in /var/run/dovecot. I installed both dovecot-common-dbgsym and libpam0g-dbgsym packages, ran `gdb /usr/lib/dovecot/dovecot-auth core`, and then ran the 5 GDB commands requested in https://wiki.ubuntu.com/Backtrace. Attached are the results!
Hi Chuck,
I have done backtraces before, but this one was a little more unusual for me. The last time I needed a backtrace, I was able to capture the daemon's full command line, then run it through GDB. In this case, I'm thinking the offending program is located at /usr/lib/ dovecot/ dovecot- auth, it is run by the dovecot daemon as needed, and then exits with a result (or, in this case, a crash) shortly after starting.
In this case, I stopped dovecot, sudo-ed into root, ran `ulimit -c unlimited`, ran dovecot manually, and had my IMAP client try a login. That caused dovecot-auth to die again (as expected), and dropped a core file in /var/run/dovecot. I installed both dovecot- common- dbgsym and libpam0g-dbgsym packages, ran `gdb /usr/lib/ dovecot/ dovecot- auth core`, and then ran the 5 GDB commands requested in https:/ /wiki.ubuntu. com/Backtrace. Attached are the results!