Sync_client errors upgraging from 2.3.16 to 2.4.5
Dear Bron
After running reconstruct - r -f -G on both client and replica and after about
22 hours all seems OK with no indications of any syncing errors.
There were some errors on some mailboxes while the reconstruct was run but none
since.
Thanks
Dear Bron
After running reconstruct - r -f -G on both client and replica and after
about 22 hours all seems OK with no indications of any syncing errors.
There were some errors on some mailboxes while the reconstruct was run
but none since.
Thanks
Stephen Carr
Bron Gondwana wrote:
On Sun,
On Sun, Dec 05, 2010 at 10:27:27AM +1030, Stephen Carr wrote:
> Dear All
>
> My prior idea was incorrect
>
> I just got this see below
>
> There was nothing reported by fuser in the users INBOX.
>
> So I ran reconstrust -f -r -G on both client and replica as per
> Bron's idea.
>
> Did a sync_
Dear All
My prior idea was incorrect
I just got this see below
There was nothing reported by fuser in the users INBOX.
So I ran reconstrust -f -r -G on both client and replica as per Bron's
idea.
Did a sync_client -v -l -m user.USER was OK
The started a rolling sync_client - seems OK
Shou
Dear All
I ran fuser * on the mailbox of the user that had the problem and got
cyrus.cache: 11366 11366m
cyrus.header: 2487 11366
cyrus.index: 2487 2487m 11366 11366
The processes are imapd
I killed the imapd processes and it seems OK.
The clients are using Thunderbir
On Sun, Dec 05, 2010 at 07:44:08AM +1030, Stephen Carr wrote:
> Dear All
>
> I thought the upgrade had worked but after more than 10 hours the
> following type of error were reported. This is from a short manual
> run of sync_client.
Can you try running a reconstruct -G of that user at each end?
