I've build this nightly snapshot with my installed openssl, which is 0.9.8b (Fedora 6) and the latest openssl development tree. The 20070605 version of dovecot starts up doing ssl protocol perfect, then after clicking a few directories, then when clicking back to INBOX, dovecot hangs. There is no logging info, even with --enable-debug on and all .conf file directives I can find. Doing a 'ngrep port 993' shows no SSL dialog. If I go through my same compile sequence using the dovecot-1.0.0 source all is well with both the system openssl and the latest openssl snapshot, so it appears something is wrong in the current nightly snapshot. My primary question is howto debug this hang, short of attaching gdb to the process. Any suggestions are appreciated. Thanks. I'm using the latest Thunderbird version 2.0.0.4 (20070604). I've build it using: [root at net1 dovecot-20070605]# build_dovecot mkdir -p /build/work/dovecot-20070605 cd /build/work/dovecot-20070605 unset CDPATH export CPPFLAGS='-pipe -O2 -I/usr/local/include' export LDFLAGS='-L/usr/local/lib' make distclean ./configure --prefix=/usr/local/pkgs/dovecot-20070605 --disable-nls --with-deliver --with-sqlite --without-vpopmail --with-notify=inotify --with-ioloop=epoll --with-ssl=openssl --enable-debug --enable-asserts make make check rm -rf /usr/local/pkgs/dovecot-20070605 make install install -c -m 555 doc/mkcert.sh /usr/local/pkgs/dovecot-20070605/sbin/dovecot-mkcert shmk /usr/local/pkgs/dovecot-20070605/sbin /usr/local/sbin mkdir -p /etc/ssl/certs /etc/ssl/private rm -f /etc/ssl/certs/dovecot.pem /etc/ssl/private/dovecot.pem export OPENSSLCONFIG=/tools/conf/dovecot-openssl.conf dovecot-mkcert cp -f /etc/ssl/certs/dovecot.pem /var/www/html/. chmod ugo+r /var/www/html/dovecot.pem groupadd dovecot || /bin/true groupadd: group dovecot exists useradd -M -g dovecot -d /usr/local -s /sbin/nologin dovecot || /bin/true useradd: user dovecot exists (cd /etc/init.d && ln -sf /tools/init.d/dovecot .) -- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com
On Sun, 2007-06-10 at 21:12 -0500, David Favor wrote:> The 20070605 version of dovecot starts up doing ssl protocol perfect, > then after clicking a few directories, then when clicking back to INBOX, > dovecot hangs. There is no logging info, even with --enable-debug > on and all .conf file directives I can find. Doing a 'ngrep port 993' > shows no SSL dialog.1) Enable rawlog to see what were the last commands and their output. http://dovecot.org/bugreport.html 2) strace the running imap process to see if it's just waiting in epoll() or if it's doing something else.> My primary question is howto debug this hang, short of attaching gdb > to the process.If it's not in epoll(), getting a gdb backtrace would be helpful too. Hmm. Or the above things matter only if the problem is with imap process and not with handling the SSL connection. So it would also be good to know if it hangs also without SSL. BTW. --enable-debug doesn't make Dovecot log any more than it normally does. It instead enables some extra code that makes Dovecot do more sanity checks so I can notice sooner if I break something. Unless you're modifying Dovecot's sources yourself it most likely isn't very useful. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: <http://dovecot.org/pipermail/dovecot/attachments/20070611/ba4a421f/attachment-0002.bin>
Seems to have had something to do with pam occasionally losing it's marbles. I've removed pam from my config file and all works well now with latest dovecot with latest openssl development nightly snapshot. - David Timo Sirainen wrote:> On Sun, 2007-06-10 at 21:12 -0500, David Favor wrote: >> The 20070605 version of dovecot starts up doing ssl protocol perfect, >> then after clicking a few directories, then when clicking back to INBOX, >> dovecot hangs. There is no logging info, even with --enable-debug >> on and all .conf file directives I can find. Doing a 'ngrep port 993' >> shows no SSL dialog. > > 1) Enable rawlog to see what were the last commands and their output. > http://dovecot.org/bugreport.html > > 2) strace the running imap process to see if it's just waiting in > epoll() or if it's doing something else. > >> My primary question is howto debug this hang, short of attaching gdb >> to the process. > > If it's not in epoll(), getting a gdb backtrace would be helpful too. > > Hmm. Or the above things matter only if the problem is with imap process > and not with handling the SSL connection. So it would also be good to > know if it hangs also without SSL. > > BTW. --enable-debug doesn't make Dovecot log any more than it normally > does. It instead enables some extra code that makes Dovecot do more > sanity checks so I can notice sooner if I break something. Unless you're > modifying Dovecot's sources yourself it most likely isn't very useful. >-- Like feeling your best ever, all day, every day? Here's how... Your simple secrets are here - http://RadicalHealth.com