Re: [Dovecot] dovecot 2.2.10 - imap: Error: Can't load plugin imap_stats_plugin:
Am 30.12.2013 14:29, schrieb giova...@neweden.uk.to:
dovecot 2.2.10 is raising this error on my installation.
Dec 30 13:57:59 imap: Error: Can't load plugin imap_stats_plugin: Plugin
stats must be loaded also (you must set:
mail_plugins=$mail_plugins stats)
Dec 30 13:57:59 imap: Fatal: Couldn't load required plugins
This error occurs at logging phase.
The dovecot configuration looks correct to me, here below an excerpt of it:
how do you come to that conclusion by quoting the error above?
you must set: mail_plugins=$mail_plugins stats and have
stats *not* configured - notice the word *also* above
mail_plugins=$mail_plugins stats
protocol imap {
mail_plugins = $mail_plugins imap_stats
}
plugin {
# how often to session statistics
stats_refresh = 30 secs
# track per-IMAP command statistics
stats_track_cmds = yes
}
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] dovecot 2.2.10 - imap: Error: Can't load plugin imap_stats_plugin:
Am 30.12.2013 14:33, schrieb Reindl Harald:
Am 30.12.2013 14:29, schrieb giova...@neweden.uk.to:
dovecot 2.2.10 is raising this error on my installation.
Dec 30 13:57:59 imap: Error: Can't load plugin imap_stats_plugin: Plugin
stats must be loaded also (you must set:
mail_plugins=$mail_plugins stats)
Dec 30 13:57:59 imap: Fatal: Couldn't load required plugins
This error occurs at logging phase.
The dovecot configuration looks correct to me, here below an excerpt of it:
how do you come to that conclusion by quoting the error above?
you must set: mail_plugins=$mail_plugins stats and have
stats *not* configured - notice the word *also* above
mail_plugins=$mail_plugins stats
protocol imap {
mail_plugins = $mail_plugins imap_stats
}
plugin {
# how often to session statistics
stats_refresh = 30 secs
# track per-IMAP command statistics
stats_track_cmds = yes
}
sorry - indeed i missed the first line and faced only mail_plugins
in the imap section :-(
signature.asc
Description: OpenPGP digital signature
Re: [Dovecot] Dovecot 2 + IMAP
12.06.2013 22:34, Michael Kliewe пишет: Hello Alex, you asked exactly the same question 5 days ago and already got the answer (from 2 people). Why did you ask again, didn't you receive the answers? Thank you for your answer. Yes, i didn't receive answer signature.asc Description: OpenPGP digital signature
Re: [Dovecot] Dovecot 2 + IMAP
On 06/12/2013 07:44 PM, Alex Dubinin wrote: This is my first experience of the mail server. Set up a mail server from Postfix + Dovecot with the MySQL authorization. When you create a new user dovecot makes strange folder structure: the 'inbox' contains 'juncus', 'tash', 'sent' etc. ie 'sent' and other folders are subdir to the 'inbox'. How to make the imap folders 'sent', 'trash' and others were not affiliated? prefix = INBOX. Remove this. This is a common misconfiguration. Where did you find this? Does Debian have this in default config or sth? -- Aleksander 'A.L.E.C' Machniak LAN Management System Developer [http://lms.org.pl] Roundcube Webmail Developer [http://roundcube.net] --- PGP: 19359DC1 @@ GG: 2275252 @@ WWW: http://alec.pl
Re: [Dovecot] Dovecot list IMAP archives with thunderbird?
On 20/06/12 17:39, Alex Crow wrote: Hi, I'm trying to access the IMAP archives with Thunderbird but can't seem to get it to work. I have tried an unencrypted connection, SSL and TLS but with no success. Any ideas? Thanks Alex Hi, Still stuck here - would really like to be able to access the archives in my email client... Anyone able to see the mailing list archives in Thunderbird or other IMAP clients? Are they currently down? Cheers Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. Transact is operated by Integrated Financial Arrangements plc Domain House, 5-7 Singer Street, London EC2A 4BQ Tel: (020) 7608 4900 Fax: (020) 7608 5300 (Registered office: as above; Registered in England and Wales under number: 3727592) Authorised and regulated by the Financial Services Authority (entered on the FSA Register; number: 190856)
Re: [Dovecot] Dovecot list IMAP archives with thunderbird?
On Sat, 2012-06-23 at 18:00 +0100, Alex Crow wrote: I'm trying to access the IMAP archives with Thunderbird but can't seem to get it to work. I have tried an unencrypted connection, SSL and TLS but with no success. Any ideas? Thanks Alex Hi, Still stuck here - would really like to be able to access the archives in my email client... Anyone able to see the mailing list archives in Thunderbird or other IMAP clients? Are they currently down? It works fine as far as I can see, even with Thunderbird. What error do you get?
Re: [Dovecot] Dovecot list IMAP archives with thunderbird?
On 23/06/12 18:06, Timo Sirainen wrote: On Sat, 2012-06-23 at 18:00 +0100, Alex Crow wrote: I'm trying to access the IMAP archives with Thunderbird but can't seem to get it to work. I have tried an unencrypted connection, SSL and TLS but with no success. Any ideas? Thanks Alex Hi, Still stuck here - would really like to be able to access the archives in my email client... Anyone able to see the mailing list archives in Thunderbird or other IMAP clients? Are they currently down? It works fine as far as I can see, even with Thunderbird. What error do you get? Hi Timo, No errors at all, I just never see any folder list or messages - tcpdump shows a few packets only when TLS mode is selected, but nothing after that, Cheers Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disclose its contents or use it in any way and are requested to delete the message along with any attachments and notify us immediately. Transact is operated by Integrated Financial Arrangements plc Domain House, 5-7 Singer Street, London EC2A 4BQ Tel: (020) 7608 4900 Fax: (020) 7608 5300 (Registered office: as above; Registered in England and Wales under number: 3727592) Authorised and regulated by the Financial Services Authority (entered on the FSA Register; number: 190856)
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
On 16.2.2012, at 3.12, interfaSys sàrl wrote: Here is a more meanigful backtrace. It happens every time I log in, using any imap client. .. #0 0x105e0d88 in imap_match () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x104e82e5 in autocreate_iter_autobox.20436.5667 () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. Still debug symbols missing from libraries, but .. perhaps this fixes it? http://hg.dovecot.org/dovecot-2.1/rev/72e1e17d2e22 I don't know why it would happen with all imap clients though. And if that doesn't solve it, show your doveconf -n output.
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
That patch didn't fix it, but I've now compiled Dovecot without LTO and
got even more info :)
Core was generated by `imap'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...done.
Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0
Reading symbols from /usr/lib/dovecot/libdovecot.so.0...done.
Loaded symbols for /usr/lib/dovecot/libdovecot.so.0
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /usr/lib/dovecot/lib01_acl_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib01_acl_plugin.so
Reading symbols from /usr/lib/dovecot/lib02_imap_acl_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib02_imap_acl_plugin.so
Reading symbols from /usr/lib/dovecot/lib10_quota_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib10_quota_plugin.so
Reading symbols from /usr/lib/dovecot/lib11_imap_quota_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib11_imap_quota_plugin.so
Reading symbols from /usr/lib/dovecot/lib11_trash_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib11_trash_plugin.so
Reading symbols from /usr/lib/dovecot/lib20_autocreate_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib20_autocreate_plugin.so
Reading symbols from /usr/lib/dovecot/lib20_fts_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib20_fts_plugin.so
Reading symbols from /usr/lib/dovecot/lib20_zlib_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib20_zlib_plugin.so
Reading symbols from /lib/libz.so.5...done.
Loaded symbols for /lib/libz.so.5
Reading symbols from /usr/lib/libbz2.so.4...done.
Loaded symbols for /usr/lib/libbz2.so.4
Reading symbols from /usr/lib/dovecot/lib21_fts_squat_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib21_fts_squat_plugin.so
Reading symbols from /usr/lib/dovecot/lib30_imap_zlib_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib30_imap_zlib_plugin.so
Reading symbols from /usr/lib/dovecot/lib90_antispam_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib90_antispam_plugin.so
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x105954b6 in imap_match (glob=0x0, data=0x10aa01d8
INBOX/spam) at array.h:189
189 array.h: No such file or directory.
in array.h
(gdb) bt full
#0 0x105954b6 in imap_match (glob=0x0, data=0x10aa01d8
INBOX/spam) at array.h:189
ctx = {inboxcase_end = 0x7fffe7d0 \237\004, sep = 64 '@',
inboxcase = 248}
i = 0
ret = IMAP_MATCH_NO
match = IMAP_MATCH_NO
#1 0x1049a119 in autocreate_iter_autobox (ctx=0x10a0f840,
autobox=0x10a0f9a8) at mailbox-list-iter.c:88
actx = (struct mailbox_list_autocreate_iterate_context *) 0x10a0f918
match = 32767
__FUNCTION__ = autocreate_iter_autobox
#2 0x1049a484 in autocreate_iter_next (ctx=0x10a0f840) at
mailbox-list-iter.c:88
actx = (struct mailbox_list_autocreate_iterate_context *) 0x10a0f918
info = (const struct mailbox_info *) 0x0
autoboxes = (const struct autocreate_box *) 0x10a0f9a8
autobox = (const struct autocreate_box *) 0x10a0f9a8
count = 1
__FUNCTION__ = autocreate_iter_next
#3 0x1049a561 in mailbox_list_iter_next (ctx=0x10a0f840) at
mailbox-list-iter.c:88
info = (const struct mailbox_info *) 0x7fffe86c
#4 0x0040d06a in list_namespace_mailboxes (ctx=0x10a3f158) at
array.h:189
info = (const struct mailbox_info *) 0x10a0f920
ns = (struct mail_namespace *) 0x0
flags = 536870916
str = (string_t *) 0x10a04290
mutf7_name = (string_t *) 0x10a043e0
name = 0x10a10040 INBOX
ret = 1
#5 0x0040dc25 in cmd_list_continue (cmd=0x10a3f040) at array.h:189
_data_stack_cur_id = 4
ctx = (struct cmd_list_context *) 0x10a3f158
ret = 0
#6 0x0040e3b7 in cmd_list_full (cmd=0x10a3f040, lsub=false) at
array.h:189
client = (struct client *) 0x10a3e840
args = (const struct imap_arg *) 0x10aa4118
list_args = (const struct imap_arg *) 0x10aa4340
arg_count = 1
ctx = (struct cmd_list_context *) 0x10a3f158
patterns = {arr = {buffer = 0x10a3f1a8, element_size = 8}, v =
0x10a3f1a8, v_modifiable = 0x10a3f1a8}
pattern = 0x10a04268 INBOX
patterns_strarr = (const char * const *) 0x10a3f1e0
str = (string_t *) 0x10a041f0
#7 0x0040e40c in cmd_list (cmd=0x10a3f040) at array.h:189
No locals.
#8 0x004140a0 in command_exec (cmd=0x10a3f040) at
imap-commands.c:90
hook = (const struct command_hook *) 0x10a22200
ret = false
#9 0x004130b9 in client_command_input (cmd=0x10a3f040) at
imap-client.c:94
client = (struct client *) 0x10a3e840
command = (struct command *) 0x7fff0001
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
On 16.2.2012, at 19.04, interfaSys sàrl wrote: That patch didn't fix it, but I've now compiled Dovecot without LTO and got even more info :) What's your doveconf -n output?
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
OK, this should fix it: http://hg.dovecot.org/dovecot-2.1/rev/ff117a044e20
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
Yep, works perfectly now. Thank you for fixing it :) On 16 February 2012 18:04:30, Timo Sirainen wrote: OK, this should fix it: http://hg.dovecot.org/dovecot-2.1/rev/ff117a044e20
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
Hello,
Here is a more meanigful backtrace. It happens every time I log in,
using any imap client.
*
Core was generated by `imap'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...done.
Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0
Reading symbols from /usr/lib/dovecot/libdovecot.so.0...done.
Loaded symbols for /usr/lib/dovecot/libdovecot.so.0
Reading symbols from /lib/libc.so.7...done.
Loaded symbols for /lib/libc.so.7
Reading symbols from /usr/lib/librt.so.1...done.
Loaded symbols for /usr/lib/librt.so.1
Reading symbols from /usr/lib/dovecot/lib01_acl_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib01_acl_plugin.so
Reading symbols from /usr/lib/dovecot/lib02_imap_acl_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib02_imap_acl_plugin.so
Reading symbols from /usr/lib/dovecot/lib10_quota_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib10_quota_plugin.so
Reading symbols from /usr/lib/dovecot/lib11_imap_quota_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib11_imap_quota_plugin.so
Reading symbols from /usr/lib/dovecot/lib11_trash_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib11_trash_plugin.so
Reading symbols from /usr/lib/dovecot/lib20_autocreate_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib20_autocreate_plugin.so
Reading symbols from /usr/lib/dovecot/lib20_fts_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib20_fts_plugin.so
Reading symbols from /usr/lib/dovecot/lib20_zlib_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib20_zlib_plugin.so
Reading symbols from /lib/libz.so.5...done.
Loaded symbols for /lib/libz.so.5
Reading symbols from /usr/lib/libbz2.so.4...done.
Loaded symbols for /usr/lib/libbz2.so.4
Reading symbols from /usr/lib/dovecot/lib21_fts_squat_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib21_fts_squat_plugin.so
Reading symbols from /usr/lib/dovecot/lib30_imap_zlib_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib30_imap_zlib_plugin.so
Reading symbols from /usr/lib/dovecot/lib90_antispam_plugin.so...done.
Loaded symbols for /usr/lib/dovecot/lib90_antispam_plugin.so
Reading symbols from /libexec/ld-elf.so.1...done.
Loaded symbols for /libexec/ld-elf.so.1
#0 0x105e0d88 in imap_match () from
/usr/lib/dovecot/libdovecot.so.0
(gdb) bt full
#0 0x105e0d88 in imap_match () from
/usr/lib/dovecot/libdovecot.so.0
No symbol table info available.
#1 0x104e82e5 in autocreate_iter_autobox.20436.5667 () from
/usr/lib/dovecot/libdovecot-storage.so.0
No symbol table info available.
#2 0x104e6eda in autocreate_iter_next.20443 () from
/usr/lib/dovecot/libdovecot-storage.so.0
No symbol table info available.
#3 0x104dd72e in mailbox_list_iter_next () from
/usr/lib/dovecot/libdovecot-storage.so.0
No symbol table info available.
#4 0x00416351 in list_namespace_mailboxes.7882 (ctx=0x10a3f158)
at cmd-list.c:408
info = (const struct mailbox_info *) 0x10a0f920
ns = (struct mail_namespace *) 0x0
flags = 536870916
str = (struct buffer *) 0x10a04290
mutf7_name = (struct buffer *) 0x10a043e0
name = (const __unknown__ *) 0x10a10040 INBOX
ret = 1
#5 0x0041c2ac in cmd_list_continue (cmd=0x10a3f040) at
cmd-list.c:823
_data_stack_cur_id = 4
ctx = (struct cmd_list_context *) 0x10a3f158
ret = 0
#6 0x0041c1d0 in cmd_list_full (cmd=0x10a3f040, lsub=false) at
cmd-list.c:999
client = (struct client *) 0x10a3e840
args = (const struct imap_arg *) 0x10aa4118
list_args = (const struct imap_arg *) 0x10aa4340
arg_count = 1
ctx = (struct cmd_list_context *) 0x10a3f158
patterns = {arr = {buffer = 0x10a3f1a8, element_size = 8}, v =
0x10a3f1a8, v_modifiable = 0x10a3f1a8}
pattern = (const __unknown__ *) 0x10a04268 INBOX
patterns_strarr = (const __unknown__ * const *) 0x10a3f1e0
str = (struct buffer *) 0x10a041f0
#7 0x0041bc80 in cmd_list (cmd=0x10a3f040) at cmd-list.c:1014
No locals.
#8 0x00411264 in command_exec (cmd=0x10a3f040) at
imap-commands.c:147
hook = (const struct command_hook *) 0x10a22200
ret = false
#9 0x0040df3c in client_command_input (cmd=0x10a3f040) at
imap-client.c:673
client = (struct client *) 0x10a3e840
command = (struct command *) 0x7fff0001
__FUNCTION__ = client_command_input
__FUNCTION__ = client_command_input
#10 0x0040de42 in client_handle_next_command (client=0x10a3e840,
remove_io_r=0x7fffea6d) at imap-client.c:740
size = 279029312
#11 0x0040d7b5 in client_handle_input (client=0x10a3e840) at
imap-client.c:777
_data_stack_cur_id = 3
ret = false
remove_io = false
handled_commands = false
__FUNCTION__ = client_handle_input
__FUNCTION__ = client_handle_input
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
Hello Pascal, I've just tested rc6 and get almost the same results. imap still crashes, but Horde still works. I forgot to mention that this is on FreeBSD 8 using gcc 4.6 and LTO. And contrary to what I said in my initial email, it doesn't seem to be ACL plugin related. imap crashes even if it's not in the plugins list. Here is the backtrace: # gdb /usr/libexec/dovecot/imap /path/to/core Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/dovecot/libdovecot-storage.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot-storage.so.0 Reading symbols from /usr/lib/dovecot/libdovecot.so.0...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/libdovecot.so.0 Reading symbols from /lib/libc.so.7...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.7 Reading symbols from /usr/lib/librt.so.1...(no debugging symbols found)...done. Loaded symbols for /usr/lib/librt.so.1 Reading symbols from /usr/lib/dovecot/lib01_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib01_acl_plugin.so Reading symbols from /usr/lib/dovecot/lib02_imap_acl_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib02_imap_acl_plugin.so Reading symbols from /usr/lib/dovecot/lib10_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib10_quota_plugin.so Reading symbols from /usr/lib/dovecot/lib11_imap_quota_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib11_imap_quota_plugin.so Reading symbols from /usr/lib/dovecot/lib11_trash_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib11_trash_plugin.so Reading symbols from /usr/lib/dovecot/lib20_autocreate_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib20_autocreate_plugin.so Reading symbols from /usr/lib/dovecot/lib20_fts_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib20_fts_plugin.so Reading symbols from /usr/lib/dovecot/lib20_zlib_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib20_zlib_plugin.so Reading symbols from /lib/libz.so.5...(no debugging symbols found)...done. Loaded symbols for /lib/libz.so.5 Reading symbols from /usr/lib/libbz2.so.4...(no debugging symbols found)...done. Loaded symbols for /usr/lib/libbz2.so.4 Reading symbols from /usr/lib/dovecot/lib21_fts_squat_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib21_fts_squat_plugin.so Reading symbols from /usr/lib/dovecot/lib30_imap_zlib_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib30_imap_zlib_plugin.so Reading symbols from /usr/lib/dovecot/lib90_antispam_plugin.so...(no debugging symbols found)...done. Loaded symbols for /usr/lib/dovecot/lib90_antispam_plugin.so Reading symbols from /libexec/ld-elf.so.1...(no debugging symbols found)...done. Loaded symbols for /libexec/ld-elf.so.1 #0 0x105c64e7 in imap_match () from /usr/lib/dovecot/libdovecot.so.0 (gdb) bt full #0 0x105c64e7 in imap_match () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x104b4bf6 in mailbox_list_iter_next () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #2 0x00416b99 in cmd_list_continue.6853 () No symbol table info available. #3 0x0042166d in cmd_list_full () No symbol table info available. #4 0x in ?? () No symbol table info available. #5 0x8080808080808080 in ?? () No symbol table info available. #6 0x0004 in ?? () No symbol table info available. #7 0x10a3f1a8 in ?? () No symbol table info available. #8 0x10aa4390 in ?? () No symbol table info available. #9 0x10a3f174 in ?? () No symbol table info available. #10 0x7fffe9a0 in ?? () No symbol table info available. #11 0x10596e4f in p_strdup () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #12 0x10a22200 in ?? () No symbol table info available. #13 0x10aa4458 in ?? () No symbol table info available. #14 0x10aa4340 in ?? () No symbol table info available. #15 0x10aa4498 in ?? () No symbol table info available. #16 0x000110a3f040 in ?? () No symbol table info available. #17 0x10a3f128 in ?? () No symbol table info available. #18 0x10a3e840 in ?? () No symbol table info available. #19 0x10a3f040 in ?? () No symbol table info available. #20 0x10a22200 in ?? () No symbol table info available. #21 0x0001 in ?? () No symbol table info available. #22 0x10a22200 in ?? () No symbol table info available. #23 0x in ?? () No symbol table info available. #24 0x0041d320 in client_command_input.12433
Re: [Dovecot] [Dovecot 2.1] imap service crash when using some clients
On 13.2.2012, at 2.02, interfaSys sàrl wrote: #0 0x105c64e7 in imap_match () from /usr/lib/dovecot/libdovecot.so.0 No symbol table info available. #1 0x104b4bf6 in mailbox_list_iter_next () from /usr/lib/dovecot/libdovecot-storage.so.0 No symbol table info available. #2 0x00416b99 in cmd_list_continue.6853 () No symbol table info available. #3 0x0042166d in cmd_list_full () This crash looks interesting, but unfortunately the libraries are stripped of debug symbols so I can't really guess why it would crash here. By default Dovecot includes them, so you must have stripped them yourself. Can you get another backtrace with debug symbols enabled? Or alternatively can you look at what IMAP command Horde sends that crashes Dovecot? http://wiki2.dovecot.org/Debugging/Rawlog shows one way of recording the IMAP traffic.
Re: [Dovecot] Dovecot 2, Imap service, client_limit
On Tue, Jul 19, 2011 at 3:56 PM, Steve Fatula compconsult...@yahoo.com wrote: I see back in November of last year, a thread about using client_limit in the imap service (not imap-login) that would allow each imap process serve more than one connection. Sounded good, until I tried it! When I did, unlike the OP of that thread, I got: dovecot: imap(submit.user): Fatal: setuid(503(submit.user) from userdb lookup) failed with euid=501(links): Operation not permitted (This binary should probably be called with process user set to 503(submit.user) instead of 501(links)) So, it would appear that this does not work. Still, the thread was posting results of their testing even that showed it worked. Sample message within the thread, read for more: http://www.dovecot.org/list/dovecot/2010-November/054893.html I'd love to be able to use a single imap process for more than one connection. Is this still possible, or, not? If so, how? Steve In my case, we use a single shared user for all mailboxes, so there's no UID issue. The imap process is always running as that one UID, so it doesn't ever try to setuid to something else. Timo, is there some way/setting to only let client_limit != 1 apply to processes running as the same user? I.e. if a imap process (with client_limit 1) was running as UID 501 (to use the OP's uids), and imap-login needed to send UID 503 to an imap process, it wouldn't send it to the one running as UID 501, but rather either create new imap proc or if UID 503 already had a imap proc running, then send UID 503 to that one. (I realize that makes almost no grammatical sense, but hopefully you know what I mean).
Re: [Dovecot] Dovecot 2, Imap service, client_limit
Mark Moseley moseleymark at gmail.com writes: Timo, is there some way/setting to only let client_limit != 1 apply to processes running as the same user? I.e. if a imap process (with client_limit 1) was running as UID 501 (to use the OP's uids), and imap-login needed to send UID 503 to an imap process, it wouldn't send it to the one running as UID 501, but rather either create new imap proc or if UID 503 already had a imap proc running, then send UID 503 to that one. That would be wonderful since then, clients with 5 connections say, would all go to one imap process instead of 5.
Re: [Dovecot] Dovecot 2, Imap service, client_limit
Hi All Exchange meeting plugin is not working , I am not able to save calendar request .. need help . Can some one help me -Original Message- From: dovecot-boun...@dovecot.org [mailto:dovecot-boun...@dovecot.org] On Behalf Of Mark Moseley Sent: Wednesday, July 20, 2011 4:38 AM Cc: dovecot@dovecot.org Subject: Re: [Dovecot] Dovecot 2, Imap service, client_limit On Tue, Jul 19, 2011 at 3:56 PM, Steve Fatula compconsult...@yahoo.com wrote: I see back in November of last year, a thread about using client_limit in the imap service (not imap-login) that would allow each imap process serve more than one connection. Sounded good, until I tried it! When I did, unlike the OP of that thread, I got: dovecot: imap(submit.user): Fatal: setuid(503(submit.user) from userdb lookup) failed with euid=501(links): Operation not permitted (This binary should probably be called with process user set to 503(submit.user) instead of 501(links)) So, it would appear that this does not work. Still, the thread was posting results of their testing even that showed it worked. Sample message within the thread, read for more: http://www.dovecot.org/list/dovecot/2010-November/054893.html I'd love to be able to use a single imap process for more than one connection. Is this still possible, or, not? If so, how? Steve In my case, we use a single shared user for all mailboxes, so there's no UID issue. The imap process is always running as that one UID, so it doesn't ever try to setuid to something else. Timo, is there some way/setting to only let client_limit != 1 apply to processes running as the same user? I.e. if a imap process (with client_limit 1) was running as UID 501 (to use the OP's uids), and imap-login needed to send UID 503 to an imap process, it wouldn't send it to the one running as UID 501, but rather either create new imap proc or if UID 503 already had a imap proc running, then send UID 503 to that one. (I realize that makes almost no grammatical sense, but hopefully you know what I mean). Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at a href=http://www.techmahindra.com/Disclaimer.html;http://www.techmahindra.com/Disclaimer.html/a externally and a href=http://tim.techmahindra.com/Disclaimer.html;http://tim.techmahindra.com/Disclaimer.html/a internally within Tech Mahindra.
Re: [Dovecot] Dovecot as IMAP proxy to Exchange
Hugo Monteiro wrote: Hello list, I'm looking into the possibility to setup dovecot to act as an IMAP proxy to an Exchange server. Things i know beforehand: - I will not be able to use the ldap (Active Directory) user DN for auth binds (but i discovered that i could could use the user userPrincipalName attribute as bind DN. I tested it using ldapsearch and it worked fine.) - I will not be able to perform any unbinded searches. - The Exchange server is unique, so i can setup a static proxy route to the server. Given the above, i'd like to post some questions: 1 - Will i be able to use auth_bind = yes given the restrictions? My first guess is that this might work if i use something like auth_bind_userdn = %...@example.org Yes, you can do things like auth_bind_userdn = %...@example.org As long as it works to bind that way with ldapsearch you should be fine. 2 - Will i be able to specify a static route to the exchange server, not having to rely on that information from the AD itself? Don't know the answer here. Another thing i'd like to know is if NTLM auth can be used while dovecot acts only as proxy. Hmm, I don't think so with auth_bind = yes. I could be wrong though.
Re: [Dovecot] dovecot 2.0.4 imap service error
here's the gdb backtrace. gdb /usr/libexec/dovecot/imap GNU gdb 6.8 Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-slackware-linux... (no debugging symbols found) (gdb) run Starting program: /usr/libexec/dovecot/imap (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] (no debugging symbols found) Debug: Loading modules from directory: /usr/lib64/dovecot [New Thread 0x7f5d50d996f0 (LWP 17175)] (no debugging symbols found) Debug: Module loaded: /usr/lib64/dovecot/lib10_quota_plugin.so (no debugging symbols found) Debug: Module loaded: /usr/lib64/dovecot/lib11_imap_quota_plugin.so (no debugging symbols found) Debug: Module loaded: /usr/lib64/dovecot/lib11_trash_plugin.so (no debugging symbols found) Debug: Module loaded: /usr/lib64/dovecot/lib20_autocreate_plugin.so (no debugging symbols found) Debug: Module loaded: /usr/lib64/dovecot/lib20_fts_plugin.so (no debugging symbols found) Debug: Module loaded: /usr/lib64/dovecot/lib21_fts_squat_plugin.so (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) Debug: Effective uid=0, gid=0, home=/root Debug: quota: No quota setting - plugin disabled Debug: Namespace : type=private, prefix=, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes location=mdbox:/var/mail/mdbox/root:INDEX=/var/mail/mdbox/root Debug: fs: root=/var/mail/mdbox/root, index=, control=, inbox= Program received signal SIGSEGV, Segmentation fault. ---Type return to continue, or q return to quit--- [Switching to Thread 0x7f5d50d996f0 (LWP 17175)] 0x7f5d4f662572 in quota_get_mail_user_quota () from /usr/lib64/dovecot/lib10_quota_plugin.so (gdb) bt full #0 0x7f5d4f662572 in quota_get_mail_user_quota () from /usr/lib64/dovecot/lib10_quota_plugin.so No symbol table info available. #1 0x7f5d4f6626a1 in quota_mailbox_list_created () from /usr/lib64/dovecot/lib10_quota_plugin.so No symbol table info available. #2 0x7f5d50912ab1 in hook_mailbox_list_created () from /usr/lib64/dovecot/libdovecot-storage.so.0 No symbol table info available. #3 0x7f5d509167f0 in mailbox_list_create () from /usr/lib64/dovecot/libdovecot-storage.so.0 No symbol table info available. #4 0x7f5d5091229d in mail_storage_create () from /usr/lib64/dovecot/libdovecot-storage.so.0 No symbol table info available. #5 0x7f5d5090bd57 in mail_namespaces_init () from /usr/lib64/dovecot/libdovecot-storage.so.0 No symbol table info available. #6 0x7f5d50918c07 in mail_storage_service_next () from /usr/lib64/dovecot/libdovecot-storage.so.0 No symbol table info available. #7 0x7f5d50919c54 in mail_storage_service_lookup_next () from /usr/lib64/dovecot/libdovecot-storage.so.0 ---Type return to continue, or q return to quit--- No symbol table info available. #8 0x00419244 in ?? () No symbol table info available. #9 0x004196d2 in main () No symbol table info available. (gdb) On Mon, Sep 27, 2010 at 4:28 PM, Timo Sirainen t...@iki.fi wrote: On 27.9.2010, at 22.17, Nishant Limbachia wrote: Just upgraded from 2.0.3 to 2.0.4 and getting this message in the logs (repeated several times) master: Error: service(imap): child 9631 killed with signal 11 Can you get gdb backtrace? http://dovecot.org/bugreport.html I'm using mdbox and had no problems using 2.0.3 until I upgraded this morning. I understand there were some Index changes and I'm not keeping indexes in a separate directory. but still I've made this change to configuration file. mail_location = mdbox:/var/mail/mdbox/%u:INDEX=/var/mail/mdbox/%u There's no need to do that.
Re: [Dovecot] dovecot 2.0.4 imap service error
On 27.9.2010, at 22.17, Nishant Limbachia wrote: Just upgraded from 2.0.3 to 2.0.4 and getting this message in the logs (repeated several times) master: Error: service(imap): child 9631 killed with signal 11 Can you get gdb backtrace? http://dovecot.org/bugreport.html I'm using mdbox and had no problems using 2.0.3 until I upgraded this morning. I understand there were some Index changes and I'm not keeping indexes in a separate directory. but still I've made this change to configuration file. mail_location = mdbox:/var/mail/mdbox/%u:INDEX=/var/mail/mdbox/%u There's no need to do that.
Re: [Dovecot] dovecot 2.0, imap-login killed with signal 11
On Thu, 2010-07-01 at 16:42 +0200, Burckhard Schmidt wrote: imap(userx): Info: Disconnected: Logged out byte... master: Error: service(imap-login): child 20241 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) Can you get gdb backtrace? The easiest would be if you managed to attach gdb into the correct imap-login process: log in gdb -p pid of imap-login cont log out bt full Also it's possible that it's already been fixed. You could try latest nightly snapshot. http://dovecot.org/nightly/
Re: [Dovecot] dovecot 2.0, imap-login killed with signal 11
Am 01.07.2010 16:49, schrieb Timo Sirainen: On Thu, 2010-07-01 at 16:42 +0200, Burckhard Schmidt wrote: imap(userx): Info: Disconnected: Logged out byte... master: Error: service(imap-login): child 20241 killed with signal 11 (core not dumped - set drop_priv_before_exec=yes) Can you get gdb backtrace? The easiest would be if you managed to attach gdb into the correct imap-login process: log in gdb -ppid of imap-login cont log out bt full Attaching to process 20797 Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1] 0xfedcc568 in ?? () (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. 0xfed57544 in ?? () (gdb) bt full #0 0xfed57544 in ?? () No symbol table info available. I think no good result. I'll try next nithly. Also it's possible that it's already been fixed. You could try latest nightly snapshot. http://dovecot.org/nightly/ -- Regards --- Burckhard Schmidt
Re: [Dovecot] dovecot 2.0, imap-login killed with signal 11
On Thu, 2010-07-01 at 17:13 +0200, Burckhard Schmidt wrote: gdb -ppid of imap-login .. Program received signal SIGSEGV, Segmentation fault. 0xfed57544 in ?? () (gdb) bt full #0 0xfed57544 in ?? () No symbol table info available. I think no good result. Yeah, not useful. I think with Solaris you need to do it like: gdb /usr/dovecotBeta6/libexec/dovecot/imap-login imap-login pid
Re: [Dovecot] Dovecot access imap folder via POP3
On 05/26/2010 10:52 PM Vincze Janos Istvan wrote: Dear All, I use postfix and dovecot (1.1.11) combo with maildir format. I would have a question about dovecot config. Can I confiugre dovecot to download mails from IMAP folders via POP3? Now, mails can be downloaded only from .INBOX. POP3 knows only the INBOX. But there's the virtual plugin, which requires Dovecot = v1.2.0. This allows you to 'map' one or more mailboxes to the INBOX for pop3. http://wiki.dovecot.org/Plugins/Virtual Regards, Pascal -- The trapper recommends today: defaced.1014...@localdomain.org
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Timo, I reinstalled all our servers with -O0 and full debugging on
-gdwarf-2 -g3. I should be able to look up anything you need done now.
Here's some more examples with the data you asked for last time, now
without optimization. I also noticed that there are a few users that
seem to be regulars with this problem.
#4 0x004d8fd7 in i_panic (format=0x501688 file %s: line %d
(%s): assertion failed: (%s)) at failures.c:207
args = {{gp_offset = 40, fp_offset = 48, overflow_arg_area =
0x7fffcf52b5a0, reg_save_area = 0x7fffcf52b4e0}}
#5 0x0044f34e in maildir_uidlist_records_array_delete
(uidlist=0x1b612330, rec=0x1b61f1f8) at maildir-uidlist.c:405
recs = (struct maildir_uidlist_rec * const *) 0x1b607f60
pos = (struct maildir_uidlist_rec * const *) 0x0
idx = 0
count = 2
__PRETTY_FUNCTION__ = maildir_uidlist_records_array_delete
#6 0x0044f8fc in maildir_uidlist_next (uidlist=0x1b612330,
line=0x1b60426a
1249562340.M302085P7316V04240006I00DB2CF1_0.gehenna7.rutgers.edu,S=19277:2,S)
at maildir-uidlist.c:552
rec = (struct maildir_uidlist_rec *) 0x1b6209f8
old_rec = (struct maildir_uidlist_rec *) 0x1b61f1f8
recs = (struct maildir_uidlist_rec * const *) 0x1b604264
count = 0
uid = 2807
(gdb) fr 5
#5 0x0044f34e in maildir_uidlist_records_array_delete
(uidlist=0x1b612330, rec=0x1b61f1f8) at maildir-uidlist.c:405
405i_assert(pos != NULL);
(gdb) p *recs
$1 = (struct maildir_uidlist_rec * const) 0x1b61fa60
(gdb) p count
$2 = 2
(gdb) p *recs[0]
$3 = {uid = 2735, flags = 6, filename = 0x1b61fa78
1262739815.M913182P4280V04240006I014D0F92_0.gehenna7.rutgers.edu,S=11791:2,,
extensions = 0x1b620980 W12036}
(gdb) p *recs[1]
$4 = {uid = 2736, flags = 0, filename = 0x1b6209a0
1262739645.M307617P13458V04240006I014D0F91_0.gehenna10.rutgers.edu,S=5005:2,S,
extensions = 0x1b6209f0 W5124}
(gdb)
Another user for comparison:
(gdb) fr 5
#5 0x0044f34e in maildir_uidlist_records_array_delete
(uidlist=0x6bd7680, rec=0x6bc93d0) at maildir-uidlist.c:405
405i_assert(pos != NULL);
(gdb) p *recs
$1 = (struct maildir_uidlist_rec * const) 0x6d5c418
(gdb) p count
$2 = 7
(gdb) p *recs[0]
$3 = {uid = 52566, flags = 4, filename = 0x6d5c438
1262781360.M836147P9323V04240007I0148DC53_0.gehenna5.rutgers.edu,S=2157:2,a,
extensions = 0x6d5c430 W2201}
(gdb) p *recs[1]
$4 = {uid = 52568, flags = 0, filename = 0x6cd4590
126262.M94168P6001V04240006I003C41C2_0.gehenna10.rutgers.edu,S=22946:2,Sa,
extensions = 0x6cd4588 W23481}
(gdb) p *recs[2]
$5 = {uid = 52569, flags = 0, filename = 0x6bc9328
1041233872.06.mbox:2,S, extensions = 0x6bc9318 W6334}
(gdb) p *recs[3]
$6 = {uid = 52570, flags = 0, filename = 0x6bc9370
1041233872.13.mbox:2,S, extensions = 0x6bc9360 W1193}
(gdb) p *recs[4]
$7 = {uid = 52571, flags = 0, filename = 0x6bc92e0
1041233872.14.mbox:2,RS, extensions = 0x6bc92d0 W3095}
(gdb) p *recs[5]
$8 = {uid = 52572, flags = 4, filename = 0x6d58ec8
1262782141.M730129P15749V03E80006I0148DC54_0.gehenna9.rutgers.edu,S=7454:2,,
extensions = 0x6d62160 W7626}
(gdb) p *recs[6]
$9 = {uid = 52573, flags = 0, filename = 0x6d62140
1041233872.16.mbox:2,S, extensions = 0x0}
(gdb)
And one more user:
(gdb) fr 5
#5 0x0044f34e in maildir_uidlist_records_array_delete
(uidlist=0x10f44680, rec=0x10f67120) at maildir-uidlist.c:405
405i_assert(pos != NULL);
(gdb) p *recs
$1 = (struct maildir_uidlist_rec * const) 0x11093760
(gdb) p count
$2 = 2
(gdb) p *recs[0]
$3 = {uid = 55108, flags = 0, filename = 0x11093778
1262788462.M201250P7938V04240006I01EF76E0_0.gehenna10.rutgers.edu,S=1731278:2,,
extensions = 0x1109d240 W1753846}
(gdb) p *recs[1]
$4 = {uid = 55109, flags = 4, filename = 0x1109d268
1262788793.M851477P3866V045C0007I01EF76E3_0.gehenna8.rutgers.edu,S=19990,
extensions = 0x0}
On 12/30/2009 12:10 PM, David Halik wrote:
Ok, I think I've got some more info and a more accurate time line for
you. I tried this on two different dumps from two different users. The
count was 4 in the first example and 0 in the second. I'm guessing
that's considered small? The links to my gdb sessions for both are
below and have some of the info you were looking for. The
corresponding logs are also there so you can see how each failed. I
put everything on pastebin so it's a little easier to see.
By the way, I also found that the stale NFS file handle message does
appear first in each instance, it was just farther back in the logs.
Lowering uid message also appears immediately after every stale NFS
message, which in turn causes all of this n amount of time later
(sometimes 5 minutes, sometimes 20) when a user does a new action. The
file reappeared message only occurs some of the time. Here's the
chain of events in every case so far that I can see:
1) fdatasync(/rci/nqu/rci/u8/user/dovecot/.INBOX/dovecot-uidlist)
failed: Stale NFS file handle
2)
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Ok, I think I've got some more info and a more accurate time line for you. I tried this on two different dumps from two different users. The count was 4 in the first example and 0 in the second. I'm guessing that's considered small? The links to my gdb sessions for both are below and have some of the info you were looking for. The corresponding logs are also there so you can see how each failed. I put everything on pastebin so it's a little easier to see. By the way, I also found that the stale NFS file handle message does appear first in each instance, it was just farther back in the logs. Lowering uid message also appears immediately after every stale NFS message, which in turn causes all of this n amount of time later (sometimes 5 minutes, sometimes 20) when a user does a new action. The file reappeared message only occurs some of the time. Here's the chain of events in every case so far that I can see: 1) fdatasync(/rci/nqu/rci/u8/user/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle 2) /rci/nqu/rci/u8/user/dovecot/.INBOX/dovecot-uidlist: next_uid was lowered (n - n-1, hdr=n-1) ...a few minutes later... (may or may not be a message reappeared warning at this point) 3) /rci/nqu/rci/u8/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 3: 1261057547.M378185P17303V03E80002I0197FB4A_0.gehenna9.rutgers.edu,S=7174:2,RS (uid i - n+1,2,3 ) 4) Panic: file maildir-uidlist.c: line 405 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) One thing to note, after the Expunged message reappeared, giving a new UID he died quickly and one more than one server simultaneously. The gdb output is from server gehenna11 of that log file. The uid in *recs[0] is also the number that you can see in the logs being lowered from 719 - 718. First user log: http://pastebin.com/m1718f07b First user gdb: http://pastebin.com/m40088dc8 The second user also died on more than one server. The output is also from gehenna11 Second user log: http://pastebin.com/f3a1756f2 Second user gdb: http://pastebin.com/m59aacde4 On 12/29/2009 7:50 PM, Timo Sirainen wrote: On 29.12.2009, at 19.09, David Halik wrote: I'll definitely get back to you on this. Right now we're closed until after New Years and I don't want to go updating the dovecot package on all of our servers until we're all back at work. I did do some quick poking around and the count is optimized out, so I'll have the package rebuilt without optimization and let you what the values are at the beginning of next week. Thanks again. well, you can probably also get the values in a bit more difficult way: p count = p uidlist.records.arr.buffer.used / uidlist.records.arr.element_size p recs[n] = p *(*uidlist.records.v)[n]
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On Wed, 2009-12-23 at 10:37 -0800, Brandon Davidson wrote: We too have set dotlock_use_excl = no. I'm not seeing the Stale NFS file handle message any more, but I am still seeing a crash. The crashes seem to be leaving the indexes in a bad state: Dec 23 09:07:44 oh-popmap3p dovecot: imap: user=cnisser, rip=x.x.x.x, pid=30101: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) You mean this doesn't get fixed by itself? It's not indexes, but dovecot-uidlist file that's the problem.. pid=7641: read(/home6/joet/Maildir/dovecot-uidlist) failed: Input/output error These just shouldn't be happening.. Or perhaps that's the same problem as ESTALE. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Hey Timo, hope you enjoyed your vacation. :) I just wanted to point out that I'm still seeing the (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) dump even after your patch. The (match == IMAP_MATCH_YES) dump is definitely fixed, but the other dump still remains... On 12/24/2009 11:39 AM, David Halik wrote: I should probably also post the messages leading up for reference. Note that I did not see any stale NFS messages this time, but did get the usual duplicate file messages: Dec 24 10:43:07 gehenna11 dovecot: IMAP(user): /rci/nqu/rci/u1/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 4: 1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S (uid 514 - 721) Dec 24 10:43:08 gehenna11 dovecot: IMAP(user): Maildir /rci/u1/user/Maildir: Expunged message reappeared, giving a new UID (old uid=516, file=1231952516.M164875P24494V03E80009I01B6DCAC_0.gehenna9.rutgers.edu,S=4355:2,S) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): /rci/nqu/rci/u1/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 6: 1233524267.M97899P9543V04240006I01B6E908_0.gehenna5.rutgers.edu,S=3039:2,S (uid 517 - 723) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): Panic: file maildir-uidlist.c: line 405 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x49edd0] - /usr/libexec/dovecot/imap [0x49ee33] - /usr/libexec/dovecot/imap [0x49e496] - /usr/libexec/dovecot/imap [0x43f064] - /usr/libexec/dovecot/imap(maildir_uidlist_refresh+0x2d0) [0x43fbf0] - /usr/libexec/dovecot/imap [0x43c91f] - /usr/libexec/dovecot/imap(maildir_storage_sync_init+0x14e) [0x43cefe] - /usr/libexec/dovecot/imap(imap_sync_init+0x67) [0x4283d7] - /usr/libexec/dovecot/imap [0x41bf5e] - /usr/libexec/dovecot/imap [0x458ecd] - /usr/libexec/dovecot/imap(io_loop_handle_timeouts+0x8b) [0x4a5f6b] - /usr/libexec/dovecot/imap(io_loop_handler_run+0x73) [0x4a6bd3] - /usr/libexec/dovecot/imap(io_loop_run+0x1d) [0x4a5d6d] - /usr/libexec/dovecot/imap(main+0x620) [0x428f20] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x354301d994] - /usr/libexec/dovecot/imap [0x419ac9] Dec 24 10:44:38 gehenna11 dovecot: dovecot: child 19032 (imap) killed with signal 6 (core dumped) On 12/24/2009 11:26 AM, David Halik wrote: Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) This is hopefully fixed by: http://hg.dovecot.org/dovecot-1.2/rev/d00abdaf9df2 Timo, I came into work this morning and found three new core dumps from maildir_uidlist_records_array_delete while running the patch you gave me yesterday, so I guess it's not fixed after all. I double checked that it is in fact running your patch, and it is. You can tell also that maildir-uidlist.c: line 403 changed to 405. Here's the short backtrace: #0 0x003543030265 in raise (sig=value optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x003543031d10 in abort () at abort.c:88 #2 0x0049eddd in default_fatal_finish (type=value optimized out, status=0) at failures.c:160 #3 0x0049ee33 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=value optimized out, args=value optimized out) at failures.c:443 #4 0x0049e496 in i_panic (format=0x6 Address 0x6 out of bounds) at failures.c:207 #5 0x0043f064 in maildir_uidlist_records_array_delete (uidlist=value optimized out, rec=0x16dbd48) at maildir-uidlist.c:405 #6 0x0043fbf0 in maildir_uidlist_refresh (uidlist=0x16c75b0) at maildir-uidlist.c:552 #7 0x0043c91f in maildir_sync_context (ctx=0x16a7188, forced=false, find_uid=0x0, lost_files_r=0x7fff86f83d87) at maildir-sync.c:659 #8 0x0043cefe in maildir_storage_sync_init (box=0x16b64f8, flags=0) at maildir-sync.c:924 #9 0x004283d7 in imap_sync_init (client=0x16b27a0, box=0x16b64f8, imap_flags=0, flags=0) at imap-sync.c:146 #10 0x0041bf5e in idle_sync_now (box=0x4a58, ctx=0x16b3db8) at cmd-idle.c:127 #11 0x00458ecd in check_timeout (ibox=0x16b64f8) at index-mailbox-check.c:43 #12 0x004a5f6b in io_loop_handle_timeouts (ioloop=0x16afb60) at ioloop.c:313 #13 0x004a6bd3 in io_loop_handler_run (ioloop=0x16afb60) at ioloop-epoll.c:180 #14 0x004a5d6d in io_loop_run (ioloop=0x16afb60) at ioloop.c:335 #15 0x00428f20 in main (argc=value optimized out, argv=value optimized out, envp=0x7fff86f840b8) at main.c:327 And the full backtrace: http://pastebin.com/f651f649e
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On Thu, 2009-12-24 at 11:39 -0500, David Halik wrote: Dec 24 10:43:07 gehenna11 dovecot: IMAP(user): /rci/nqu/rci/u1/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 4: 1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S (uid 514 - 721) Dec 24 10:43:08 gehenna11 dovecot: IMAP(user): Maildir /rci/u1/user/Maildir: Expunged message reappeared, giving a new UID (old uid=516, file=1231952516.M164875P24494V03E80009I01B6DCAC_0.gehenna9.rutgers.edu,S=4355:2,S) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): /rci/nqu/rci/u1/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 6: 1233524267.M97899P9543V04240006I01B6E908_0.gehenna5.rutgers.edu,S=3039:2,S (uid 517 - 723) Wonder if there's a corresponding Expunged message reappeared, giving a new UID (old uid=x) having Dupliate file entry .. (uid x - for each log line? Meaning that the duplicate file entries are caused by those reappearing messages? (And the reappearing messages are probably caused by dentry caching issues.) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): Panic: file maildir-uidlist.c: line 405 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) I couldn't previously really figure out how this could happen, even when manually causing the expunged message reappeared error. Could you do in gdb something like: fr 6 (or whatever frame gives usable results) p *rec p count p *recs[0] p *recs[1] p *recs[..up until count-1] If count is large, the main things I want to know are: 1) Is the array sorted (recs[n]-uid recs[n+1]-uid always)? 2) is rec-uid anywhere in the recs array? If it complains about values being optimized away, recompile without -O2. I usually do that by just removing it from src/lib-storage/index/maildir/Makefile and touch dovecot-uidlist.c and make + make install. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On 12/29/2009 6:18 PM, Timo Sirainen wrote: Wonder if there's a corresponding Expunged message reappeared, giving a new UID (old uid=x) having Dupliate file entry .. (uid x - for each log line? Meaning that the duplicate file entries are caused by those reappearing messages? (And the reappearing messages are probably caused by dentry caching issues.) I'm wondering there are multiple causes going on that all spawn the same error. Is some instances, yes I do see the Duplicate file... preceding the error, in some instances I don't, but I do get the NFS stale message then. The output above just happens to be from during the duplicate instance. Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): Panic: file maildir-uidlist.c: line 405 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) If it complains about values being optimized away, recompile without -O2. I usually do that by just removing it from src/lib-storage/index/maildir/Makefile and touch dovecot-uidlist.c and make + make install. I'll definitely get back to you on this. Right now we're closed until after New Years and I don't want to go updating the dovecot package on all of our servers until we're all back at work. I did do some quick poking around and the count is optimized out, so I'll have the package rebuilt without optimization and let you what the values are at the beginning of next week. Thanks again.
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On 29.12.2009, at 19.09, David Halik wrote: I'll definitely get back to you on this. Right now we're closed until after New Years and I don't want to go updating the dovecot package on all of our servers until we're all back at work. I did do some quick poking around and the count is optimized out, so I'll have the package rebuilt without optimization and let you what the values are at the beginning of next week. Thanks again. well, you can probably also get the values in a bit more difficult way: p count = p uidlist.records.arr.buffer.used / uidlist.records.arr.element_size p recs[n] = p *(*uidlist.records.v)[n]
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) This is hopefully fixed by: http://hg.dovecot.org/dovecot-1.2/rev/d00abdaf9df2 Timo, I came into work this morning and found three new core dumps from maildir_uidlist_records_array_delete while running the patch you gave me yesterday, so I guess it's not fixed after all. I double checked that it is in fact running your patch, and it is. You can tell also that maildir-uidlist.c: line 403 changed to 405. Here's the short backtrace: #0 0x003543030265 in raise (sig=value optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x003543031d10 in abort () at abort.c:88 #2 0x0049eddd in default_fatal_finish (type=value optimized out, status=0) at failures.c:160 #3 0x0049ee33 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=value optimized out, args=value optimized out) at failures.c:443 #4 0x0049e496 in i_panic (format=0x6 Address 0x6 out of bounds) at failures.c:207 #5 0x0043f064 in maildir_uidlist_records_array_delete (uidlist=value optimized out, rec=0x16dbd48) at maildir-uidlist.c:405 #6 0x0043fbf0 in maildir_uidlist_refresh (uidlist=0x16c75b0) at maildir-uidlist.c:552 #7 0x0043c91f in maildir_sync_context (ctx=0x16a7188, forced=false, find_uid=0x0, lost_files_r=0x7fff86f83d87) at maildir-sync.c:659 #8 0x0043cefe in maildir_storage_sync_init (box=0x16b64f8, flags=0) at maildir-sync.c:924 #9 0x004283d7 in imap_sync_init (client=0x16b27a0, box=0x16b64f8, imap_flags=0, flags=0) at imap-sync.c:146 #10 0x0041bf5e in idle_sync_now (box=0x4a58, ctx=0x16b3db8) at cmd-idle.c:127 #11 0x00458ecd in check_timeout (ibox=0x16b64f8) at index-mailbox-check.c:43 #12 0x004a5f6b in io_loop_handle_timeouts (ioloop=0x16afb60) at ioloop.c:313 #13 0x004a6bd3 in io_loop_handler_run (ioloop=0x16afb60) at ioloop-epoll.c:180 #14 0x004a5d6d in io_loop_run (ioloop=0x16afb60) at ioloop.c:335 #15 0x00428f20 in main (argc=value optimized out, argv=value optimized out, envp=0x7fff86f840b8) at main.c:327 And the full backtrace: http://pastebin.com/f651f649e -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I should probably also post the messages leading up for reference. Note that I did not see any stale NFS messages this time, but did get the usual duplicate file messages: Dec 24 10:43:07 gehenna11 dovecot: IMAP(user): /rci/nqu/rci/u1/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 4: 1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S (uid 514 - 721) Dec 24 10:43:08 gehenna11 dovecot: IMAP(user): Maildir /rci/u1/user/Maildir: Expunged message reappeared, giving a new UID (old uid=516, file=1231952516.M164875P24494V03E80009I01B6DCAC_0.gehenna9.rutgers.edu,S=4355:2,S) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): /rci/nqu/rci/u1/user/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 6: 1233524267.M97899P9543V04240006I01B6E908_0.gehenna5.rutgers.edu,S=3039:2,S (uid 517 - 723) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): Panic: file maildir-uidlist.c: line 405 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 24 10:44:38 gehenna11 dovecot: IMAP(user): Raw backtrace: /usr/libexec/dovecot/imap [0x49edd0] - /usr/libexec/dovecot/imap [0x49ee33] - /usr/libexec/dovecot/imap [0x49e496] - /usr/libexec/dovecot/imap [0x43f064] - /usr/libexec/dovecot/imap(maildir_uidlist_refresh+0x2d0) [0x43fbf0] - /usr/libexec/dovecot/imap [0x43c91f] - /usr/libexec/dovecot/imap(maildir_storage_sync_init+0x14e) [0x43cefe] - /usr/libexec/dovecot/imap(imap_sync_init+0x67) [0x4283d7] - /usr/libexec/dovecot/imap [0x41bf5e] - /usr/libexec/dovecot/imap [0x458ecd] - /usr/libexec/dovecot/imap(io_loop_handle_timeouts+0x8b) [0x4a5f6b] - /usr/libexec/dovecot/imap(io_loop_handler_run+0x73) [0x4a6bd3] - /usr/libexec/dovecot/imap(io_loop_run+0x1d) [0x4a5d6d] - /usr/libexec/dovecot/imap(main+0x620) [0x428f20] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x354301d994] - /usr/libexec/dovecot/imap [0x419ac9] Dec 24 10:44:38 gehenna11 dovecot: dovecot: child 19032 (imap) killed with signal 6 (core dumped) On 12/24/2009 11:26 AM, David Halik wrote: Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) This is hopefully fixed by: http://hg.dovecot.org/dovecot-1.2/rev/d00abdaf9df2 Timo, I came into work this morning and found three new core dumps from maildir_uidlist_records_array_delete while running the patch you gave me yesterday, so I guess it's not fixed after all. I double checked that it is in fact running your patch, and it is. You can tell also that maildir-uidlist.c: line 403 changed to 405. Here's the short backtrace: #0 0x003543030265 in raise (sig=value optimized out) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #1 0x003543031d10 in abort () at abort.c:88 #2 0x0049eddd in default_fatal_finish (type=value optimized out, status=0) at failures.c:160 #3 0x0049ee33 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=value optimized out, args=value optimized out) at failures.c:443 #4 0x0049e496 in i_panic (format=0x6 Address 0x6 out of bounds) at failures.c:207 #5 0x0043f064 in maildir_uidlist_records_array_delete (uidlist=value optimized out, rec=0x16dbd48) at maildir-uidlist.c:405 #6 0x0043fbf0 in maildir_uidlist_refresh (uidlist=0x16c75b0) at maildir-uidlist.c:552 #7 0x0043c91f in maildir_sync_context (ctx=0x16a7188, forced=false, find_uid=0x0, lost_files_r=0x7fff86f83d87) at maildir-sync.c:659 #8 0x0043cefe in maildir_storage_sync_init (box=0x16b64f8, flags=0) at maildir-sync.c:924 #9 0x004283d7 in imap_sync_init (client=0x16b27a0, box=0x16b64f8, imap_flags=0, flags=0) at imap-sync.c:146 #10 0x0041bf5e in idle_sync_now (box=0x4a58, ctx=0x16b3db8) at cmd-idle.c:127 #11 0x00458ecd in check_timeout (ibox=0x16b64f8) at index-mailbox-check.c:43 #12 0x004a5f6b in io_loop_handle_timeouts (ioloop=0x16afb60) at ioloop.c:313 #13 0x004a6bd3 in io_loop_handler_run (ioloop=0x16afb60) at ioloop-epoll.c:180 #14 0x004a5d6d in io_loop_run (ioloop=0x16afb60) at ioloop.c:335 #15 0x00428f20 in main (argc=value optimized out, argv=value optimized out, envp=0x7fff86f840b8) at main.c:327 And the full backtrace: http://pastebin.com/f651f649e -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I switched all of our servers to dotlock_use_excl=no last night, but we're still seeing the errors: Dec 23 08:22:04 gehenna17.rutgers.edu dovecot: imap-login: Login: user=user1, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Dec 23 08:36:21 gehenna11.rutgers.edu dovecot: imap-login: Login: user=user1, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Dec 23 09:17:09 gehenna18.rutgers.edu dovecot: imap-login: Login: user=user1, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Dec 23 10:59:37 gehenna11.rutgers.edu dovecot: IMAP(user1): fdatasync(/rci/nqu/rci/u1/user1/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle Dec 23 10:59:37 gehenna11.rutgers.edu dovecot: IMAP(user1): /rci/nqu/rci/u1/user1/dovecot/.INBOX/dovecot-uidlist: next_uid was lowered (512 - 511, hdr=511) Dec 23 11:05:43 gehenna11.rutgers.edu dovecot: IMAP(user1): Maildir /rci/u1/user1/Maildir: Expunged message reappeared, giving a new UID (old uid=1, file=1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S) Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): /rci/nqu/rci/u1/user1/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 4: 1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S (uid 1 - 514) Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) It must be related to locking though because we can see that the user is logged in on more than one server and the issues occur when the two dovecot instances fight over the uidlist. The second error I'm seeing much more of though. A few users are spawning these errors on almost every connection. This doesn't appear to be locking related, since the user is logged in on only one server as far as I can tell and there are also no NFS or duplicate file errors: Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: imap-login: Login: user=user2, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: IMAP(user2): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: IMAP(user2): Raw backtrace: /usr/libexec/dovecot/imap [0x49ed50] - /usr/libexec/dovecot/imap [0x49edb3] - /usr/libexec/dovecot/imap [0x49e416] - /usr/libexec/dovecot/imap [0x41c7c0] - /us r/libexec/dovecot/imap [0x41c9c2] - /usr/libexec/dovecot/imap(cmd_list_full+0x49a) [0x41d60a] - /usr/libexec/dovecot/imap(cmd_list+0xb) [0x41d8ab] - /usr/libexec/dovecot/imap [0x4208cc] - /usr/libexec/dovecot/imap [0x420982] - /usr/ libexec/dovecot/imap(client_handle_input+0x3f) [0x420abf] - /usr/libexec/dovecot/imap(client_input+0x5f) [0x42160f] - /usr/libexec/dovecot/imap(io_loop_handler_run+0xf8) [0x4a6bd8] - /usr/libexec/dovecot/imap(io_loop_run+0x1d) [0x4a5c ed] - /usr/libexec/dovecot/imap(main+0x620) [0x428ef0] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x38af41d994] - /usr/libexec/dovecot/imap [0x419ac9] Dec 23 11:18:33 gehenna17.rutgers.edu dovecot: imap-login: Login: user=user2, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx, TLS Dec 23 11:18:33 gehenna17.rutgers.edu dovecot: IMAP(user2): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 23 11:18:33 gehenna17.rutgers.edu dovecot: IMAP(user2): Raw backtrace: /usr/libexec/dovecot/imap [0x49ed50] - /usr/libexec/dovecot/imap [0x49edb3] - /usr/libexec/dovecot/imap [0x49e416] - /usr/libexec/dovecot/imap [0x41c7c0] - /us r/libexec/dovecot/imap [0x41c9c2] - /usr/libexec/dovecot/imap(cmd_list_full+0x49a) [0x41d60a] - /usr/libexec/dovecot/imap(cmd_list+0xb) [0x41d8ab] - /usr/libexec/dovecot/imap [0x4208cc] - /usr/libexec/dovecot/imap [0x420982] - /usr/ libexec/dovecot/imap(client_handle_input+0x3f) [0x420abf] - /usr/libexec/dovecot/imap(client_input+0x5f) [0x42160f] - /usr/libexec/dovecot/imap(io_loop_handler_run+0xf8) [0x4a6bd8] - /usr/libexec/dovecot/imap(io_loop_run+0x1d) [0x4a5c ed] - /usr/libexec/dovecot/imap(main+0x620) [0x428ef0] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x38af41d994] - /usr/libexec/dovecot/imap [0x419ac9] On 12/22/2009 08:17 PM, Timo Sirainen wrote: On 22.12.2009, at 16.42, David Halik wrote: I just double checked and we're seeing the same thing here, although we were never running with noac to begin with. Our poor NFS server would melt probably. ;) This is immediately before the crash: Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): fdatasync(/rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle The interesting this is that this function is called only when dovecot-uidlist.lock has been created, i.e. when uidlist is locked, meaning nothing should have deleted the dovecot-uidlist while it was being written to, so this error just
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On Wed, 2009-12-23 at 11:37 -0500, David Halik wrote: Dec 23 11:05:43 gehenna11.rutgers.edu dovecot: IMAP(user1): Maildir /rci/u1/user1/Maildir: Expunged message reappeared, giving a new UID (old uid=1, file=1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S) The above causes: Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): /rci/nqu/rci/u1/user1/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 4: 1231949492.M325236P5922V03E80009I01B6DCA5_0.gehenna9.rutgers.edu,S=4398:2,S (uid 1 - 514) Although in my tests it doesn't.. Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) This is hopefully fixed by: http://hg.dovecot.org/dovecot-1.2/rev/d00abdaf9df2 Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: IMAP(user2): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) So you get a core dump? Could you print a few values: fr 6 (or whatever starts giving the right values) p *ctx p *ctx.ns p ctx.patterns[0] p ctx.patterns[1] p ctx.patterns[2] p match p ns_prefix p p The ctx.patterns values are the most important ones I think. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Timo, On 12/23/09 8:37 AM, David Halik dha...@jla.rutgers.edu wrote: I switched all of our servers to dotlock_use_excl=no last night, but we're still seeing the errors: We too have set dotlock_use_excl = no. I'm not seeing the Stale NFS file handle message any more, but I am still seeing a crash. The crashes seem to be leaving the indexes in a bad state: Dec 23 09:07:44 oh-popmap3p dovecot: imap: user=cnisser, rip=x.x.x.x, pid=30101: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 23 09:07:44 oh-popmap3p dovecot: imap: user=cnisser, rip= x.x.x.x, pid=30101: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x41ccc4] - imap [0x41cd26] - imap [0x4733be] - imap [0x4e4171] - imap(io_loop_handle_timeouts+0x1d) [0x4e41ce] - imap(io_loop_handler_run+0x86) [0x4e4f29] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3217e1d994] - imap [0x419aa9] Dec 23 09:07:45 oh-popmap3p dovecot: dovecot: child 30101 (imap) killed with signal 6 (core dumped) Dec 23 09:09:16 cc-popmap3p dovecot: imap: user=cnisser, rip= x.x.x.x, pid=5975: Corrupted index cache file /home16/cnisser/.imapidx/.INBOX/dovecot.index.cache: invalid record size Dec 23 09:09:17 oh-popmap2p dovecot: imap: user=cnisser, rip=y.y.y.y, pid=3279: read() failed with index cache file /home16/cnisser/.imapidx/.INBOX/dovecot.index.cache: Input/output error Dec 23 09:09:38 cc-popmap3p dovecot: imap: user=cnisser, rip= x.x.x.x, pid=5975: Corrupted index cache file /home16/cnisser/.imapidx/.INBOX/dovecot.index.cache: invalid record size Dec 23 09:18:12 cc-popmap3p dovecot: imap: user=cnisser, rip= x.x.x.x, pid=5975: Corrupted index cache file /home16/cnisser/.imapidx/.INBOX/dovecot.index.cache: invalid record size We're also seeing another odd error that seems to be unrelated to the crashes, but seemed like it bears reporting. Reading of uidlists and cache files seems to intermittently fail with EIO. It doesn't seem to tie in with anything else, and I don't see any corresponding NFS errors in the system log. Dec 23 09:31:06 oh-popmap4p dovecot: imap: user=joet, rip=a.a.a.a, pid=7641: read(/home6/joet/Maildir/dovecot-uidlist) failed: Input/output error Dec 23 09:53:17 cc-popmap2p dovecot: imap: user=catm, rip=b.b.b.b, pid=12840: read(/home3/catm/Maildir/dovecot-uidlist) failed: Input/output error Dec 23 09:59:38 cc-popmap5p dovecot: imap: user=kforrist, rip=c.c.c.c, pid=13539: read() failed with index cache file /home15/kforrist/.imapidx/.INBOX/dovecot.index.cache: Input/output error -Brad
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Dec 23 11:05:44 gehenna18.rutgers.edu dovecot: IMAP(user1): Panic: file
maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete):
assertion failed: (pos != NULL)
This is hopefully fixed by:
http://hg.dovecot.org/dovecot-1.2/rev/d00abdaf9df2
Thanks for the help as always. I'm currently patching 1.2.9 with this
and pushing the changes out to our dovecot servers. I'll update you
later today if we stop seeing the panic.
Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: IMAP(user2): Panic: file
cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match ==
IMAP_MATCH_YES)
So you get a core dump? Could you print a few values:
fr 6 (or whatever starts giving the right values)
p *ctx
p *ctx.ns
p ctx.patterns[0]
p ctx.patterns[1]
p ctx.patterns[2]
p match
p ns_prefix
p p
The ctx.patterns values are the most important ones I think.
The values from lines 5-7 all look the the same. Here's the answers from
line 6 though:
(gdb) fr 6
#6 0x0041c9c2 in cmd_list_continue (cmd=0x1212dcc8) at
cmd-list.c:375
375list_namespace_send_prefix(ctx, TRUE);
(gdb) p *ctx
$17 = {cmd = 0x1212dcc8, ref = 0x12132b50 , patterns = 0x1212de48,
list_flags = 16386, status_items = 0, ns = 0x1212bf70, list_iter =
0x121304f8, ns_prefixes_listed = {arr = {buffer = 0x1212de58,
element_size = 8}, v = 0x1212de58,
v_modifiable = 0x1212de58}, lsub = 0, lsub_no_unsubscribed = 0,
inbox_found = 1, seen_inbox_namespace = 1, cur_ns_match_inbox = 1,
cur_ns_send_prefix = 0, cur_ns_skip_trailing_sep = 1, used_listext = 0}
(gdb) p *ctx.ns
$18 = {next = 0x0, type = NAMESPACE_PRIVATE, sep = 46 '.', real_sep = 46
'.', sep_str = .\000, flags = 8213, prefix = 0x1212bfd0 INBOX.,
prefix_len = 6, alias_for = 0x0, alias_chain_next = 0x0, user = 0x1212b988,
owner = 0x1212b988, list = 0x1212c348, 0x1212c038}
(gdb) p ctx.patterns[0]
$19 = 0x12132b58 Inbox
(gdb) p ctx.patterns[1]
$20 = 0x0
(gdb) p ctx.patterns[2]
$21 = 0x1212de90
(gdb) p match
No symbol match in current context.
(gdb) p ns_prefix
No symbol ns_prefix in current context.
(gdb) p p
No symbol p in current context.
...and here's the full trace for reference
http://pastebin.com/f77189785
--
David Halik
System Administrator
OIT-CSS Rutgers University
dha...@jla.rutgers.edu
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On Wed, 2009-12-23 at 14:06 -0500, David Halik wrote: Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: IMAP(user2): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Fixed: http://hg.dovecot.org/dovecot-1.2/rev/56dd8c276ed6 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
It looks like this and the previous patch you gave me fixed both panics as intended. I pushed the changes out about five hours ago and haven't seen a single core dump yet! Thanks for such a quick fix Timo, you rock as always. If I see any change in behavior I'll post, but I think that did it. I have one or two squat panics that I'm going to send in after the holidays, but they're much less of a concern since we don't run them on our production systems yet and they're not that big of a deal. Thanks again. On 12/23/2009 4:01 PM, Timo Sirainen wrote: On Wed, 2009-12-23 at 14:06 -0500, David Halik wrote: Dec 23 11:18:32 gehenna17.rutgers.edu dovecot: IMAP(user2): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Fixed: http://hg.dovecot.org/dovecot-1.2/rev/56dd8c276ed6
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I'm seeing both of these dumps on multiple users now with 1.2.9, so I went ahead and did backtraces for them both. maildir_uidlist_records_array_delete panic: http://pastebin.com/f20614d8 ns_get_listed_prefix panic: http://pastebin.com/f1420194c On 12/21/2009 12:43 PM, David Halik wrote: Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) I also started receiving a good deal of these, but only from one user so far: Dec 21 12:16:42 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:19:57 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Let me know if you need full backtraces from the core dump. On 12/17/2009 02:06 PM, David Halik wrote: On 12/17/2009 01:07 PM, Timo Sirainen wrote: On Thu, 2009-12-17 at 12:49 -0500, David Halik wrote: I applied those patches to my 1.2.8 installation before 1.2.9 was released and that immediately fixed the expunge crash, but the array_delete bug is still there. Do you also see the duplicate file entry before the crash? Yes, the duplicate file entry is always reported immediately before the crash, just as Ralf reported too. You can see it in this example pastebin I took from one of our users: http://pastebin.com/f29c55de5 maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot Are the index/control files on NFS? Are there multiple different servers accessing mail data? Correct. All index, control files, amd mail storage are located on NFS and there are multiple load balanced servers accessing the NFS data. We're currently running with: mmap_disable = yes dotlock_use_excl = yes fsync_disable = no mail_nfs_storage = yes mail_nfs_index = yes -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
We've started seeing the maildir_uidlist_records_array_delete assert crash as well. It always seems to be preceded by a 'stale NFS file handle' error from a the same user on a different connection. Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: fdatasync(/home11/apbao/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: /home11/apbao/Maildir/dovecot-uidlist: next_uid was lowered (2642 - 2641, hdr=2641) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3c4ea1d994] - imap [0x419aa9] Dec 22 11:17:26 cc-popmap2p dovecot: dovecot: child 28088 (imap) killed with signal 6 (core dumped) Dec 22 13:16:49 cc-popmap3p dovecot: imap: user=ndunn, rip=x.x.x.x, pid=3908: fdatasync(/home2/ndunn/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e5021d994] - imap [0x419aa9] Dec 22 13:25:16 cc-popmap3p dovecot: dovecot: child 3228 (imap) killed with signal 6 (core dumped) I will note that we did not start seeing this crash until we took 'noac' out of our NFS mount options, as discussed on this list late last week. On the other hand, load on our NFS server (as measured in IOPS/sec) has dropped by a factor of 10. -Brad -Original Message- From: dovecot-bounces+brandond=uoregon@dovecot.org [mailto:dovecot- bounces+brandond=uoregon@dovecot.org] On Behalf Of David Halik Sent: Tuesday, December 22, 2009 7:48 AM To: dovecot@dovecot.org Subject: Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace) I'm seeing both of these dumps on multiple users now with 1.2.9, so I went ahead and did backtraces for them both. maildir_uidlist_records_array_delete panic: http://pastebin.com/f20614d8 ns_get_listed_prefix panic: http://pastebin.com/f1420194c On 12/21/2009 12:43 PM, David Halik wrote: Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) I also started receiving a good deal of these, but only from one user so far: Dec 21 12:16:42 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:19:57 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Let me know if you need full backtraces from the core
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I just double checked and we're seeing the same thing here, although we were never running with noac to begin with. Our poor NFS server would melt probably. ;) This is immediately before the crash: Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): fdatasync(/rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): /rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist: next_uid was lowered (1507 - 1506, hdr=1506) Dec 22 13:12:06 gehenna14.rutgers.edu dovecot: IMAP(user): /rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist: Duplicate file entry at line 3: 1249348137.M369064P26267V04240006I01ED7E09_0.gehenna5.rutgers.edu,S=15857:2,S (uid 1208 - 1508) On 12/22/2009 04:33 PM, Brandon Davidson wrote: We've started seeing the maildir_uidlist_records_array_delete assert crash as well. It always seems to be preceded by a 'stale NFS file handle' error from a the same user on a different connection. Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: fdatasync(/home11/apbao/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 10:12:20 oh-popmap5p dovecot: imap: user=apbao, rip=a.a.a.a, pid=2439: /home11/apbao/Maildir/dovecot-uidlist: next_uid was lowered (2642 - 2641, hdr=2641) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 11:17:26 cc-popmap2p dovecot: imap: user=apbao, rip=b.b.b.b, pid=28088: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3c4ea1d994] - imap [0x419aa9] Dec 22 11:17:26 cc-popmap2p dovecot: dovecot: child 28088 (imap) killed with signal 6 (core dumped) Dec 22 13:16:49 cc-popmap3p dovecot: imap: user=ndunn, rip=x.x.x.x, pid=3908: fdatasync(/home2/ndunn/Maildir/dovecot-uidlist) failed: Stale NFS file handle Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 22 13:25:16 cc-popmap3p dovecot: imap: user=ndunn, rip=y.y.y.y, pid=3228: Raw backtrace: imap [0x4d8986] - imap [0x4d97b0] - imap(i_fatal+0) [0x4d8c7a] - imap [0x44f2cc] - imap [0x44f814] - imap [0x4500a2] - imap(maildir_uidlist_refresh+0x9d) [0x450686] - imap [0x44bff1] - imap [0x44c0a8] - imap [0x44c178] - imap(maildir_storage_sync_init+0x7c) [0x44c6e6] - imap(mailbox_sync_init+0x44) [0x489922] - imap(imap_sync_init+0xab) [0x42e02b] - imap [0x42f107] - imap(cmd_sync_delayed+0x1c6) [0x42f663] - imap(client_handle_input+0x119) [0x4244d4] - imap(client_input+0xb4) [0x424594] - imap(io_loop_handler_run+0x17d) [0x4e5020] - imap(io_loop_run+0x3b) [0x4e4214] - imap(main+0xa6) [0x4300af] - /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e5021d994] - imap [0x419aa9] Dec 22 13:25:16 cc-popmap3p dovecot: dovecot: child 3228 (imap) killed with signal 6 (core dumped) I will note that we did not start seeing this crash until we took 'noac' out of our NFS mount options, as discussed on this list late last week. On the other hand, load on our NFS server (as measured in IOPS/sec) has dropped by a factor of 10. -Brad -Original Message- From: dovecot-bounces+brandond=uoregon@dovecot.org [mailto:dovecot- bounces+brandond=uoregon@dovecot.org] On Behalf Of David Halik Sent: Tuesday, December 22, 2009 7:48 AM To: dovecot@dovecot.org Subject: Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace) I'm seeing both of these dumps on multiple users now with 1.2.9, so I went ahead and did backtraces for them both. maildir_uidlist_records_array_delete panic: http://pastebin.com/f20614d8 ns_get_listed_prefix panic: http://pastebin.com/f1420194c On 12/21/2009 12:43 PM, David Halik wrote: Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On 22.12.2009, at 16.42, David Halik wrote: I just double checked and we're seeing the same thing here, although we were never running with noac to begin with. Our poor NFS server would melt probably. ;) This is immediately before the crash: Dec 22 13:09:20 gehenna14.rutgers.edu dovecot: IMAP(user): fdatasync(/rci/nqu/rci/u5/bruben/dovecot/.INBOX/dovecot-uidlist) failed: Stale NFS file handle The interesting this is that this function is called only when dovecot-uidlist.lock has been created, i.e. when uidlist is locked, meaning nothing should have deleted the dovecot-uidlist while it was being written to, so this error just shouldn't happen.. So apparently the dotlocking just isn't working properly for your NFS servers. See if dotlock_use_excl=no helps?
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
Just wanted to update you that I just upgraded all of our servers to 1.2.9 and I'm still seeing the array_delete panic: Dec 21 12:10:16 gehenna11.rutgers.edu dovecot: IMAP(user1): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) Dec 21 12:15:12 gehenna19.rutgers.edu dovecot: IMAP(user2): Panic: file maildir-uidlist.c: line 403 (maildir_uidlist_records_array_delete): assertion failed: (pos != NULL) I also started receiving a good deal of these, but only from one user so far: Dec 21 12:16:42 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:18:20 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 21 12:19:57 gehenna14.rutgers.edu dovecot: IMAP(user3): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Let me know if you need full backtraces from the core dump. On 12/17/2009 02:06 PM, David Halik wrote: On 12/17/2009 01:07 PM, Timo Sirainen wrote: On Thu, 2009-12-17 at 12:49 -0500, David Halik wrote: I applied those patches to my 1.2.8 installation before 1.2.9 was released and that immediately fixed the expunge crash, but the array_delete bug is still there. Do you also see the duplicate file entry before the crash? Yes, the duplicate file entry is always reported immediately before the crash, just as Ralf reported too. You can see it in this example pastebin I took from one of our users: http://pastebin.com/f29c55de5 maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot Are the index/control files on NFS? Are there multiple different servers accessing mail data? Correct. All index, control files, amd mail storage are located on NFS and there are multiple load balanced servers accessing the NFS data. We're currently running with: mmap_disable = yes dotlock_use_excl = yes fsync_disable = no mail_nfs_storage = yes mail_nfs_index = yes -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
I found this post from a couple of weeks ago: http://www.mail-archive.com/dovecot@dovecot.org/msg24127.html Any update on this? I'm experiencing the same issue. Out of a user population of 4000, I get about 20 of these dumps a day, so it's not major issue, but I thought I'd follow up. Here is an example: http://pastebin.com/f29c55de5 I can provide a more detailed debug log from teh core dump if necessary, but since the above email already had it I figured I'd wait. Note this is *not* the same issue as: - maildir: v1.2.7 and v1.2.8 caused assert-crashes in maildir_uidlist_records_drop_expunges() I applied those patches to my 1.2.8 installation before 1.2.9 was released and that immediately fixed the expunge crash, but the array_delete bug is still there. dovecot -n --- bash-3.2# /usr/sbin/dovecot -n # 1.2.8: /etc/dovecot.conf # OS: Linux 2.6.18-164.6.1.el5 x86_64 CentOS release 5.4 (Final) listen: * ssl_cert_file: /rci/local/certs/imapd-pop3d.pem ssl_key_file: /rci/local/certs/imapd-pop3d.pem disable_plaintext_auth: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_max_processes_count: 2048 max_mail_processes: 2048 first_valid_uid: 100 mail_location: maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_drop_priv_before_exec: yes mail_executable(default): /rci/local/etc/convert-courier-imap.sh mail_executable(imap): /rci/local/etc/convert-courier-imap.sh mail_executable(pop3): /rci/local/etc/convert-courier-pop.sh mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): UID%u-%v namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: passdb: driver: pam args: dovecot userdb: driver: passwd -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On Thu, 2009-12-17 at 12:49 -0500, David Halik wrote: I applied those patches to my 1.2.8 installation before 1.2.9 was released and that immediately fixed the expunge crash, but the array_delete bug is still there. Do you also see the duplicate file entry before the crash? maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot Are the index/control files on NFS? Are there multiple different servers accessing mail data? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot-1.2.8 imap crash (with backtrace)
On 12/17/2009 01:07 PM, Timo Sirainen wrote: On Thu, 2009-12-17 at 12:49 -0500, David Halik wrote: I applied those patches to my 1.2.8 installation before 1.2.9 was released and that immediately fixed the expunge crash, but the array_delete bug is still there. Do you also see the duplicate file entry before the crash? Yes, the duplicate file entry is always reported immediately before the crash, just as Ralf reported too. You can see it in this example pastebin I took from one of our users: http://pastebin.com/f29c55de5 maildir:~/Maildir:INDEX=/rci/nqu%h/dovecot:CONTROL=/rci/nqu%h/dovecot Are the index/control files on NFS? Are there multiple different servers accessing mail data? Correct. All index, control files, amd mail storage are located on NFS and there are multiple load balanced servers accessing the NFS data. We're currently running with: mmap_disable = yes dotlock_use_excl = yes fsync_disable = no mail_nfs_storage = yes mail_nfs_index = yes -- David Halik System Administrator OIT-CSS Rutgers University dha...@jla.rutgers.edu
Re: [Dovecot] dovecot with IMAP and POP3 mixed
On Sun, Mar 22, 2009 at 12:27:54PM +0100, Andreas Meyer wrote: Yes, this is what I get too and the default_folder_prefix is empty. I run dovecot with pop3, imap and squirrelmail with no problems. The major difference I see between your dovecot -n and mine other than the fact that you have 1.0.5 and I have 1.2.beta3 is that I have mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u In other words, I specify one file for the INBOX and another directory for everything else. I don't think this works with maildir though. -- Mark Sapiro mark at msapiro net The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Re: [Dovecot] dovecot with IMAP and POP3 mixed
Hello!
Mark Sapiro m...@msapiro.net schrieb:
On Sun, Mar 22, 2009 at 12:27:54PM +0100, Andreas Meyer wrote:
Yes, this is what I get too and the default_folder_prefix is empty.
I run dovecot with pop3, imap and squirrelmail with no problems.
The major difference I see between your dovecot -n and mine other than
the fact that you have 1.0.5 and I have 1.2.beta3 is that I have
Yes, this is a SuSE-rpm from openSuSE10.3
mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u
In other words, I specify one file for the INBOX and another directory
for everything else. I don't think this works with maildir though.
I have the beast running. I found out that I had to create a directory
where dovecot can write indexes and such things to.
# dovecot -n
# 1.0.5: /etc/dovecot/dovecot.conf
log_path: /var/log/dovecot1
protocols: imap imaps pop3
ssl_disable: yes
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/lib/dovecot/imap-login
login_executable(imap): /usr/lib/dovecot/imap-login
login_executable(pop3): /usr/lib/dovecot/pop3-login
mail_location:
mbox:/var/spool/vhosts/%d/dovecotprivate/%n:INBOX=/var/spool/vhosts/%d/%n
mail_debug: yes
mail_executable(default): /usr/lib/dovecot/imap
mail_executable(imap): /usr/lib/dovecot/imap
mail_executable(pop3): /usr/lib/dovecot/pop3
mail_plugin_dir(default): /usr/lib/dovecot/modules/imap
mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
auth default:
passdb:
driver: passwd-file
args: /etc/dovecot/passwd
userdb:
driver: passwd-file
args: /etc/dovecot/passwd
So in dovecotprivate directories for the indexes are stored for mbox-users.
This works, I had to set permissions to 777 for dovecotprivate so that dovecot
can write into it. I don't know if this is a security-risk.
The /etc/dovecot/passwd then looks like this:
# anup.de (maildir)
m...@anup.de:{PLAIN}passwd:5000:5000::/var/spool/vhosts/anup.de/mail::userdb_mail=maildir:~/
u...@anup.de:{PLAIN}passwd:5000:5000::/var/spool/vhosts/anup.de/user::userdb_mail=maildir:~/
# anup.de (mbox)
us...@anup.de:{PLAIN}passwd7:5000:5000
us...@anup.de:{PLAIN}passwd8:5000:5000
Works great and dovecot can handle both maildir and mbox for one domain.
And this solved also the problem with Squirrelmail. The setup is not fully
testet yet.
Thank you all!
--
Andreas Meyer
A man, a miss, a car -- a curve,
He kissed the miss and missed the curve -- Burma Shave (1948)
Mein öffentlicher GPG-Schlüssel unter:
http://gpg-keyserver.de/pks/lookup?search=anmeyerfingerprint=onop=index
Re: [Dovecot] dovecot with IMAP and POP3 mixed
Hello! Seth Mattinen se...@rollernet.us schrieb: Bill Cole wrote: There *should* be some way to make SquirrelMail stop trying to create its folders under INBOX, but I have no idea if there actually *is* one. Some IMAP servers only allow the creation of folders as children of INBOX, and as a result some (broken) IMAP clients only know how to create folders that way. You can accommodate such software in Dovecot by using namespaces. Run the squirrelmail configure program and change the default folder prefix to blank under folder defaults. The default folder prefix is empty. ~Seth -- Andreas Meyer A man, a miss, a car -- a curve, He kissed the miss and missed the curve -- Burma Shave (1948) Mein öffentlicher GPG-Schlüssel unter: http://gpg-keyserver.de/pks/lookup?search=anmeyerfingerprint=onop=index
Re: [Dovecot] dovecot with IMAP and POP3 mixed
Andreas Meyer wrote, On 3/21/09 11:16 AM:
Hello!
I tried to setup dovecot to work with IMAP and POP3 but when I connect
with Squirrelmail, I get an error saying CREATE INBOX.Sent
reason: Mailbox doesn't allow inferior mailboxes
That's for user7, right?
The cause of that error is SquirrelMail (using IMAP) is trying to create a
mailbox as a child of INBOX, but since user7 is defined as using mbox
format, that fails. If you use mbox storage, an IMAP folder can have either
messages or subfolders but never both, because when using mbox an IMAP
folder containing messages is a file, while an IMAP folder containing
subfolders is a directory. See http://wiki.dovecot.org/MailboxFormat/mbox
for more info.
There *should* be some way to make SquirrelMail stop trying to create its
folders under INBOX, but I have no idea if there actually *is* one. Some
IMAP servers only allow the creation of folders as children of INBOX, and as
a result some (broken) IMAP clients only know how to create folders that
way. You can accommodate such software in Dovecot by using namespaces.
I think you should start by reading http://wiki.dovecot.org/MailLocation and
http://wiki.dovecot.org/Namespaces to understand your options.
# dovecot --version
1.0.5
# dovecot -n
# 1.0.5: /etc/dovecot/dovecot.conf
log_path: /var/log/dovecot
protocols: imap imaps pop3
ssl_disable: yes
login_dir: /var/run/dovecot/login
login_executable(default): /usr/lib/dovecot/imap-login
login_executable(imap): /usr/lib/dovecot/imap-login
login_executable(pop3): /usr/lib/dovecot/pop3-login
mail_location: maildir:/var/spool/vhosts/%d/%n
mail_executable(default): /usr/lib/dovecot/imap
mail_executable(imap): /usr/lib/dovecot/imap
mail_executable(pop3): /usr/lib/dovecot/pop3
mail_plugin_dir(default): /usr/lib/dovecot/modules/imap
mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap
mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3
pop3_uidl_format(default):
pop3_uidl_format(imap):
pop3_uidl_format(pop3): %08Xu%08Xv
auth default:
passdb:
driver: passwd-file
args: /etc/dovecot/passwd
userdb:
driver: passwd-file
args: /etc/dovecot/passwd
and /etc/dovecot/passwd looks like this:
anme...@anup.de:{PLAIN}password:5000:5000::/var/spool/vhosts/anup.de/anmeyer::userdb_mail=maildir:~/
us...@anup.de:{PLAIN}password7:5000:5000::/var/spool/vhosts/anup.de/user7::userdb_mail=mbox:~/:INBOX=/var/spool/vhosts/anup.de/%u
The mbox of user7 already exists. Can someone help to get both variants working
so that dovecot can handle IMAP and POP3 accounts?
This is not about POP3 and IMAP, it is about storage formats. POP3 and IMAP
are both able to use either maildir or mbox storage. Users are not
restricted to one or the other access protocol, no matter what storage
format they use.
Re: [Dovecot] dovecot with IMAP and POP3 mixed
Bill Cole wrote: Andreas Meyer wrote, On 3/21/09 11:16 AM: Hello! I tried to setup dovecot to work with IMAP and POP3 but when I connect with Squirrelmail, I get an error saying CREATE INBOX.Sent reason: Mailbox doesn't allow inferior mailboxes That's for user7, right? The cause of that error is SquirrelMail (using IMAP) is trying to create a mailbox as a child of INBOX, but since user7 is defined as using mbox format, that fails. If you use mbox storage, an IMAP folder can have either messages or subfolders but never both, because when using mbox an IMAP folder containing messages is a file, while an IMAP folder containing subfolders is a directory. See http://wiki.dovecot.org/MailboxFormat/mbox for more info. There *should* be some way to make SquirrelMail stop trying to create its folders under INBOX, but I have no idea if there actually *is* one. Some IMAP servers only allow the creation of folders as children of INBOX, and as a result some (broken) IMAP clients only know how to create folders that way. You can accommodate such software in Dovecot by using namespaces. Run the squirrelmail configure program and change the default folder prefix to blank under folder defaults. ~Seth
Re: [Dovecot] dovecot with IMAP and POP3 mixed
On 3/21/09, Seth Mattinen wrote: Bill Cole wrote: Andreas Meyer wrote, On 3/21/09 11:16 AM: Hello! I tried to setup dovecot to work with IMAP and POP3 but when I connect with Squirrelmail, I get an error saying CREATE INBOX.Sent reason: Mailbox doesn't allow inferior mailboxes That's for user7, right? The cause of that error is SquirrelMail (using IMAP) is trying to create a mailbox as a child of INBOX, but since user7 is defined as using mbox format, that fails. If you use mbox storage, an IMAP folder can have either messages or subfolders but never both, because when using mbox an IMAP folder containing messages is a file, while an IMAP folder containing subfolders is a directory. See http://wiki.dovecot.org/MailboxFormat/mbox for more info. There *should* be some way to make SquirrelMail stop trying to create its folders under INBOX, but I have no idea if there actually *is* one. Some IMAP servers only allow the creation of folders as children of INBOX, and as a result some (broken) IMAP clients only know how to create folders that way. You can accommodate such software in Dovecot by using namespaces. Run the squirrelmail configure program and change the default folder prefix to blank under folder defaults. ~Seth When I set up a squirrellmail with Dovecot, on the configuration pade id option D. D. Set pre-defined settings for specific IMAP servers I write in 'dovecot', and it sets a number of setting for me, for example: Please select your IMAP server: bincimap= Binc IMAP server courier = Courier IMAP server cyrus = Cyrus IMAP server dovecot = Dovecot Secure IMAP server exchange= Microsoft Exchange IMAP server hmailserver = hMailServer macosx = Mac OS X Mailserver mercury32 = Mercury/32 uw = University of Washington's IMAP server quit= Do not change anything Command dovecot imap_server_type = dovecot default_folder_prefix = none trash_folder = Trash sent_folder = Sent draft_folder = Drafts show_prefix_option = false default_sub_of_inbox = false show_contain_subfolders_option = false optional_delimiter = detect delete_folder = false -- Gary V
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On Wed, Feb 11, 2009 at 07:22:50PM +0200, Harry Lachanas wrote: Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? Isn't that (for users (as opposed to admins) to create subfolders in a public namespacejust impossible with 1.1.x) ? -- Thomas Hummel | Institut Pasteur hum...@pasteur.fr | Pôle informatique - systèmes et réseau
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On Wed, 2009-02-11 at 19:22 +0200, Harry Lachanas wrote: Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? .. namespace: type: public separator: / prefix: Public/ location: maildir:/home/Public:INBOX=~/Maildir:INDEX=~/Maildir/p-idx:CONTROL=~/Maildir/p-ctrl You don't need to specify INBOX here, since this namespace has no INBOX. passdb: driver: pam userdb: driver: passwd So you're using multiple UIDs? How about just removing filesystem write permissions from /home/Public? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
Thomas Hummel wrote: On Wed, Feb 11, 2009 at 07:22:50PM +0200, Harry Lachanas wrote: Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? Isn't that (for users (as opposed to admins) to create subfolders in a public namespacejust impossible with 1.1.x) ? You got me ! :-( puzzled ? er.! Now I am not so sure what I really meant when I asked the question! :-) :-) Not to mention yours !!! Cheers Harry
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
Kiitos Timo ,,, On Wed, 2009-02-11 at 19:22 +0200, Harry Lachanas wrote: Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? .. namespace: type: public separator: / prefix: Public/ location: maildir:/home/Public:INBOX=~/Maildir:INDEX=~/Maildir/p-idx:CONTROL=~/Maildir/p-ctrl You don't need to specify INBOX here, since this namespace has no INBOX. passdb: driver: pam userdb: driver: passwd So you're using multiple UIDs? How about just removing filesystem write permissions from /home/Public? But this would disable users from dumping mails into the folders right ??? Thanks Harry.
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On Wed, 2009-02-11 at 20:12 +0200, Harry Lachanas wrote: So you're using multiple UIDs? How about just removing filesystem write permissions from /home/Public? But this would disable users from dumping mails into the folders right ??? No, for example if you had a folder called box it would exist in /home/Public/.box/ directory and that would need to have write permissions. Dovecot doesn't need to write anything directly under /home/Public/. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On 2/11/2009, Harry Lachanas (grha...@freemail.gr) wrote: Here is my conf Please don't snip critical info from dovecot -n output... There hsould be a version line and a line with info about your system. -- Best regards, Charles
Re: [Dovecot] Dovecot 1.1.4 imap core
On Oct 7, 2008, at 5:40 PM, Anton Zakatov wrote: Core was generated by `/usr/libexec/dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x003ab2279f8c in strcasecmp () from /lib64/libc.so.6 (gdb) backtrace #0 0x003ab2279f8c in strcasecmp () from /lib64/libc.so.6 #1 0x0041c30e in command_unregister (name=0x4986aa LOGOUT) at commands.c:80 Does this happen every time when logging out? What plugins do you have loaded? PGP.sig Description: This is a digitally signed message part
Re: [Dovecot] dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor
On Thu, 2008-04-17 at 15:47 +0300, Mart Pirita wrote: Hello. Since I upgraded few months ago from version 1.0 to 1.1 (right now using v1.1.rc4) in logs for some users only (but in different servers) I noticed errors: dovecot: Fatal: IMAP(user2): write(event_pipe) failed: Bad file descriptor dovecot: Fatal: IMAP(user3): write(event_pipe) failed: Bad file descriptor Does this help or change the error message at least? http://hg.dovecot.org/dovecot-1.1/rev/63cd8ec2007a I already tried to delete delete cache and index files. This problem has something to do with dnotify support, not with indexes or any other files. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.0.10 - IMAP - Nokia N95 ?
On Tue, 26 Feb 2008, Patrick wrote: I was wondering if anyone has IMAP working between Dovecot 1.0.10 and a Nokia N95 (8GB version with firmware 15.x.x.x)? I've been trying to make it work using a default Dovecot config but the N95 just hangs when updating the folder list which has a bunch of nested folders. Can you log the IMAP conversation with e.g. Dovecot's rawlog: http://wiki.dovecot.org/MainConfig?highlight=rawlog ? -- Asheesh. -- I never loved another person the way I loved myself. -- Mae West
Re: [Dovecot] Dovecot 1.0.10 - IMAP - Nokia N95 ?
On Tue, 2008-02-26 at 16:49 +0200, Timo Sirainen wrote: On Tue, 2008-02-26 at 14:15 +0100, Patrick wrote: In wireshark all I see are a bunch of TCP transmissions over and over from the Dovecot server to the N95 and the N95 just sits there. What commands/replies? Tomorrow I'll make make a trace with wireshark and put it up for download and report back with the location. Thanks for taking an interest. Regards, Patrick
Re: [Dovecot] Dovecot 1.0.10 - IMAP - Nokia N95 ?
On Tue, 2008-02-26 at 11:21 -0800, Asheesh Laroia wrote: On Tue, 26 Feb 2008, Patrick wrote: I was wondering if anyone has IMAP working between Dovecot 1.0.10 and a Nokia N95 (8GB version with firmware 15.x.x.x)? I've been trying to make it work using a default Dovecot config but the N95 just hangs when updating the folder list which has a bunch of nested folders. Can you log the IMAP conversation with e.g. Dovecot's rawlog: http://wiki.dovecot.org/MainConfig?highlight=rawlog ? Will do that. In addition to Timo's request I'll generate this log and make it available together with the wireshark trace. Thanks for the suggestion. Regards, Patrick
Re: [Dovecot] Dovecot push imap/imap notify support?
Charles Marcus wrote: Hmm, seems yes. Osx Leopard built in Mail application have now the IDLE check box. Does it mean, that now need to use the classic check for new mail after xx minute at all? Btw, seems in Thunderbird this imap push works well. Isn't one downside to IDLE that only the current selected folder works? Ie, if you are in a folder other than Inbox, you wouldn't get IDLE notifications of anything in the Inbox until you selected that folder? That's why imap push is usually tied to NOTFY[1], QRESYNC[2], and CONDSTORE[3] support in addition to IDLE. Sadly 2 of them are just in draft status so there's not much client or server support yet. [1]http://tools.ietf.org/html/draft-gulbrandsen-imap-notify-07 [2]http://tools.ietf.org/html/draft-ietf-lemonade-reconnect-client-06 [3]http://www.tools.ietf.org/html/rfc4551 -- Angel Marin http://anmar.eu.org/
Re: [Dovecot] Dovecot push imap/imap notify support?
At 2:26 PM -0400 10/31/07, Charles Marcus wrote: Hmm, seems yes. Osx Leopard built in Mail application have now the IDLE check box. Does it mean, that now need to use the classic check for new mail after xx minute at all? Btw, seems in Thunderbird this imap push works well. Isn't one downside to IDLE that only the current selected folder works? yes Ie, if you are in a folder other than Inbox, you wouldn't get IDLE A common approach for clients using IDLE as a push alternative is to open multiple connections, running an IDLE in each mailbox. For example, I currently have ChatterEmail running on my Treo with 5 open connections to my Dovecot server, one for each of 5 folders. -- Bill Cole [EMAIL PROTECTED]
Re: [Dovecot] Dovecot push imap/imap notify support?
Mart Pirita [EMAIL PROTECTED] wrote: Tried search, no luck, does the Dovecot include push imap/imap notify support? If you're looking for something iPhone-compatible, then no. Theirs is a proprietary system which from what I've read, seems to use SMS in combination with IMAP. Wacky. (If you aren't talking about iPhone compatibility, I'm less knowledgeable, but dovecot does support IDLE-style imap push style notification.) Alan Ferrency
Re: [Dovecot] Dovecot push imap/imap notify support?
Tere. If you're looking for something iPhone-compatible, then no. Theirs is a proprietary system which from what I've read, seems to use SMS in combination with IMAP. Wacky. Yep, thats wacky. (If you aren't talking about iPhone compatibility, I'm less knowledgeable, but dovecot does support IDLE-style imap push style notification.) Hmm, seems yes. Osx Leopard built in Mail application have now the IDLE check box. Does it mean, that now need to use the classic check for new mail after xx minute at all? Btw, seems in Thunderbird this imap push works well. -- Mart
Re: [Dovecot] Dovecot push imap/imap notify support?
Hmm, seems yes. Osx Leopard built in Mail application have now the IDLE check box. Does it mean, that now need to use the classic check for new mail after xx minute at all? Btw, seems in Thunderbird this imap push works well. Isn't one downside to IDLE that only the current selected folder works? Ie, if you are in a folder other than Inbox, you wouldn't get IDLE notifications of anything in the Inbox until you selected that folder? -- Best regards, Charles
Re: [Dovecot] Dovecot 1.1alpha2 - (imap) killed with signal 10
On Wed, 2007-08-08 at 01:57 +0200, Luca Corti wrote: Program terminated with signal 10, Bus error. #0 mailbox_list_index_sync_write_dir (ctx=0xf75e8, sync_dir=0xf7650, Thanks, I'll try to get this fixed soon. You can anyway prevent this crash by setting mailbox_list_index_disable=yes signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dovecot for imap
John Peacock spake the following on 4/30/2007 10:30 AM: [EMAIL PROTECTED] wrote: Users have inbox, trash and sent folder, but none of the other folders that they have created in /home/Username. Are the folders /invisible/ or not /subscribed/? Have one of the users go into the Horde folder subscribe page and see if their personal folders are displayed there. With other clients, e.g. Thunderbird, it is necessary to force the client to resubscribe to the folders when changing things. HTH John Part of the migration docs does mention copying/renaming .mailboxlist to .subscriptions and editing to suit. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't
Re: [Dovecot] dovecot for imap
If you mean the folders (as opposed to the inbox) of a user, this is the way I understand the interaction between the subscription list and folder displays: 1) The purpose of subscription lists is to restrict the folders presented in the folder list. 2) I think that the default is for IMAP to look for use and use for a subscription list. There is, on some clients, a check box to disable subscription lists AND SHOW ALL FOLDERS, but this is, by default, set to enable, so that the IMAP client/server interaction is to look and use a subscription list. This disablement configuration check box is buried 3 levels down and not easy to find. 3) Since the subscription lists under UWIMAP have a different name (unless you've copied the content over into the name that DC is looking for), Dovecot does not find it and does not display folders. 4) After banging around awhile, the users start laboriously checking all the subscription boxes in order to see their folders. In using the subscription list to SEE folders, they are using them exactly backwards. What they should be doing is (in a box hidden in advanced config) turning off subscription lists...but that's hard to find. 5) Everybody is aggravated Since sometimes the folders displayed can weirdly not match what is in the old subscription list OR there can be multiple subscripiton list scattered around the user's homedir, a co-worker here had a bright idea: when migrating from UWIMAP, don't copy the existing subscription list to the .subscriptions file that DC wants, instead do this: ls -1 ~/mail ~/mail/.subscriptions. After migration, all users should see all folders...and the few that actually use subscription lists to restrict what they see can be dealt with easily. That's how I see it...but maybe I'm getting it wrong... [EMAIL PROTECTED] wrote: Quoting Charles Marcus [EMAIL PROTECTED]: [EMAIL PROTECTED] wrote: I have been using uw-imap on my mailserver. I tried briefly to use dovecot with the default config. It seem to work faster, but users imap folders (user accounts are in openldap) disappeared. Is there a sample config somewhere I can look at to get some idea how to configure dovecot so all the imap folders users created will appear when I make the switch? Most of my users login via Horde. Server is an FC6 box, dovecot installed via yum install. Google is your friend: http://wiki.dovecot.org/MissingMailboxes -- Best regards, Charles Sort of missed that when looking at the wiki. Sorry, ddh
