Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
Dovecot replication stopped working correctly after upgrade
View unanswered posts
View posts from last 24 hours

 
Reply to topic    Gentoo Forums Forum Index Networking & Security
View previous topic :: View next topic  
Author Message
Belliash
Advocate
Advocate


Joined: 24 Nov 2004
Posts: 2503
Location: Wroclaw, Poland

PostPosted: Tue May 01, 2018 5:21 pm    Post subject: Dovecot replication stopped working correctly after upgrade Reply with quote

After latest upgrade I am encountering a problem with dovecot. I have configured a replication and sometimes it fails to work. In logs I have found the following errors:

Code:
Apr 29 12:36:11 doveadm: Error: net_connect_unix(/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable
Apr 29 12:36:12 doveadm: Error: net_connect_unix(/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable
Apr 29 12:36:12 doveadm: Error: net_connect_unix(/run/dovecot/replicator-doveadm) failed: Resource temporarily unavailable


Also `doveadm replicator status` shows some failed request.
I have not done any reconfiguration - only system upgrade.

Anyone experiencing this kind of problems?
Everything (including dovecot) is working correctly. Only replication sometimes does not work...
_________________
Asio Software Technologies
Belliash IT Weblog


Last edited by Belliash on Thu Jul 23, 2020 10:20 am; edited 1 time in total
Back to top
View user's profile Send private message
gerdesj
l33t
l33t


Joined: 29 Sep 2005
Posts: 621
Location: Yeovil, Somerset, UK

PostPosted: Wed May 09, 2018 11:25 pm    Post subject: Re: Dovecot replication stopped working correctly after upgr Reply with quote

"file_create_locked(/var/spool/mail/mail.org/login/.maildir/.dovecot-box-sync.lock) failed"

Please try and create that file yourself as both root and the user that that process is running as. Also look out for read only file system (unlikely). If I had to guess, the user that a process is running as has been changed because "reasons" or perms have been changed. You've got a decently readable error message which is quite rare.

"WRITE lock held by pid 5921" if perms check out then this looks suspicious. Use ps aux | grep 5921 (or whatever) to see if that process is still running and get some more hints.

Back to basics mate 8)
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Networking & Security All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum