[Dovecot] Dovecot Sieve crash
I just transferred the files in my home directory from an x86_64 machine to an i686 machine. This included the .dovecot.sieve and .dovecot.sievec files in my home root, and the Dovecot index files in my ~/Maildir directory. Everything seemed to be working until I tried sending an email that triggers a Sieve "redirect" command, then I got the following in the logs. I then tried the same dovecot.sieve file using a separate account which has always been on the i686 machine (and the index files have always been written there too), and the Sieve "redirect" worked fine. There were core files written in my home directory which I can post if necessary.
Both the x86_64 and i686 machines are CentOS 4.5 running Dovecot 1.0.5 and Dovecot Sieve plugin 1.0.1.
Sep 15 21:44:10 myhost deliver(julian): Trying to allocate 0 bytes Sep 15 21:44:10 myhost deliver(julian): Raw backtrace: /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x24) [0x80a08b4] -> /usr/libexec/dovecot/deliver [0x80a06a9] -> /usr/libexec/dovecot/deliver [0x80a91bd] -> /usr/libexec/dovecot/deliver [0x80574f8] -> /usr/libexec/dovecot/deliver(duplicate_check+0x51) [0x8057671] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x133f1f] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x549) [0x141b59] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x3fd) [0x134c4d] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x1339f8] -> /usr/libexec/dovecot/deliver(main+0x10c8) [0x8056e28] -> /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x506de3] -> /usr/libexec/dovecot/deliver [0x80550a1] Sep 15 21:44:10 myhost postfix/local[4924]: E1947344AE: to=<julian@lava.net>, relay=local, delay=0.35, delays=0.17/0.01/0/0.17, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/libexec/dovecot/deliver")
Isn't .dovecot.sievec a binary file that should be recreated on the target platform? /Lars
Julian Cowley wrote:
I just transferred the files in my home directory from an x86_64 machine to an i686 machine. This included the .dovecot.sieve and .dovecot.sievec files in my home root, and the Dovecot index files in my ~/Maildir directory. Everything seemed to be working until I tried sending an email that triggers a Sieve "redirect" command, then I got the following in the logs. I then tried the same dovecot.sieve file using a separate account which has always been on the i686 machine (and the index files have always been written there too), and the Sieve "redirect" worked fine. There were core files written in my home directory which I can post if necessary.
Both the x86_64 and i686 machines are CentOS 4.5 running Dovecot 1.0.5 and Dovecot Sieve plugin 1.0.1.
Sep 15 21:44:10 myhost deliver(julian): Trying to allocate 0 bytes Sep 15 21:44:10 myhost deliver(julian): Raw backtrace: /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x24) [0x80a08b4] -> /usr/libexec/dovecot/deliver [0x80a06a9] -> /usr/libexec/dovecot/deliver [0x80a91bd] -> /usr/libexec/dovecot/deliver [0x80574f8] -> /usr/libexec/dovecot/deliver(duplicate_check+0x51) [0x8057671] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x133f1f] ->
/usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x549) [0x141b59] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x3fd) [0x134c4d] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x1339f8] -> /usr/libexec/dovecot/deliver(main+0x10c8) [0x8056e28] -> /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x506de3] -> /usr/libexec/dovecot/deliver [0x80550a1] Sep 15 21:44:10 myhost postfix/local[4924]: E1947344AE: to=<julian@lava.net>, relay=local, delay=0.35, delays=0.17/0.01/0/0.17, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/libexec/dovecot/deliver")
Lars Stavholm wrote:
Isn't .dovecot.sievec a binary file that should be recreated on the target platform?
Also, dovecot-sieve is available as version 1.0.2. /L
Julian Cowley wrote:
I just transferred the files in my home directory from an x86_64 machine to an i686 machine. This included the .dovecot.sieve and .dovecot.sievec files in my home root, and the Dovecot index files in my ~/Maildir directory. Everything seemed to be working until I tried sending an email that triggers a Sieve "redirect" command, then I got the following in the logs. I then tried the same dovecot.sieve file using a separate account which has always been on the i686 machine (and the index files have always been written there too), and the Sieve "redirect" worked fine. There were core files written in my home directory which I can post if necessary.
Both the x86_64 and i686 machines are CentOS 4.5 running Dovecot 1.0.5 and Dovecot Sieve plugin 1.0.1.
Sep 15 21:44:10 myhost deliver(julian): Trying to allocate 0 bytes Sep 15 21:44:10 myhost deliver(julian): Raw backtrace: /usr/libexec/dovecot/deliver(i_syslog_panic_handler+0x24) [0x80a08b4] -> /usr/libexec/dovecot/deliver [0x80a06a9] -> /usr/libexec/dovecot/deliver [0x80a91bd] -> /usr/libexec/dovecot/deliver [0x80574f8] -> /usr/libexec/dovecot/deliver(duplicate_check+0x51) [0x8057671] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x133f1f] ->
/usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0x549) [0x141b59] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x3fd) [0x134c4d] -> /usr/lib/dovecot/lda/lib90_cmusieve_plugin.so [0x1339f8] -> /usr/libexec/dovecot/deliver(main+0x10c8) [0x8056e28] -> /lib/tls/libc.so.6(__libc_start_main+0xd3) [0x506de3] -> /usr/libexec/dovecot/deliver [0x80550a1] Sep 15 21:44:10 myhost postfix/local[4924]: E1947344AE: to=<julian@lava.net>, relay=local, delay=0.35, delays=0.17/0.01/0/0.17, dsn=5.3.0, status=bounced (Command died with signal 6: "/usr/libexec/dovecot/deliver")
On Sun, 16 Sep 2007, Lars Stavholm wrote:
Julian Cowley wrote:
I just transferred the files in my home directory from an x86_64 machine to an i686 machine. This included the .dovecot.sieve and .dovecot.sievec files in my home root, and the Dovecot index files in my ~/Maildir directory. Everything seemed to be working until I tried sending an email that triggers a Sieve "redirect" command, then I got the following in the logs. I then tried the same dovecot.sieve file using a separate account which has always been on the i686 machine (and the index files have always been written there too), and the Sieve "redirect" worked fine. There were core files written in my home directory which I can post if necessary.
Both the x86_64 and i686 machines are CentOS 4.5 running Dovecot 1.0.5 and Dovecot Sieve plugin 1.0.1.
Isn't .dovecot.sievec a binary file that should be recreated on the target platform?
I removed the .dovecot.sievec just to be sure, but the crashing continued. I got the same result after compiling it manually with the sievec utility.
I'll see if 1.0.2 makes a difference, but I posted this now just in case someone had seen it before.
On Sat, 2007-09-15 at 22:41 -1000, Julian Cowley wrote:
/usr/libexec/dovecot/deliver(duplicate_check+0x51) [0x8057671] ->
Looks like your duplicate database has broken. Delete .dovecot.lda-dupes file and it should work again.
This will be fixed in next version: http://hg.dovecot.org/dovecot-1.0/rev/9d4e89fa62d0
On Sun, 16 Sep 2007, Timo Sirainen wrote:
On Sat, 2007-09-15 at 22:41 -1000, Julian Cowley wrote:
/usr/libexec/dovecot/deliver(duplicate_check+0x51) [0x8057671] ->Looks like your duplicate database has broken. Delete .dovecot.lda-dupes file and it should work again.
This will be fixed in next version: http://hg.dovecot.org/dovecot-1.0/rev/9d4e89fa62d0
Thanks. Just tried removing the dovecot.lda-duples file and it seems to work. No crashes after running my test case, and it appears to be stable with other mail as well.
All other files in my home directory (in particular the Dovecot index files) on the i686 machine were as transferred from the x86_64 machine via rsync -a --delete. So far it looks like transferring entire home directories between different architectures is not a problem.
On Sun, 2007-09-16 at 02:47 -1000, Julian Cowley wrote:
On Sun, 16 Sep 2007, Timo Sirainen wrote:
On Sat, 2007-09-15 at 22:41 -1000, Julian Cowley wrote:
/usr/libexec/dovecot/deliver(duplicate_check+0x51) [0x8057671] ->Looks like your duplicate database has broken. Delete .dovecot.lda-dupes file and it should work again.
This will be fixed in next version: http://hg.dovecot.org/dovecot-1.0/rev/9d4e89fa62d0
Thanks. Just tried removing the dovecot.lda-duples file and it seems to work. No crashes after running my test case, and it appears to be stable with other mail as well.
All other files in my home directory (in particular the Dovecot index files) on the i686 machine were as transferred from the x86_64 machine via rsync -a --delete. So far it looks like transferring entire home directories between different architectures is not a problem.
I should probably do something about the dupes file. The format is simple, stupid and looks like it also breaks if you move it between 32bit and 64bit systems. Dovecot's other files can handle it.
participants (3)
-
Julian Cowley
-
Lars Stavholm
-
Timo Sirainen