[Dovecot] Is replication broken?
Steffen Kaiser
skdovecot at smail.inf.fh-brs.de
Thu Jan 30 16:02:24 EET 2014
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Thu, 30 Jan 2014, IT geek 31 wrote:
> Here are the errors on the remote server (the last two are a different
> mailbox!):
>
> Jan 30 13:25:16 Server2 dovecot: dsync-server(MailUser1): Panic: file
> mbox-lock.c: line 799 (mbox_lock): assertion failed: (lock_type == F_RDLCK
> || mbox->mbox_lock_type != F_RDLCK)
>
> Jan 30 13:25:16 Server2 dovecot: dsync-server(MailUser1): Fatal: master:
> service(doveadm): child 26627 killed with signal 6 (core not dumped - set
> service doveadm { drop_priv_before_exec=yes })
follow the advice, set ulimit -c unlimited, get a core dump, then
gdb /usr/.../binary core
bt full
post the output and use some subject line, e.g.
dsync-server(MailUser1): Panic: file mbox-lock.c: line 799 with coredump
to get Timos attension, that you have information for the panic.
> Any help is appreciated.
provide Timo any information about the core dump, give it an useful title,
e.g. "BUG Panic: file mbox-lock.c: with backtrace" to catch his attention
during his busy phases of work. Bumping the subject is not useful.
I found only this:
http://thr3ads.net/dovecot/2013/05/2645571-dsync-assert-failure-in-2.2.2
which says "Appears to work properly again in 2.2.4.".
> On 30 January 2014 14:29, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de>wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> On Thu, 30 Jan 2014, IT geek 31 wrote:
>>
>> On 30 January 2014 12:52, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de
>>>> wrote:
>>>
>>> On Thu, 30 Jan 2014, IT geek 31 wrote:
>>>>
>>>> Apologies for this being my 248th post about replication...
>>>>
>>>>>
>>>>> The current error I'm getting is:
>>>>>
>>>>> Jan 30 12:10:54 Server1 dovecot: dsync-local(MailUser1): Error: dsync(
>>>>> Server2.test.com): read() failed: read((fd)) failed: Connection reset
>>>>> by
>>>>> peer
>>>>>
>>>>>
>>>> this is a generic network error:
>>>> http://stackoverflow.com/questions/1434451/what-does-
>>>> connection-reset-by-peer-mean
>>>>
>>>> The other side of the communication channel closed the connection. It
>>>> also
>>>> does not neccessarily mean that other end point did it, but it could be a
>>>> firewall, router, whatever in between as well.
>>>>
>>>> Do you know why I am now getting:
>>>
>>>
>>> Jan 30 12:50:43 Server1 dovecot: dsync-local(MailUser1): Error: read(
>>> Server2.test.com) failed: EOF
>>>
>>
>> First you get "Connection reset by peer", the system closes the file
>> descriptot, Dovecot reads further from the handle and gets EOF. It's a
>> subsequent error, IMHO.
>>
>> - -- Steffen Kaiser
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.11 (GNU/Linux)
>>
>> iQEVAwUBUupTvXD1/YhP6VMHAQJxAggAyeX8kLK1AaoTsGPzIFfVW9GZKKF/eMpT
>> kgzL1UlY86ht0N3c2mvcOLBqjV15QSjNLaAV7wN4wPflMeescLScPUga21hrKKJV
>> 077T8ggLZE8Du6qTrkGej48/g6SdE/ZuyKiG/h/7s9OcdHJXHSIaqzVL7i+SNRmp
>> g0lo2n0axIk9M1mLLHw3SbbKEN1kDcrOGtdqh2Pl2wohLWNTJ+ZN1YpcBzJgOlq2
>> hIQeuVqvUXHLP8/S7CFngPVeZM+Kxr12HpOOt95/eqf4VEhyF1C1KXFVUXMbGkfX
>> +6bifTBkoGIzwznGHOIsigmJWrk9a7RM0rk5stFLvyGfdjxyN0VYCg==
>> =HOzr
>> -----END PGP SIGNATURE-----
>>
>
- --
Steffen Kaiser
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQEVAwUBUupbcXD1/YhP6VMHAQIPvwgAt/vLcy5rW9CuUIWuePrK4X3lr9930YM4
A1gs57G++lLEWkJAYN5uxQ/rODbluAq+7yXfR6HUoeOQu+ZCuxIjSnG5Dqo9iwYE
eJudAOs7oJIEBASfv3EaYtCCh44M8sZ6u+Y0+VFnNUbpqmr2hQn+OL67srsqnCFQ
J3xFEHFvdyLK8QrIhtMucSYh6KwmmPjKRNCy6/L71aq7ZCEfG0UR55gnv7XQ/BDF
kfTaC1pRUcZImO2WyTDwD8jXFjIhoH5bBiEbh7z2EKoKborpLK/hnSSpLvfhBZwf
A09Ep4fXP/wFmXuDsbrWyc4BZVl1a76Nq21IOPtTL5foP8SjALQHRg==
=PxdB
-----END PGP SIGNATURE-----
More information about the dovecot
mailing list