index problems after update
Hello List,
i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/myuser emails are delivered again if i delete index-files from .imap folder. So index is recreated and everything works again. I cant reproduce this problem, but every 2 days i have one user who is reporting this problem.
Second problem is similiar. I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. After that i installed an self packaged dovecot 2.2.36.1 Now here is same problem, dovecot is not showing new mails, but the difference is we have a Raw backtrace in Log just as expected:
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1ee2) [0x7f78b3b2cee2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1fda) [0x7f78b3b2cfda] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78b3abb8a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x78a) [0x7f78b3e7940a] -> /usr/lib/dovecot/libdovecot.so.0(+0x83592) [0x7f78b3b0e592] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x74) [0x7f78b3b38814] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f78b3b392fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x4a) [0x7f78b3e7a2ea] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x4a) [0x7f78b3dfd8da] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x24a) [0x7f78b3ebb57a] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76d81c] -> dovecot/imap m038422 ip.ip.ip.ip FETCH [0x5581ac76ba54] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76cd69] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75e1bb] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76a09c] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768612] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac7686ac] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768a6d] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768fbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f78b3b43482] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f78b3b44b9e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f78b3b43516] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78b3b436c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78b3ac6aa3] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b159] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f78b36bbb97] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b2fa] Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
Over all dovecot and OS versions we use same old-fashioned setup. Mails are delivered by procmail to classic mbox file. This is output of doveconf -n
# 2.2.36.1 (5d621cf65): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.18.0-14-generic x86_64 Ubuntu 18.04.1 LTS # Hostname: myhostname auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@üÜöÖäÄ auth_worker_max_count = 60 disable_plaintext_auth = no imap_capability = +XLIST lock_method = flock login_greeting = mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_cache_min_mail_count = 30 mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_max_userip_connections = 30 mbox_read_locks = dotlock mbox_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Archiv { auto = no special_use = } mailbox Drafts { auto = no special_use = } mailbox Junk { auto = no special_use = } mailbox Sent { auto = no special_use = } mailbox Trash { auto = no special_use = } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth-worker { idle_kill = 1 mins } service auth { idle_kill = 1 mins unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { executable = /usr/lib/dovecot/imap-login process_min_avail = 4 service_count = 0 user = dovecot } service imap { process_limit = 1024 } service pop3-login { executable = /usr/lib/dovecot/pop3-login process_min_avail = 4 service_count = 0 user = dovecot } service pop3 { executable = /usr/lib/dovecot/pop3 process_limit = 1024 } shutdown_clients = no ssl_ca = </path/cert.pem ssl_cert = </path/cert.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = mail_log notify ssl = yes } protocol pop3 { pop3_client_workarounds = oe-ns-eoh outlook-no-nuls pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv ssl = yes }
Whats going wrong here? Main problem is first one. dovecot stops showing new mail during service without telling a reason. reason looks like a broken index file. What to do here? Please tell me your opinion.
Thanks, Hajo
Hello, Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot:
Hello List,
i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/myuser emails are delivered again if i delete index-files from .imap folder. So index is recreated and everything works again. I cant reproduce this problem, but every 2 days i have one user who is reporting this problem.
Second problem is similiar. I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. After that i installed an self packaged dovecot 2.2.36.1 Now here is same problem, dovecot is not showing new mails, but the difference is we have a Raw backtrace in Log just as expected:
i think this crash is a special problem of dovecot 2.2.36.1. if i downgrade to 2.2.33.2 all is working well, upgrading again to 2.2.36.1 leeds to same crash.
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1ee2) [0x7f78b3b2cee2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1fda) [0x7f78b3b2cfda] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78b3abb8a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x78a) [0x7f78b3e7940a] -> /usr/lib/dovecot/libdovecot.so.0(+0x83592) [0x7f78b3b0e592] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x74) [0x7f78b3b38814] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f78b3b392fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x4a) [0x7f78b3e7a2ea] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x4a) [0x7f78b3dfd8da] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x24a) [0x7f78b3ebb57a] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76d81c] -> dovecot/imap m038422 ip.ip.ip.ip FETCH [0x5581ac76ba54] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76cd69] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75e1bb] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76a09c] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768612] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac7686ac] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768a6d] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768fbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f78b3b43482] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f78b3b44b9e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f78b3b43516] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78b3b436c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78b3ac6aa3] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b159] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f78b36bbb97] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b2fa] Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
Over all dovecot and OS versions we use same old-fashioned setup. Mails are delivered by procmail to classic mbox file. This is output of doveconf -n
# 2.2.36.1 (5d621cf65): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.18.0-14-generic x86_64 Ubuntu 18.04.1 LTS # Hostname: myhostname auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@üÜöÖäÄ auth_worker_max_count = 60 disable_plaintext_auth = no imap_capability = +XLIST lock_method = flock login_greeting = mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_cache_min_mail_count = 30 mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_max_userip_connections = 30 mbox_read_locks = dotlock mbox_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Archiv { auto = no special_use = } mailbox Drafts { auto = no special_use = } mailbox Junk { auto = no special_use = } mailbox Sent { auto = no special_use = } mailbox Trash { auto = no special_use = } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth-worker { idle_kill = 1 mins } service auth { idle_kill = 1 mins unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { executable = /usr/lib/dovecot/imap-login process_min_avail = 4 service_count = 0 user = dovecot } service imap { process_limit = 1024 } service pop3-login { executable = /usr/lib/dovecot/pop3-login process_min_avail = 4 service_count = 0 user = dovecot } service pop3 { executable = /usr/lib/dovecot/pop3 process_limit = 1024 } shutdown_clients = no ssl_ca = </path/cert.pem ssl_cert = </path/cert.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = mail_log notify ssl = yes } protocol pop3 { pop3_client_workarounds = oe-ns-eoh outlook-no-nuls pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv ssl = yes }
Whats going wrong here? Main problem is first one. dovecot stops showing new mail during service without telling a reason. reason looks like a broken index file. What to do here? Please tell me your opinion.
Thanks, Hajo
Thanks, Hajo
Hello,
Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot:
Hello, Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot:
Hello List,
i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/myuser emails are delivered again if i delete index-files from .imap folder. So index is recreated and everything works again. I cant reproduce this problem, but every 2 days i have one user who is reporting this problem.
Iam surprised that no one has an opinion in this case. Nobody else noticed this problem? Yesterday i had a customer who was affected twice. First time we saw an errormessage, which leads to an index problem:
Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: Corrupted record in index cache file /home/popuser/username/mail/.imap/INBOX/dovecot.index.cache: UID 26876: Broken physical size in mailbox INBOX: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) (FETCH BODY[] for mailbox INBOX UID 26876)
At this point no new incoming mail is delivered by imapd. We deleted index files, dovecot reacreated them and all was working again. a day later same user was affected again. But like all other cases before there is no error or unusual logline. i turned mail_debug on, but no further hint. There are definitely new Mails in /var/mail/username but dovecot still shows old state from cache. I deleted index-files again and imap-client showed a lot of new unread mails. In log i can see that people are active in imap-clients and managing mails. If a new mail is coming in this period it seems to harm index-files some times. We never noticed same behaviour with long used dovecot 2.2.22
It seems that 2.2.33.2 which is bundled with Ubuntu18.04 LTS has a special problem.
Please help. What is your advice?
Second problem is similiar. I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. After that i installed an self packaged dovecot 2.2.36.1 Now here is same problem, dovecot is not showing new mails, but the difference is we have a Raw backtrace in Log just as expected:
i think this crash is a special problem of dovecot 2.2.36.1. if i downgrade to 2.2.33.2 all is working well, upgrading again to 2.2.36.1 leeds to same crash.
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1ee2) [0x7f78b3b2cee2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1fda) [0x7f78b3b2cfda] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78b3abb8a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x78a) [0x7f78b3e7940a] -> /usr/lib/dovecot/libdovecot.so.0(+0x83592) [0x7f78b3b0e592] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x74) [0x7f78b3b38814] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f78b3b392fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x4a) [0x7f78b3e7a2ea] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x4a) [0x7f78b3dfd8da] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x24a) [0x7f78b3ebb57a] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76d81c] -> dovecot/imap m038422 ip.ip.ip.ip FETCH [0x5581ac76ba54] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76cd69] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75e1bb] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76a09c] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768612] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac7686ac] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768a6d] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768fbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f78b3b43482] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f78b3b44b9e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f78b3b43516] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78b3b436c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78b3ac6aa3] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b159] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f78b36bbb97] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b2fa] Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
Over all dovecot and OS versions we use same old-fashioned setup. Mails are delivered by procmail to classic mbox file. This is output of doveconf -n
# 2.2.36.1 (5d621cf65): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.18.0-14-generic x86_64 Ubuntu 18.04.1 LTS # Hostname: myhostname auth_mechanisms = plain login auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@üÜöÖäÄ auth_worker_max_count = 60 disable_plaintext_auth = no imap_capability = +XLIST lock_method = flock login_greeting = mailserver ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_cache_min_mail_count = 30 mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_max_userip_connections = 30 mbox_read_locks = dotlock mbox_very_dirty_syncs = yes namespace inbox { inbox = yes location = mailbox Archiv { auto = no special_use = } mailbox Drafts { auto = no special_use = } mailbox Junk { auto = no special_use = } mailbox Sent { auto = no special_use = } mailbox Trash { auto = no special_use = } prefix = } passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth-worker { idle_kill = 1 mins } service auth { idle_kill = 1 mins unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { executable = /usr/lib/dovecot/imap-login process_min_avail = 4 service_count = 0 user = dovecot } service imap { process_limit = 1024 } service pop3-login { executable = /usr/lib/dovecot/pop3-login process_min_avail = 4 service_count = 0 user = dovecot } service pop3 { executable = /usr/lib/dovecot/pop3 process_limit = 1024 } shutdown_clients = no ssl_ca = </path/cert.pem ssl_cert = </path/cert.pem ssl_cipher_list = ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-DSS-AES128-GCM-SHA256:kEDH+AESGCM:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES256-SHA:ECDHE-ECDSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-DSS-AES128-SHA256:DHE-RSA-AES256-SHA256:DHE-DSS-AES256-SHA:DHE-RSA-AES256-SHA:AES128-GCM-SHA256:AES256-GCM-SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:AES:CAMELLIA:!DES-CBC3-SHA:!aNULL:!eNULL:!EXPORT:!DES:!RC4:!MD5:!PSK:!aECDH:!EDH-DSS-DES-CBC3-SHA:!EDH-RSA-DES-CBC3-SHA:!KRB5-DES-CBC3-SHA ssl_dh_parameters_length = 2048 ssl_key = # hidden, use -P to show it ssl_prefer_server_ciphers = yes userdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = mail_log notify ssl = yes } protocol pop3 { pop3_client_workarounds = oe-ns-eoh outlook-no-nuls pop3_no_flag_updates = no pop3_uidl_format = %08Xu%08Xv ssl = yes }
Whats going wrong here? Main problem is first one. dovecot stops showing new mail during service without telling a reason. reason looks like a broken index file. What to do here? Please tell me your opinion.
Thanks, Hajo
Thanks, Hajo
Thanks, Hajo
El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribió:
Hello,
Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot:
Hello, Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot:
Hello List,
i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/myuser emails are delivered again if i delete index-files from .imap folder. So index is recreated and everything works again. I cant reproduce this problem, but every 2 days i have one user who is reporting this problem.
Iam surprised that no one has an opinion in this case. Nobody else noticed this problem? Yesterday i had a customer who was affected twice. First time we saw an errormessage, which leads to an index problem:
Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: Corrupted record in index cache file /home/popuser/username/mail/.imap/INBOX/dovecot.index.cache: UID 26876: Broken physical size in mailbox INBOX: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) (FETCH BODY[] for mailbox INBOX UID 26876)
At this point no new incoming mail is delivered by imapd. We deleted index files, dovecot reacreated them and all was working again. a day later same user was affected again. But like all other cases before there is no error or unusual logline. i turned mail_debug on, but no further hint. There are definitely new Mails in /var/mail/username but dovecot still shows old state from cache. I deleted index-files again and imap-client showed a lot of new unread mails. In log i can see that people are active in imap-clients and managing mails. If a new mail is coming in this period it seems to harm index-files some times. We never noticed same behaviour with long used dovecot 2.2.22
It seems that 2.2.33.2 which is bundled with Ubuntu18.04 LTS has a special problem.
Please help. What is your advice?
Second problem is similiar. I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. After that i installed an self packaged dovecot 2.2.36.1 Now here is same problem, dovecot is not showing new mails, but the difference is we have a Raw backtrace in Log just as expected:
i think this crash is a special problem of dovecot 2.2.36.1. if i downgrade to 2.2.33.2 all is working well, upgrading again to 2.2.36.1 leeds to same crash.
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1ee2) [0x7f78b3b2cee2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1fda) [0x7f78b3b2cfda] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78b3abb8a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x78a) [0x7f78b3e7940a] -> /usr/lib/dovecot/libdovecot.so.0(+0x83592) [0x7f78b3b0e592] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x74) [0x7f78b3b38814] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f78b3b392fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x4a) [0x7f78b3e7a2ea] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x4a) [0x7f78b3dfd8da] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x24a) [0x7f78b3ebb57a] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76d81c] -> dovecot/imap m038422 ip.ip.ip.ip FETCH [0x5581ac76ba54] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76cd69] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75e1bb] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76a09c] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768612] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac7686ac] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768a6d] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768fbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f78b3b43482] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f78b3b44b9e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f78b3b43516] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78b3b436c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78b3ac6aa3] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b159] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f78b36bbb97] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b2fa] Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
Thanks, Hajo
Thanks, Hajo
Hi,
A few days ago I posted a similar issue. My environment has RHEL6 and 7 servers. When I last updated the servers RHEL6 servers mantained 2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used for sympa) processed a message for a user, its indexes were corrupted, and the user could't access his inbox through webmail, so I had to delete dovecot.* files from the user mail path to get it working again. This is the error shown at the dovecot log:
Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3713268b8a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3713268bf6] -> /usr/lib64/dovecot/libdovecot.so.0() [0x37132224aa] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x7fd) [0x3713aca43d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xec) [0x3713acacac] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x234) [0x3713acbae4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x83) [0x3713abcce3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_refresh+0xe) [0x3713ab793e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_sync_header_refresh+0x10) [0x3713a4e1e0] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4e330] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4f3d4] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4f7b3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xd9) [0x3713a4fa59] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x3713a7d731] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x3713a7e7b7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x62) [0x3713aa8fc2] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xc3ec) [0x7fd272dfe3ec] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x5c) [0x3713a7f4fc] -> dovecot/imap(imap_status_get+0x7a) [0x41dbea] -> dovecot/imap(cmd_status+0x179) [0x413059] -> dovecot/imap(command_exec+0x3d) [0x4170bd] -> dovecot/imap() [0x416180] -> dovecot/imap() [0x41627a] -> dovecot/imap(client_handle_input+0x11d) [0x4164ed] -> dovecot/imap(client_input+0x6f) [0x41685f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3713278a56] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x3713279b27] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x37132789c8] Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Fatal: master: service(imap): child 2057 killed with signal 6 (core dumped)
My solution was to downgrade dovecot and dovecot-pigeonhole back to 2.2.10-8.el7.x86_64 Regards
--
*Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco <3D"http://www.uam.es/">
Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.
Hello,
Am 15.02.2019 um 10:03 schrieb Gonzalo Palacios Goicolea via dovecot:
El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribió:
Hello,
Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot:
Hello, Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot:
Hello List,
i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/myuser emails are delivered again if i delete index-files from .imap folder. So index is recreated and everything works again. I cant reproduce this problem, but every 2 days i have one user who is reporting this problem.
Iam surprised that no one has an opinion in this case. Nobody else noticed this problem? Yesterday i had a customer who was affected twice. First time we saw an errormessage, which leads to an index problem:
Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: Corrupted record in index cache file /home/popuser/username/mail/.imap/INBOX/dovecot.index.cache: UID 26876: Broken physical size in mailbox INBOX: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) (FETCH BODY[] for mailbox INBOX UID 26876)
At this point no new incoming mail is delivered by imapd. We deleted index files, dovecot reacreated them and all was working again. a day later same user was affected again. But like all other cases before there is no error or unusual logline. i turned mail_debug on, but no further hint. There are definitely new Mails in /var/mail/username but dovecot still shows old state from cache. I deleted index-files again and imap-client showed a lot of new unread mails. In log i can see that people are active in imap-clients and managing mails. If a new mail is coming in this period it seems to harm index-files some times. We never noticed same behaviour with long used dovecot 2.2.22
It seems that 2.2.33.2 which is bundled with Ubuntu18.04 LTS has a special problem.
Please help. What is your advice?
Second problem is similiar. I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. After that i installed an self packaged dovecot 2.2.36.1 Now here is same problem, dovecot is not showing new mails, but the difference is we have a Raw backtrace in Log just as expected:
i think this crash is a special problem of dovecot 2.2.36.1. if i downgrade to 2.2.33.2 all is working well, upgrading again to 2.2.36.1 leeds to same crash.
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1ee2) [0x7f78b3b2cee2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1fda) [0x7f78b3b2cfda] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78b3abb8a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x78a) [0x7f78b3e7940a] -> /usr/lib/dovecot/libdovecot.so.0(+0x83592) [0x7f78b3b0e592] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x74) [0x7f78b3b38814] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f78b3b392fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x4a) [0x7f78b3e7a2ea] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x4a) [0x7f78b3dfd8da] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x24a) [0x7f78b3ebb57a] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76d81c] -> dovecot/imap m038422 ip.ip.ip.ip FETCH [0x5581ac76ba54] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76cd69] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75e1bb] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76a09c] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768612] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac7686ac] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768a6d] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768fbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f78b3b43482] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f78b3b44b9e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f78b3b43516] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78b3b436c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78b3ac6aa3] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b159] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f78b36bbb97] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b2fa] Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
Thanks, Hajo
Thanks, Hajo
Hi,
A few days ago I posted a similar issue. My environment has RHEL6 and 7 servers. When I last updated the servers RHEL6 servers mantained 2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used for sympa) processed a message for a user, its indexes were corrupted, and the user could't access his inbox through webmail, so I had to delete dovecot.* files from the user mail path to get it working again. This is the error shown at the dovecot log:
Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3713268b8a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3713268bf6] -> /usr/lib64/dovecot/libdovecot.so.0() [0x37132224aa] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x7fd) [0x3713aca43d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xec) [0x3713acacac] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x234) [0x3713acbae4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x83) [0x3713abcce3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_refresh+0xe) [0x3713ab793e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_sync_header_refresh+0x10) [0x3713a4e1e0] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4e330] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4f3d4] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4f7b3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xd9) [0x3713a4fa59] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x3713a7d731] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x3713a7e7b7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x62) [0x3713aa8fc2] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xc3ec) [0x7fd272dfe3ec] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x5c) [0x3713a7f4fc] -> dovecot/imap(imap_status_get+0x7a) [0x41dbea] -> dovecot/imap(cmd_status+0x179) [0x413059] -> dovecot/imap(command_exec+0x3d) [0x4170bd] -> dovecot/imap() [0x416180] -> dovecot/imap() [0x41627a] -> dovecot/imap(client_handle_input+0x11d) [0x4164ed] -> dovecot/imap(client_input+0x6f) [0x41685f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3713278a56] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x3713279b27] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x37132789c8] Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Fatal: master: service(imap): child 2057 killed with signal 6 (core dumped)
Thanks for your reply, so iam not the only one. I think downgrading is not an option for me. Ubuntu 18.04 comes with openssl 1.1.0 and it seems that older versions like 2.2.22 not compile successful. Best way for me would be a patch from Ubuntu-side, but without any errormessage or something its wasted time to file a bugreport. Though Ubuntu 18.04 should run for next 5 years.
My solution was to downgrade dovecot and dovecot-pigeonhole back to 2.2.10-8.el7.x86_64 Regards
--
*Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco <3D"http://www.uam.es/">
Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.
Thanks, Hajo
On February 15, 2019 at 3:35 AM Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Thanks for your reply, so iam not the only one. I think downgrading is not an option for me. Ubuntu 18.04 comes with openssl 1.1.0 and it seems that older versions like 2.2.22 not compile successful. Best way for me would be a patch from Ubuntu-side, but without any errormessage or something its wasted time to file a bugreport. Though Ubuntu 18.04 should run for next 5 years.
michael
Hello,
thanks for your reply.
On February 15, 2019 at 3:35 AM Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Thanks for your reply, so iam not the only one. I think downgrading is not an option for me. Ubuntu 18.04 comes with openssl 1.1.0 and it seems that older versions like 2.2.22 not compile successful. Best way for me would be a patch from Ubuntu-side, but without any errormessage or something its wasted time to file a bugreport. Though Ubuntu 18.04 should run for next 5 years. https://repo.dovecot.org/
michael Without statement of dovecot developers i dont like upgrading. I want to explain: One should think that latest versions in 2.2 tree are almost bugfree and stable. But this one is ugly. dovecot crashes its index without noticing by itself and hiding new mails. To be particular dovecot is not usable in a classic mbox setup with this versions. Obviously this problem is unknown to developers, else i expected a short answer. So it is still thinkable that this problem still exists in 2.3 versions. At this point it's frustrating and disappointing that this case is ignored by developers. My first mail was 11 days ago. Not every user is an early adopter with 2.3 versions/mdbox etc. the bigger the company the slower upgrades are deployed. We have several hundreds of affected servers with 2.2.33.2, we have several thousands servers with older versions without this problem, which should get updated next weeks/months. For upgrading i need a version where this problem is fixed (we can
Am 15.02.2019 um 17:34 schrieb Michael Slusarz via dovecot: package by ourselfes if needed). we dont need newest features, just a stable classic imapd. we cant use our customers as dummies and test different versions to see if a bug is fixed or may be other issues appear. I hope there is an understanding for our situation.
Thanks, Hajo
Hello,
it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves.
Am 15.02.2019 um 11:35 schrieb Hajo Locke via dovecot:
Hello,
Am 15.02.2019 um 10:03 schrieb Gonzalo Palacios Goicolea via dovecot:
El 15/02/2019 a las 8:47, Hajo Locke via dovecot escribió:
Hello,
Am 11.02.2019 um 09:12 schrieb Hajo Locke via dovecot:
Hello, Am 08.02.2019 um 09:25 schrieb Hajo Locke via dovecot:
Hello List,
i have a problem with index-files which is separated in 2 subproblems. May be these problems are connected. Currently we use Ubuntu 18.04 LTS which is bundled with dovecot 2.2.33.2 These servers are fresh installed machines and users are added to the system after, there was no upgrade. Sometimes it happens, that dovecot stops showing new mail. There is no error in log, dovecot just seems to do his normal operations but is not delivering new emails from /var/mail/myuser emails are delivered again if i delete index-files from .imap folder. So index is recreated and everything works again. I cant reproduce this problem, but every 2 days i have one user who is reporting this problem.
Iam surprised that no one has an opinion in this case. Nobody else noticed this problem? Yesterday i had a customer who was affected twice. First time we saw an errormessage, which leads to an index problem:
Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: Corrupted record in index cache file /home/popuser/username/mail/.imap/INBOX/dovecot.index.cache: UID 26876: Broken physical size in mailbox INBOX: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) Feb 13 15:46:58 hostname dovecot[30097]: imap(username): Error: read(/var/mail/username) failed: Cached message size smaller than expected (2118 < 8088, box=INBOX, UID=26876) (FETCH BODY[] for mailbox INBOX UID 26876)
At this point no new incoming mail is delivered by imapd. We deleted index files, dovecot reacreated them and all was working again. a day later same user was affected again. But like all other cases before there is no error or unusual logline. i turned mail_debug on, but no further hint. There are definitely new Mails in /var/mail/username but dovecot still shows old state from cache. I deleted index-files again and imap-client showed a lot of new unread mails. In log i can see that people are active in imap-clients and managing mails. If a new mail is coming in this period it seems to harm index-files some times. We never noticed same behaviour with long used dovecot 2.2.22
It seems that 2.2.33.2 which is bundled with Ubuntu18.04 LTS has a special problem.
Please help. What is your advice?
Second problem is similiar. I Upgraded a server from Ubuntu 16.04 to Ubuntu 18.04. This includes an upgrade from dovecot 2.2.22 to 2.2.33.2. After that i installed an self packaged dovecot 2.2.36.1 Now here is same problem, dovecot is not showing new mails, but the difference is we have a Raw backtrace in Log just as expected:
i think this crash is a special problem of dovecot 2.2.36.1. if i downgrade to 2.2.33.2 all is working well, upgrading again to 2.2.36.1 leeds to same crash.
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xa1ee2) [0x7f78b3b2cee2] -> /usr/lib/dovecot/libdovecot.so.0(+0xa1fda) [0x7f78b3b2cfda] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f78b3abb8a8] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_header+0x78a) [0x7f78b3e7940a] -> /usr/lib/dovecot/libdovecot.so.0(+0x83592) [0x7f78b3b0e592] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read+0x74) [0x7f78b3b38814] -> /usr/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3d) [0x7f78b3b392fd] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_header_stream+0x4a) [0x7f78b3e7a2ea] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_header_stream+0x4a) [0x7f78b3dfd8da] -> /usr/lib/dovecot/libdovecot-storage.so.0(imap_msgpart_open+0x24a) [0x7f78b3ebb57a] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76d81c] -> dovecot/imap m038422 ip.ip.ip.ip FETCH [0x5581ac76ba54] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76cd69] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75e1bb] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac76a09c] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768612] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac7686ac] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768a6d] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac768fbc] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x52) [0x7f78b3b43482] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x12e) [0x7f78b3b44b9e] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x36) [0x7f78b3b43516] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x7f78b3b436c8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f78b3ac6aa3] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b159] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xe7) [0x7f78b36bbb97] -> dovecot/imap myuser ip.ip.ip.ip FETCH [0x5581ac75b2fa] Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
Thanks, Hajo
Thanks, Hajo
Hi,
A few days ago I posted a similar issue. My environment has RHEL6 and 7 servers. When I last updated the servers RHEL6 servers mantained 2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used for sympa) processed a message for a user, its indexes were corrupted, and the user could't access his inbox through webmail, so I had to delete dovecot.* files from the user mail path to get it working again. This is the error shown at the dovecot log:
Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Panic: file mail-index-sync-keywords.c: line 227 (keywords_update_records): assertion failed: (data_offset >= sizeof(struct mail_index_record)) Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x3713268b8a] -> /usr/lib64/dovecot/libdovecot.so.0() [0x3713268bf6] -> /usr/lib64/dovecot/libdovecot.so.0() [0x37132224aa] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_keywords+0x7fd) [0x3713aca43d] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_record+0xec) [0x3713acacac] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_map+0x234) [0x3713acbae4] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_map+0x83) [0x3713abcce3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_refresh+0xe) [0x3713ab793e] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_sync_header_refresh+0x10) [0x3713a4e1e0] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4e330] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4f3d4] -> /usr/lib64/dovecot/libdovecot-storage.so.0() [0x3713a4f7b3] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xd9) [0x3713a4fa59] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x3713a7d731] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x3713a7e7b7] -> /usr/lib64/dovecot/libdovecot-storage.so.0(index_storage_get_status+0x62) [0x3713aa8fc2] -> /usr/lib64/dovecot/lib10_quota_plugin.so(+0xc3ec) [0x7fd272dfe3ec] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_get_status+0x5c) [0x3713a7f4fc] -> dovecot/imap(imap_status_get+0x7a) [0x41dbea] -> dovecot/imap(cmd_status+0x179) [0x413059] -> dovecot/imap(command_exec+0x3d) [0x4170bd] -> dovecot/imap() [0x416180] -> dovecot/imap() [0x41627a] -> dovecot/imap(client_handle_input+0x11d) [0x4164ed] -> dovecot/imap(client_input+0x6f) [0x41685f] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x3713278a56] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xa7) [0x3713279b27] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x38) [0x37132789c8] Feb 5 09:33:25 buzon1 dovecot: imap(user@domain): Fatal: master: service(imap): child 2057 killed with signal 6 (core dumped)
Thanks for your reply, so iam not the only one. I think downgrading is not an option for me. Ubuntu 18.04 comes with openssl 1.1.0 and it seems that older versions like 2.2.22 not compile successful. Best way for me would be a patch from Ubuntu-side, but without any errormessage or something its wasted time to file a bugreport. Though Ubuntu 18.04 should run for next 5 years.
My solution was to downgrade dovecot and dovecot-pigeonhole back to 2.2.10-8.el7.x86_64 Regards
--
*Gonzalo Palacios Goicolea* U.T de Infraestructura de Equipos Centrales /Tecnologías de la Información/ Universidad Autónoma de Madrid • Campus de Cantoblanco <3D"http://www.uam.es/">
Antes de imprimir este correo piense si es necesario.Cuidemos el medioambiente.
Thanks, Hajo
On 18 February 2019 09:28 Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Hello,
it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves.
Core dump with backtrace would help, if possible to acquire. Please refer to https://dovecot.org/bugreport.html for information how to get a core dump.
Aki
Hello,
Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:
On 18 February 2019 09:28 Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Hello,
it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves.
Thanks for your answer. Core dump with backtrace would help, if possible to acquire. Please refer to https://dovecot.org/bugreport.html for information how to get a core dump.
Aki
Unfortunately its hard to get a backtrace because dovecot is not crashing. so it seems to be more a kind of logic problem in code and no unexpected situation. yesterday evening i had next incident. I upgraded from 2.2.33.2 to 2.2.36.1, but same behaviour. Also 2.2.36.1 is tricked by the broken index and delivers no new mails. it starts delivering if i delete index files. At this point i cant tell if 2.2.36.1 also has same bug and writes a damaged index, but very likely. We dont know this problems with 2.2.22, between 2.2.22 and 2.2.33.2 a change on mbox-index code must happend which leads to this big problem. So imapd cant do what he was created for.
For next incident i prepared a 2.3.2.1 on base of Ubuntu 18.10 and will try this. In my opinion this is a major problem and i expect a lot of affected people with version > 2.2.22 and classic mbox-storage.
Thanks, Hajo
On 21.2.2019 10.53, Hajo Locke via dovecot wrote:
Hello,
Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:
On 18 February 2019 09:28 Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Hello, it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves. Thanks for your answer. Core dump with backtrace would help, if possible to acquire. Please refer to https://dovecot.org/bugreport.html for information how to get a core dump.
Aki
Unfortunately its hard to get a backtrace because dovecot is not crashing. so it seems to be more a kind of logic problem in code and no unexpected situation. yesterday evening i had next incident. I upgraded from 2.2.33.2 to 2.2.36.1, but same behaviour. Also 2.2.36.1 is tricked by the broken index and delivers no new mails. it starts delivering if i delete index files. At this point i cant tell if 2.2.36.1 also has same bug and writes a damaged index, but very likely. We dont know this problems with 2.2.22, between 2.2.22 and 2.2.33.2 a change on mbox-index code must happend which leads to this big problem. So imapd cant do what he was created for.
For next incident i prepared a 2.3.2.1 on base of Ubuntu 18.10 and will try this. In my opinion this is a major problem and i expect a lot of affected people with version > 2.2.22 and classic mbox-storage.
Thanks, Hajo
We consider mbox + procmail setup somewhat edge case, and if the core dump does not point into something more generic, it will probably not get fixed. It is more likely to have this working if you use dovecot-lda/lmtp with sieve instead of procmail.
Aki
Hello,
Am 21.02.2019 um 10:51 schrieb Aki Tuomi via dovecot:
On 21.2.2019 10.53, Hajo Locke via dovecot wrote:
Hello,
Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:
On 18 February 2019 09:28 Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Hello, it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves.
Thanks for your answer. Core dump with backtrace would help, if possible to acquire. Please refer to https://dovecot.org/bugreport.html for information how to get a core dump.
Aki
Unfortunately its hard to get a backtrace because dovecot is not crashing. so it seems to be more a kind of logic problem in code and no unexpected situation. yesterday evening i had next incident. I upgraded from 2.2.33.2 to 2.2.36.1, but same behaviour. Also 2.2.36.1 is tricked by the broken index and delivers no new mails. it starts delivering if i delete index files. At this point i cant tell if 2.2.36.1 also has same bug and writes a damaged index, but very likely. We dont know this problems with 2.2.22, between 2.2.22 and 2.2.33.2 a change on mbox-index code must happend which leads to this big problem. So imapd cant do what he was created for.
For next incident i prepared a 2.3.2.1 on base of Ubuntu 18.10 and will try this. In my opinion this is a major problem and i expect a lot of affected people with version > 2.2.22 and classic mbox-storage.
Thanks, Hajo We consider mbox + procmail setup somewhat edge case, and if the core dump does not point into something more generic, it will probably not get fixed. It is more likely to have this working if you use dovecot-lda/lmtp with sieve instead of procmail.
Aki
I think mbox+procmail is a classic setup and wide used and good solution for many usecases. Same setup we use many years. We run ~2 mio mailboxes. our automated systems depends on this setup. creating mailboxes, managing mailboxes, creating automated filterrules, backupsystem to tell something of them. we can not switch our whole mailsetup to work around this bug. How to get a dump if dovecot not crashing but has wrong behaviour? I would like to help and provide useful info, but it depends on kind of problem. I think if a classic setup is not working in dovecot any more, this is a serious problem.
Thanks, Hajo
On 21 Feb 2019, at 12.23, Hajo Locke via dovecot <dovecot@dovecot.org> wrote: I think mbox+procmail is a classic setup and wide used and good solution for many usecases. Same setup we use many years. We run ~2 mio mailboxes. our automated systems depends on this setup. creating mailboxes, managing mailboxes, creating automated filterrules, backupsystem to tell something of them. we can not switch our whole mailsetup to work around this bug. How to get a dump if dovecot not crashing but has wrong behaviour? I would like to help and provide useful info, but it depends on kind of problem. I think if a classic setup is not working in dovecot any more, this is a serious problem.
In you first email to this thread it says:
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
So imap is crashing and even dumping a core.
Also I must disagree with your mbox+procmail statement. mbox has always been very unoptimised mailbox format and everyone should be emphasised not to use it. Also that combination has always had problems with indexing and file locking. I would not use it on high volume mailservers. Or even medium volume mailservers.
Sami
Hello,
Am 21.02.2019 um 12:18 schrieb Sami Ketola via dovecot:
On 21 Feb 2019, at 12.23, Hajo Locke via dovecot <dovecot@dovecot.org> wrote: I think mbox+procmail is a classic setup and wide used and good solution for many usecases. Same setup we use many years. We run ~2 mio mailboxes. our automated systems depends on this setup. creating mailboxes, managing mailboxes, creating automated filterrules, backupsystem to tell something of them. we can not switch our whole mailsetup to work around this bug. How to get a dump if dovecot not crashing but has wrong behaviour? I would like to help and provide useful info, but it depends on kind of problem. I think if a classic setup is not working in dovecot any more, this is a serious problem. In you first email to this thread it says:
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
yes, but this is not 2.2.33.2 from Ubuntu 18.04, this happend after update to 2.2.36.1 I try to get a coredump from 2.2.36.1, but after my tests the basic behaviour is the same as in 2.2.33.2 -> no new mails and no errormessage. so iam not sure if this is really same problem or different. I was able now to catch a coredump of 2.2.36.1 I hope this is helpful and leads to the original problem. output of bt full is here: https://pastebin.com/awdpN4U3
So imap is crashing and even dumping a core.
Also I must disagree with your mbox+procmail statement. mbox has always been very unoptimised mailbox format and everyone should be emphasised not to use it. Also that combination has always had problems with indexing and file locking. I would not use it on high volume mailservers. Or even medium volume mailservers. Thats true, but worked for long years with dovecot. mbox+procmail long time was only possibility to store mails and iam sure a lot of people use it. Was there an official statement that support for mbox+procmail was dropped? Ubuntu 18.04 is fairly new OS and they offer still no 2.3 version (may be same bug), they offer 2.2.33.2 and i think this problem will reach users just with a delay. Please help, current situation is very unsatisfying.
Sami
Thanks, Hajo
On 2019-02-21 22:18, Sami Ketola via dovecot wrote:
On 21 Feb 2019, at 12.23, Hajo Locke via dovecot <dovecot@dovecot.org> wrote: I think mbox+procmail is a classic setup and wide used and good solution for many usecases. Same setup we use many years. We run ~2 mio mailboxes. our automated systems depends on this setup. creating mailboxes, managing mailboxes, creating automated filterrules, backupsystem to tell something of them. we can not switch our whole mailsetup to work around this bug. How to get a dump if dovecot not crashing but has wrong behaviour? I would like to help and provide useful info, but it depends on kind of problem. I think if a classic setup is not working in dovecot any more, this is a serious problem.
In you first email to this thread it says:
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
So imap is crashing and even dumping a core.
Also I must disagree with your mbox+procmail statement. mbox has always been very unoptimised mailbox format and everyone should be emphasised not to use it. Also that combination has always had problems with indexing and file locking. I would not use it on high volume mailservers. Or even medium volume mailservers.
Not directly affected by this issue since I'm not using mbox for any production system nor have I for many years. And it'd take a lot of effort to convince me to use mbox for anything someone would even dare to classify, even remotely, as "production". But if I understand OP's point of view correctly, he's not arguing necessarily for or against a specific mailbox format. Instead, he's flagging a regression and people will be very reluctant to upgrade or even adopt a certain feature in a new release of a product if regressions are seen as acceptable. Something that previously worked in an otherwise unchanged environment stopped working after an upgrade and this is a regression. Trying to convince people to move away from mbox is a very sensible approach, I'm all for it, but in cases like this not practical.
-- Adi Pircalabu
Hello,
Am 21.02.2019 um 23:06 schrieb Adi Pircalabu via dovecot:
On 2019-02-21 22:18, Sami Ketola via dovecot wrote:
On 21 Feb 2019, at 12.23, Hajo Locke via dovecot <dovecot@dovecot.org> wrote: I think mbox+procmail is a classic setup and wide used and good solution for many usecases. Same setup we use many years. We run ~2 mio mailboxes. our automated systems depends on this setup. creating mailboxes, managing mailboxes, creating automated filterrules, backupsystem to tell something of them. we can not switch our whole mailsetup to work around this bug. How to get a dump if dovecot not crashing but has wrong behaviour? I would like to help and provide useful info, but it depends on kind of problem. I think if a classic setup is not working in dovecot any more, this is a serious problem.
In you first email to this thread it says:
Feb 8 08:45:37 hostname dovecot[14882]: imap(myuser): Fatal: master: service(imap): child 14135 killed with signal 6 (core dumped)
So imap is crashing and even dumping a core.
Also I must disagree with your mbox+procmail statement. mbox has always been very unoptimised mailbox format and everyone should be emphasised not to use it. Also that combination has always had problems with indexing and file locking. I would not use it on high volume mailservers. Or even medium volume mailservers.
Not directly affected by this issue since I'm not using mbox for any production system nor have I for many years. And it'd take a lot of effort to convince me to use mbox for anything someone would even dare to classify, even remotely, as "production". But if I understand OP's point of view correctly, he's not arguing necessarily for or against a specific mailbox format. Instead, he's flagging a regression and people will be very reluctant to upgrade or even adopt a certain feature in a new release of a product if regressions are seen as acceptable. Something that previously worked in an otherwise unchanged environment stopped working after an upgrade and this is a regression. Trying to convince people to move away from mbox is a very sensible approach, I'm all for it, but in cases like this not practical.
yes, thanks for your support. I think this is the case here.
As conclusion: We believe mdbox is better storage format, but we cant switch 2mio mboxes + peripherie adhoc. We did a downgrade to 2.2.26.0 a few weeks ago. 2.2.26.0 is first version usable with openssl 1.1.0 and solves this issue. so this dovecot problem must introduced after 2.2.26.0 and leads to a problem where dovecot is not able to fulfill its basic purpose. until this downgrade we had a lot of problems and complaints and felt forsaken. Too bad that there is no really interest to fix mbox related problems.
Thanks, Hajo
El 21/02/2019 a las 10:51, Aki Tuomi via dovecot escribió:
On 21.2.2019 10.53, Hajo Locke via dovecot wrote:
Hello,
Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:
On 18 February 2019 09:28 Hajo Locke via dovecot <dovecot@dovecot.org> wrote:
Hello, it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves.
Thanks for your answer. Core dump with backtrace would help, if possible to acquire. Please refer to https://dovecot.org/bugreport.html for information how to get a core dump.
Aki
Unfortunately its hard to get a backtrace because dovecot is not crashing. so it seems to be more a kind of logic problem in code and no unexpected situation. yesterday evening i had next incident. I upgraded from 2.2.33.2 to 2.2.36.1, but same behaviour. Also 2.2.36.1 is tricked by the broken index and delivers no new mails. it starts delivering if i delete index files. At this point i cant tell if 2.2.36.1 also has same bug and writes a damaged index, but very likely. We dont know this problems with 2.2.22, between 2.2.22 and 2.2.33.2 a change on mbox-index code must happend which leads to this big problem. So imapd cant do what he was created for.
For next incident i prepared a 2.3.2.1 on base of Ubuntu 18.10 and will try this. In my opinion this is a major problem and i expect a lot of affected people with version > 2.2.22 and classic mbox-storage.
Thanks, Hajo We consider mbox + procmail setup somewhat edge case, and if the core dump does not point into something more generic, it will probably not get fixed. It is more likely to have this working if you use dovecot-lda/lmtp with sieve instead of procmail.
Aki
Hi Aki, In support of Hajo I've to say that a few days ago I posted a similar issue, and I use dovecot-lda+sieve. My environment has RHEL6 and 7 servers. When I last updated the servers RHEL6 servers mantained 2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used for sympa) processed a message for a user, its indexes were corrupted, and the user could't access his inbox through webmail, so I had to delete dovecot.* files from the user mail path to get it working again. My solution was to downgrade dovecot and dovecot-pigeonhole back to 2.2.10-8.el7.x86_64 Regards
*Gonzalo *
For replicated servers I'm stuck with 2.2.33.2 because of pop3/dsync problems, but on single servers I have no index problems after upgrading to dovecot-2.2.35-1.el7.centos.0.x86_64 or dovecot-2.2.36-3.el7.x86_64.
All servers run CentOS 7 (RHEL 7) but use lmtp delivery with mdbox and sieve. Maybe something in dovecot-lda has changed?
Best regards Gerald
Am 21.02.2019 um 14:12 schrieb Gonzalo Palacios Goicolea via dovecot <dovecot@dovecot.org>:
El 21/02/2019 a las 10:51, Aki Tuomi via dovecot escribió:
On 21.2.2019 10.53, Hajo Locke via dovecot wrote:
Hello,
Am 20.02.2019 um 10:39 schrieb Aki Tuomi via dovecot:
On 18 February 2019 09:28 Hajo Locke via dovecot <dovecot@dovecot.org> <mailto:dovecot@dovecot.org> wrote:
Hello, it seems we need a dovecot developers opinion. May be we hit a bug or cant help ourselves.
Thanks for your answer. Core dump with backtrace would help, if possible to acquire. Please refer to https://dovecot.org/bugreport.html <https://dovecot.org/bugreport.html> for information how to get a core dump.
Aki
Unfortunately its hard to get a backtrace because dovecot is not crashing. so it seems to be more a kind of logic problem in code and no unexpected situation. yesterday evening i had next incident. I upgraded from 2.2.33.2 to 2.2.36.1, but same behaviour. Also 2.2.36.1 is tricked by the broken index and delivers no new mails. it starts delivering if i delete index files. At this point i cant tell if 2.2.36.1 also has same bug and writes a damaged index, but very likely. We dont know this problems with 2.2.22, between 2.2.22 and 2.2.33.2 a change on mbox-index code must happend which leads to this big problem. So imapd cant do what he was created for.
For next incident i prepared a 2.3.2.1 on base of Ubuntu 18.10 and will try this. In my opinion this is a major problem and i expect a lot of affected people with version > 2.2.22 and classic mbox-storage.
Thanks, Hajo We consider mbox + procmail setup somewhat edge case, and if the core dump does not point into something more generic, it will probably not get fixed. It is more likely to have this working if you use dovecot-lda/lmtp with sieve instead of procmail.
Aki
Hi Aki, In support of Hajo I've to say that a few days ago I posted a similar issue, and I use dovecot-lda+sieve. My environment has RHEL6 and 7 servers. When I last updated the servers RHEL6 servers mantained 2.2.10-1_14.el6.x86_64 version, while RHEL7 updated dovecot from 2.2.10-8.el7.x86_64 to 2.2.36-3.el7.x86_64. When the RHEL7 servers (used for sympa) processed a message for a user, its indexes were corrupted, and the user could't access his inbox through webmail, so I had to delete dovecot.* files from the user mail path to get it working again. My solution was to downgrade dovecot and dovecot-pigeonhole back to 2.2.10-8.el7.x86_64 Regards Gonzalo
participants (7)
-
Adi Pircalabu
-
Aki Tuomi
-
Gerald Galster
-
Gonzalo Palacios Goicolea
-
Hajo Locke
-
Michael Slusarz
-
Sami Ketola