Displaying 8 results from an estimated 8 matches for "51110".
Did you mean:
51,10
2018 Apr 02
1
2.3.1 Replication is throwing scary errors
Hi
[This is Dovecot 2.3.1 at FreeBSD STABLE-11.1 running in two jails at distinct servers.]
I did upgrade from 2.2.35 to 2.3.1 today, and I do become pounded by error messages at server1 (and vice versa at server2) as follows:
| Apr 2 17:12:18 <mail.err> server1.lan dovecot: doveadm: Error: dsync(server2.lan): I/O has stalled, \
no activity for 600 seconds (last sent=mail_change, last
2018 May 06
2
2.3.1 Replication is throwing scary errors
...re like ? />//>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't
> lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking
> failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to
> manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of
> locking/timeout, and now missing mails depending with server your MUA
> will conn...
2018 Apr 08
0
2.3.1 Replication is throwing scary errors
...2 are like ?
>
> Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't lock /home/to/USER1/.dovecot-sync.lock: \
> fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking failed: Timed out after 30 seconds \
> (WRITE lock held by pid 51110)
>
> [1] Even stopping dovecot will not end those processes. One has to manually kill those before restarting dovecot.
>
> After one day of testing 2.3.1 with a couple of those episodes of locking/timeout, and now missing mails depending with server your MUA will connect to, I went ba...
2018 May 06
3
2.3.1 Replication is throwing scary errors
.../>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't
>>> lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking
>>> failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to
>>> manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of
>>> locking/timeout, and now missing mails depending with server your MU...
2018 May 06
0
2.3.1 Replication is throwing scary errors
.../>//>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't
> > lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking
> > failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to
> > manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of
> > locking/timeout, and now missing mails depending with server your MUA
>...
2018 May 06
1
2.3.1 Replication is throwing scary errors
...erver2 are like ? />//>/Apr 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't
lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking
failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to
manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of
locking/timeout, and now missing mails depending with server your MUA
will connect to, I we...
2018 May 06
0
2.3.1 Replication is throwing scary errors
...r 3 17:10:49 <mail.err> server2.lan dovecot: doveadm: Error: Couldn't
>>>> lock /home/to/USER1/.dovecot-sync.lock: \ />/fcntl(/home/to/USER1/.dovecot-sync.lock, write-lock, F_SETLKW) locking
>>>> failed: Timed out after 30 seconds \ />/(WRITE lock held by pid 51110) />//>/[1] Even stopping dovecot will not end those processes. One has to
>>>> manually kill those before restarting dovecot. />//>/After one day of testing 2.3.1 with a couple of those episodes of
>>>> locking/timeout, and now missing mails depending with server...
2018 Apr 03
3
2.3.1 Replication is throwing scary errors
Hi,
> ------------------------------
>
> Message: 2
> Date: Mon, 2 Apr 2018 22:06:07 +0200
> From: Michael Grimm <trashcan at ellael.org>
> To: Dovecot Mailing List <dovecot at dovecot.org>
> Subject: 2.3.1 Replication is throwing scary errors
> Message-ID: <29998016-D62F-4348-93D1-613B13DA90DB at ellael.org>
> Content-Type: text/plain; charset=utf-8