We have often found the below error in VPS servers using OpenVZ, and some cases using OpenStack, in neither case is used for storage or sharing ISCSI or NFS
Client can not receive messages via POP3 or IMAP
In /var/log/maillog the message below is seen
Oct 31 15:28:26 vps dovecot: pop3(user@domain.com): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07400] -> /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e07456] -> /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718e06df3] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718b6566b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mail_index_sync_commit+0x89) [0x2b3718b5ced9] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aeae4d] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aea357] -> /usr/lib64/dovecot/libdovecot-storage.so.0 [0x2b3718aea698] -> /usr/lib64/dovecot/libdovecot-storage.so.0(maildir_storage_sync_init+0xbb) [0x2b3718aea83b] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync_init+0x31) [0x2b3718b15e31] -> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_sync+0x27) [0x2b3718b18537] -> dovecot/pop3(client_create+0x332) [0x405702] -> dovecot/pop3 [0x40414b] -> dovecot/pop3 [0x404708] -> /usr/lib64/dovecot/libdovecot.so.0 [0x2b3718dc9a52] -> /usr/lib
Both POP3 as IMAP
Oct 31 15:24:42 vps dovecot: imap(user@domain.com): Warning: fscking index file /home/user/mail/domain.com/user/dovecot.index Oct 31 15:28:26 vps dovecot: pop3(user@domain.com): Warning: fscking index file /home/user/mail/domain.com/user/dovecot.index
Today I do to solve this the procedure below
- Access the directory mailbox
- Remove files dovecot.index *
- Run the command doveadm index-u $ user @ $ domain-q INBOX
The question is for what reason this only occurs with VPS servers, I do not find this error on any single physical server to virtual and dovecot settings are the same.
att
Alex Vitola