Re: Strange index error on NFS after upgrade to CentOS 7 from 6
Il 25/08/20 16:27, Aki Tuomi ha scritto: On 25/08/2020 16:43 Alessio Cecchi wrote: Hi, I'm running 3 Dovecot director and 6 Dovecot backend on CentOS 6 and Dovecot 2.3.10, with Maildir shared on NFSv3 (on NetApp). Since CentOS 6 will be EOL on November I started to upgrade to CentOS 7 the first Dovecot backend. But after Director start to direct users on new CentOS 7 server some errors, for any users, come up, an example: Aug 21 14:56:41 Error: imap(ales...@cecchi.it) session=<11sBlmKtj1qelGW/>: Mailbox INBOX: Broken or unexpectedly changed file /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: Invalid data: - re-reading from beginning Aug 21 14:56:41 Error: imap(ales...@cecchi.it) session=<11sBlmKtj1qelGW/>: Mailbox INBOX: Broken file /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: Invalid data: Consequently to the error the user see the synchronization of his mailbox again. The Dovecot version and configuration is the same that in CentOS 6, also the mount parameters are the same, so I suspect that could be some difference in the NFS client implementation on CentOS 7. This the entry on fstab: 192.168.1.2:/vmail0 /mnt/vmail0 nfs rw,nfsvers=3,noatime,nodiratime,_netdev,nordirplus 0 0 # Bind for vmail0 /mnt/vmail0/domains /home/vmail/domains none x-systemd.requires=/mnt/vmail0,x-systemd.automount,bind 0 0 In the archive of this list I found a similar issue but without a solutions: https://dovecot.org/pipermail/dovecot/2018-October/113207.html Do you have any suggestions? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice What versions are you running mixed? Aki Hi Aki, the only mixed version is CentOS version on Dovecot backend: CentoS 6 backend: # dovecot -n # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: Linux 2.6.32-754.29.2.el6.x86_64 x86_64 CentOS release 6.10 (Final) Centos 7 backend: # dovecot -n # 2.3.10 (0da0eff44): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.10 (bf8ef1c2) # OS: Linux 3.10.0-1127.18.2.el7.x86_64 x86_64 CentOS Linux release 7.8.2003 (Core) and also the dovecot configuration is the same (was copied via rsync): $ diff dovecot-a-cos6.txt dovecot-a-cos7.txt 3,4c3,4 < # OS: Linux 2.6.32-754.29.2.el6.x86_64 x86_64 CentOS release 6.10 (Final) < # Hostname: pop01 --- > # OS: Linux 3.10.0-1127.18.2.el7.x86_64 x86_64 CentOS Linux release 7.8.2003 (Core) > # Hostname: pop02 126c126 < import_environment = TZ CORE_OUTOFMEM CORE_ERROR --- > import_environment = TZ CORE_OUTOFMEM CORE_ERROR LISTEN_PID LISTEN_FDS I have noticed this, a user have the "Indalid data" error on Centos 7, I moved him to Centos 6, with doveadm director move, and the "Invalid data" error come again also on Centos 6 but only one time, like if the dovecot-uidlist file was wrong and need to be fixed, but after the "fix" executed from Dovecot in Centos 6 the file become fine. Instead, on Centos 7 the "Invalid data" error comes multiple time. Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice
Strange index error on NFS after upgrade to CentOS 7 from 6
Hi, I'm running 3 Dovecot director and 6 Dovecot backend on CentOS 6 and Dovecot 2.3.10, with Maildir shared on NFSv3 (on NetApp). Since CentOS 6 will be EOL on November I started to upgrade to CentOS 7 the first Dovecot backend. But after Director start to direct users on new CentOS 7 server some errors, for any users, come up, an example: Aug 21 14:56:41 Error: imap(ales...@cecchi.it) session=<11sBlmKtj1qelGW/>: Mailbox INBOX: Broken or unexpectedly changed file /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: Invalid data: - re-reading from beginning Aug 21 14:56:41 Error: imap(ales...@cecchi.it) session=<11sBlmKtj1qelGW/>: Mailbox INBOX: Broken file /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: Invalid data: Consequently to the error the user see the synchronization of his mailbox again. The Dovecot version and configuration is the same that in CentOS 6, also the mount parameters are the same, so I suspect that could be some difference in the NFS client implementation on CentOS 7. This the entry on fstab: 192.168.1.2:/vmail0 /mnt/vmail0 nfs rw,nfsvers=3,noatime,nodiratime,_netdev,nordirplus 0 0 # Bind for vmail0 /mnt/vmail0/domains /home/vmail/domains none x-systemd.requires=/mnt/vmail0,x-systemd.automount,bind 0 0 In the archive of this list I found a similar issue but without a solutions: https://dovecot.org/pipermail/dovecot/2018-October/113207.html Do you have any suggestions? Thanks -- Alessio Cecchi Postmaster @ http://www.qboxmail.it https://www.linkedin.com/in/alessice
Re: Dovecot search message problem
Hi all
I think I solved the problem by changing the treatment of plugins in the
dovecot configuration.
The global definition of the mail_plugins parameter was not being loaded
within protocol sessions. I added the load in all the blocks where the
sessions are defined.
Now I ask, is it necessary to add in all sessions, better to say, the fts
fts_solr plugins would not only be necessary in the imap protocol? This is
a question to ensure less memory usage.
Below is my current configuration:
root@server01:~# doveconf -n
# 2.3.4.1 (f79e8e7e4): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.4 ()
# OS: Linux 4.19.0-10-amd64 x86_64 Debian 10.5
# Hostname: server01.example1.com
auth_mechanisms = plain login
disable_plaintext_auth = no
doveadm_password = # hidden, use -P to show it
doveadm_port = 2727
listen = *,[::]
log_timestamp = "%Y-%m-%d %H:%M:%S "
mail_debug = yes
mail_max_userip_connections = 100
mail_plugins = " notify replication fts fts_solr"
mail_privileged_group = vmail
namespace inbox {
inbox = yes
location =
mailbox Drafts {
auto = no
special_use = \Drafts
}
mailbox Junk {
auto = subscribe
autoexpunge = 60 days
special_use = \Junk
}
mailbox Sent {
auto = no
special_use = \Sent
}
mailbox "Sent Messages" {
auto = no
special_use = \Sent
}
mailbox Trash {
auto = subscribe
autoexpunge = 60 days
special_use = \Trash
}
prefix =
}
passdb {
args = /etc/dovecot/dovecot-sql.conf
driver = sql
}
plugin {
fts = solr
fts_solr = url=http://localhost:8983/solr/dovecot/
mail_replica = tcp:xxx.xxx.xxx.3:2727
quota = dict:user::file:/var/vmail/%d/%n/.quotausage
sieve = /var/vmail/%d/%n/.sieve
sieve_max_redirects = 25
}
protocols = imap pop3
service aggregator {
fifo_listener replication-notify-fifo {
group = root
mode = 0660
user = vmail
}
unix_listener replication-notify {
group = root
mode = 0660
user = vmail
}
}
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0660
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
user = root
}
service doveadm {
inet_listener {
port = 2727
}
user = vmail
}
service imap-login {
client_limit = 1000
process_limit = 512
}
service lmtp {
unix_listener /var/spool/postfix/private/dovecot-lmtp {
group = postfix
mode = 0600
user = postfix
}
}
service replicator {
process_min_avail = 1
unix_listener replicator-doveadm {
group = root
mode = 0660
user = vmail
}
}
service stats {
unix_listener stats-reader {
group = vmail
mode = 0660
user = vmail
}
unix_listener stats-writer {
group = vmail
mode = 0660
user = vmail
}
}
ssl_ca =
escreveu:
> Hi
>
> I have a dovecot installed on debian 10 using solr to have a better search
> speed in emails.
> I am observing after an upgrade of the debian dovecot package the error
> below:
>
> Aug 25 00:33:45 server01 dovecot:
> imap(usern...@example.com)<24104>:
> Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b)
> [0x7f0faeaeb62b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1)
> [0x7f0faeaeb6c1] -> /usr/lib/dovecot/libdovecot.so.0(+0x4a149)
> [0x7f0faea5a149] -> /usr/lib/dovecot/libdovecot.so.0(+0x474ac)
> [0x7f0faea574ac] ->
> /usr/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x104)
> [0x7f0faead3844] ->
> /usr/lib/dovecot/libdovecot.so.0(message_search_msg+0xa8) [0x7f0faead5df8]
> -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xcf89e) [0x7f0faec6e89e] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(mail_search_args_foreach+0x45)
> [0x7f0faebf0445] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd0774)
> [0x7f0faec6f774] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xd1a68)
> [0x7f0faec70a68] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(index_storage_search_next_nonblock+0x61)
> [0x7f0faec710e1] ->
> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_search_next_nonblock+0x28)
> [0x7f0faebf9e58] -> dovecot/imap(+0x2691f) [0x55a43cada91f] ->
> dovecot/imap(command_exec+0x70) [0x55a43cad3d80] -> dovecot/imap(+0x25ed2)
> [0x55a43cad9ed2] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0x111)
> [0x7f0faeb018f1] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xd0)
> [0x7f0faeb03070] ->
> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f0faeb01b7c]
> -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f0faeb01ce0] ->
> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f0faea820d3]
> -> dovecot/imap(main+0x325) [0x55a43cac4bf5] ->
> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f0fae86809b] ->
> dovecot/imap(_start+0x2a) [0x55a43cac4d8a]
> Aug 25 00:33:45 server01 dovecot:
> imap(usern...@example.com)<24104>:
> Fatal: master: service(imap): child 24104 killed with signal 6 (core dumped)
>
> The package versions are:
> ii dovecot-core
Panic with namespace
Hi,
I was trying to configure a namespace like this:
10-mail.conf
namespace inbox {
prefix = "iNBox."
inbox = yes
}
And when a client connected, I got the panic below. Dovecot version is 2.3.4.1
(f79e8e7e4) on Debian 10.
Aug 25 16:18:27 kman dovecot: imap(kman@...)<20082>: Panic:
file mailbox-list-maildir-iter.c: line 511 (maildir_list_iter_next
): assertion failed: ((ctx->info.flags & MAILBOX_NOCHILDREN) != 0)
Aug 25 16:18:27 kman dovecot: imap(kman@...)<20082>: Error:
Raw
backtrace: /usr/lib/dovecot/libdovecot.so.0(+0xdb62b) [0x7f659
9d9962b] -> /usr/lib/dovecot/libdovecot.so.0(+0xdb6c1) [0x7f6599d996c1] ->
/usr/lib/dovecot/libdovecot.so.0(+0x4a149) [0x7f6599d08149] -> /usr/lib/dov
ecot/libdovecot-storage.so.0(+0x45b6e) [0x7f6599e92b6e] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_sync+0x1dc)
[0x7f6599f08c6c] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_index_refresh_force+0xfb)
[0x7f6599f0ac3b] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb9274
) [0x7f6599f06274] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb9467)
[0x7f6599f06467] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_exists+0
x68) [0x7f6599ea70e8] ->
/usr/lib/dovecot/libdovecot-storage.so.0(mailbox_list_mailbox+0x1f6)
[0x7f6599eb6126] -> /usr/lib/dovecot/libdovecot-storage.
so.0(mailbox_list_iter_init_namespaces+0x208) [0x7f6599f0be08] ->
dovecot/imap(cmd_list_full+0x60e) [0x5654c07d02de] ->
dovecot/imap(command_exec+0x70
) [0x5654c07d9d80] -> dovecot/imap(+0x1e3f2) [0x5654c07d83f2] ->
dovecot/imap(+0x1e494) [0x5654c07d8494] ->
dovecot/imap(client_handle_input+0x1b5) [0
x5654c07d8845] -> dovecot/imap(client_input+0x7e) [0x5654c07d8d6e] ->
/usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x6f) [0x7f6599dafadf] -> /usr/
lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0x136) [0x7f6599db10d6]
-> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x4c) [0x7f65
99dafb7c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x40) [0x7f6599dafce0]
-> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f659
9d300d3] -> dovecot/imap(main+0x325) [0x5654c07cabf5] ->
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f6599b1b09b] ->
dovecot/imap(_sta
rt+0x2a) [0x5654c07cad8a]
-- K
Re: unsupported auth mechanism
Thank you! I really appreciate your help > Il 24/08/2020 18:37 Josef 'Jeff' Sipek ha > scritto: > > > On Mon, Aug 24, 2020 at 17:11:04 +0200, absolutely_f...@libero.it wrote: > > Hi, > > > > last friday I upgraded from dovecot-2.3.10.1_2 to dovecot-2.3.11.3 > > (FreeBSD). > > > > Since then, I started having some issues with some customers. > > > > The log I see is like: > > > > pop3-login: Disconnected (tried to use unsupported auth mechanism): > > user=, method=USER, rip=x,y,x,z, lip=x,y,w,z, > > session= > > > > While, before upgrade, same user logged succesfully: > > > > pop3-login: Login: user=, method=PLAIN, rip=x,y,x,z, > > lip=x,y,w,z, mpid=62876, session= > > The only thing that comes to mind is the pop3 issue where an auth attempt > after a failed auth attempt would always fail. I'm not sure why the client > that's having issues is failing the first attempt (unless it tries an > unsupported mechanism first, and then tries to fall back to PLAIN). Anyway, > there is a fix on the master branch. > > https://github.com/dovecot/core/commit/d0ea7f9f4530878a40ae0275cf0c36d3ff9111fc > > You can try to patch the 2.3.11.3 code with it and see if that helps. > 2.3.12 and 2.3.11.4 (if there is one) will have this fix. > > Jeff. > > -- > mainframe, n.: > An obsolete device still used by thousands of obsolete companies serving > billions of obsolete customers and making huge obsolete profits for their > obsolete shareholders. And this year's run twice as fast as last year's.
Re: Strange index error on NFS after upgrade to CentOS 7 from 6
> On 25/08/2020 16:43 Alessio Cecchi wrote: > > > Hi, > > I'm running 3 Dovecot director and 6 Dovecot backend on CentOS 6 and Dovecot > 2.3.10, with Maildir shared on NFSv3 (on NetApp). > > Since CentOS 6 will be EOL on November I started to upgrade to CentOS 7 the > first Dovecot backend. > > But after Director start to direct users on new CentOS 7 server some errors, > for any users, come up, an example: > > Aug 21 14:56:41 Error: imap(ales...@cecchi.it) session=<11sBlmKtj1qelGW/>: > Mailbox INBOX: Broken or unexpectedly changed file > /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: > Invalid data: - re-reading from beginning > Aug 21 14:56:41 Error: imap(ales...@cecchi.it) session=<11sBlmKtj1qelGW/>: > Mailbox INBOX: Broken file > /home/vmail/domains/cecchi.it/alessio/Maildir/dovecot-uidlist line 18664: > Invalid data: > > Consequently to the error the user see the synchronization of his mailbox > again. > > The Dovecot version and configuration is the same that in CentOS 6, also the > mount parameters are the same, so I suspect that could be some difference in > the NFS client implementation on CentOS 7. > > This the entry on fstab: > > 192.168.1.2:/vmail0 /mnt/vmail0 nfs > rw,nfsvers=3,noatime,nodiratime,_netdev,nordirplus 0 0 > # Bind for vmail0 > /mnt/vmail0/domains /home/vmail/domains none > x-systemd.requires=/mnt/vmail0,x-systemd.automount,bind 0 0 > > In the archive of this list I found a similar issue but without a solutions: > > https://dovecot.org/pipermail/dovecot/2018-October/113207.html > > Do you have any suggestions? > Thanks > > -- > Alessio Cecchi > Postmaster @ http://www.qboxmail.it > https://www.linkedin.com/in/alessice What versions are you running mixed? Aki
Re: zlib errors after upgrading
> On 25/08/2020 14:35 Robert Nowotny wrote: > > > I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 > > > Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870>: Error: > Mailbox Sent: UID=40826: > read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: > read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe > (FETCH BODY[]) > > many of those entries > > after installing2.3.10.1 those files are still broken - but new files are > working again. > > anything I can tweak or do ? > > Hi! Is it possible your mdbox file is corrupted? Can you share doveconf -n? Aki
zlib errors after upgrading
I get ZLIB Errors after dovecot upgrade from 2.3.10.1 to 2.3.11.3 Aug 21 15:27:34 lxc-imap dovecot: imap(acsida)<63870>: Error: Mailbox Sent: UID=40826: read(zlib(/home/vmail/virtualmailboxes/acsida/storage/m.2409)) failed: read(/home/vmail/virtualmailboxes/acsida/storage/m.2409) failed: Broken pipe (FETCH BODY[]) many of those entries after installing 2.3.10.1 those files are still broken - but new files are working again. anything I can tweak or do ? smime.p7s Description: S/MIME Cryptographic Signature
