Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

Hi Oswald,

* Oswald Buddenhagen  [2018-02-16 11:37]:
> On Sat, Feb 10, 2018 at 12:20:18PM +0100, Peter P. wrote:
> > Now here is a thing that puzzles me. On that channel's imap server there
> > appears to exist folders
> > /Drafts
> > /Junk
> > /SPAM
> > /Sent
> > in addition to the ones known to me and synced by me
> > INBOX/Drafts
> > INBOX/Junk
> > INBOX/SPAM
> > INBOX/Sent
> >
> > [...]
> > Can this first group of folders be server-side duplicates of the
> > INBOX/... ones as the seem to hold the same content.
> >
> i expect these to be artifacts from the previous behavior change when
> you updated to mbsync 1.2.
You are correct, they were created locally when I updated without care.
I deleted these folders and all is fine, thank you for your kind help.

> that would imply that the contents aren't actually the same - the bogus
> folders should lack the more recent messages.
> 
> > Strangely they are not detected as folders by thunderbird, nor are
> > they visible in a Horde webmail interface.
> > 
> these certainly use the default namespace, so they don't see anything
> outside INBOX.
And I discovered that they are (were)local folders only. 

cheers, P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Oswald Buddenhagen]

On Sat, Feb 10, 2018 at 12:20:18PM +0100, Peter P. wrote:
> Now here is a thing that puzzles me. On that channel's imap server there
> appears to exist folders
>   /Drafts
>   /Junk
>   /SPAM
>   /Sent
> in addition to the ones known to me and synced by me
>   INBOX/Drafts
>   INBOX/Junk
>   INBOX/SPAM
>   INBOX/Sent
>
> [...]
> Can this first group of folders be server-side duplicates of the
> INBOX/... ones as the seem to hold the same content.
>
i expect these to be artifacts from the previous behavior change when
you updated to mbsync 1.2.
that would imply that the contents aren't actually the same - the bogus
folders should lack the more recent messages.

> Strangely they are not detected as folders by thunderbird, nor are
> they visible in a Horde webmail interface.
> 
these certainly use the default namespace, so they don't see anything
outside INBOX.

> On the (local) slave I discovered these folders as unix hidden folders
> .Drafts
> .Sent
> .Junk
> .SPAM
>
you didn't specify where you found these in, and what your Maildir
config is (your pasted config file lacked the local store).

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Aaron W. Swenson]

On 2018-02-08 11:06, Aaron W. Swenson wrote:
> On 2018-02-08 12:28, Peter P. wrote:
> > Hi list,
> > 
> > upgrading from to on a Debian testing box I do get the following for one
> > of my channels:
> > 
> >  Error: incompatible journal version (got 2, expected 3)
> > 
> > The mailing list archive doesn't seem to know about it so far.
> > 
> > thanks!
> > P
> 
> Same here on Gentoo. I was going to write about it, but kept forgetting
> to do so.
> 
> Upgraded from 1.2.1 to 1.3.0. Is there some upgrade step we need to do?

I know this isn’t going to be much help, but I fixed this problem by
finally figuring out which account it was complaining about, and
removing all .mbsyncstate files under the Inbox subdirectory.

It was a bit difficult figuring out which account and subdirectory were
the issue, but I finally noticed my work email hadn’t been updating on
my home machine.

Here’s the important bits from ‘mbsync -a -V -Dsm’:

Channel work
Opening master store work-remote...
Resolving imap.secureserver.net... ok
Connecting to imap.example.net (ip.ad.dr.ess:993)...
Opening slave store work-local...
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
reading sync state /home/titan/.maildir/work/Inbox/.mbsyncstate ...
  entry (18073,8946,8,)
  …snip a few thousand lines…
recovering journal ...
Error: incompatible journal version (got 2, expected 3)

mbsync then merrily continued taking care of the rest of folders before
going on to the next account.


signature.asc
Description: Digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

* Oswald Buddenhagen  [2018-02-09 23:32]:
> On Fri, Feb 09, 2018 at 08:11:28PM +0100, Peter P. wrote:
> > IMAPAccount mychannel
> > Host imap.whatever
> > User whoever
> > Pass whatever
> > 
> > IMAPStore mychannel-remote
> > Account mychannel
> > # Path INBOX
> > UseNamespace no
> > 
> > Channel mychannel
> > Master :mychannel-remote:
> > Slave :mychannel-local:
> > Patterns * !INBOX/Junk
> > Create Slave
> > SyncState *
> > Expunge Both
> > CopyArrivalDate yes
> > 
> 
> looks reasonable. try the -D option.

I figured out that it is the mailbox
\Sent 
which causes this error. With
 $mbsync -V -Dsm mychannel:/Sent
I get the error reported as:
[...]
Connection is now encrypted
Logging in...
Authenticating with SASL mechanism PLAIN...
recovering journal ...
Error: incompatible journal version (got 2, expected 3)
without further information.

On another Debian testing computer I do not get the "incompatible journal
version" error with the same config and mbsync 1.3.0.
Let me know if you want me to invenstigate further, possibly comparing
journal files etc...

Now here is a thing that puzzles me. On that channel's imap server there
appears to exist folders
/Drafts
/Junk
/SPAM
/Sent
in addition to the ones known to me and synced by me
INBOX/Drafts
INBOX/Junk
INBOX/SPAM
INBOX/Sent
This first group of folders are the ones causing errors:
Error: channel mychannel: master /Drafts cannot be opened.
Error: channel mychannel: master /Junk cannot be opened.
Error: channel mychannel: master /SPAM cannot be opened.
and /Sent is causing the aforementioned
Error: incompatible journal version (got 2, expected 3)

If I add the first group of folders to the Patterns to avoid as 
Patterns !/Drafts !/Junk !/SPAM !/Sent
all four errors go away.

Can this first group of folders be server-side duplicates of the
INBOX/... ones as the seem to hold the same content. Strangely they are
not detected as folders by thunderbird, nor are they visible in a Horde
webmail interface.

On the (local) slave I discovered these folders as unix hidden folders
.Drafts
.Sent
.Junk
.SPAM
I would be fine with deleting them from my slave and excluding them as
Pattern as I don't want to sync them, but wonder if this is due to my
mistake or if it's something in 1.3.0 that might have triggered this.

Thank you for your time and help, it is greatly appreciated!

Peter

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Oswald Buddenhagen]

On Fri, Feb 09, 2018 at 08:11:28PM +0100, Peter P. wrote:
> IMAPAccount mychannel
> Host imap.whatever
> User whoever
> Pass whatever
> 
> IMAPStore mychannel-remote
> Account mychannel
> # Path INBOX
> UseNamespace no
> 
> Channel mychannel
> Master :mychannel-remote:
> Slave :mychannel-local:
> Patterns * !INBOX/Junk
> Create Slave
> SyncState *
> Expunge Both
> CopyArrivalDate yes
> 

looks reasonable. try the -D option.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

* Oswald Buddenhagen  [2018-02-08 20:01]:
> On Thu, Feb 08, 2018 at 07:32:17PM +0100, Peter P. wrote:
> > Trying to apply what you recomment I am noticing the following
> > dicrepancy between Debian's 1.2.1-2 and 1.3.0-1: [...]
> > 
> that looks related to one NEWS item ... for 1.2.0.
> i'd need to see the full config to make a call.
Here it is:

IMAPAccount mychannel
Host imap.whatever
User whoever
Pass whatever

IMAPStore mychannel-remote
Account mychannel
# Path INBOX
UseNamespace no

Channel mychannel
Master :mychannel-remote:
Slave :mychannel-local:
Patterns * !INBOX/Junk
Create Slave
SyncState *
Expunge Both
CopyArrivalDate yes

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Oswald Buddenhagen]

On Thu, Feb 08, 2018 at 07:32:17PM +0100, Peter P. wrote:
> Trying to apply what you recomment I am noticing the following
> dicrepancy between Debian's 1.2.1-2 and 1.3.0-1: [...]
> 
that looks related to one NEWS item ... for 1.2.0.
i'd need to see the full config to make a call.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Peter P.]

* Oswald Buddenhagen  [2018-02-08 18:44]:
> On Thu, Feb 08, 2018 at 12:28:15PM +0100, Peter P. wrote:
> > upgrading from to on a Debian testing box I do get the following for one
> > of my channels:
> > 
> >  Error: incompatible journal version (got 2, expected 3)
> > 
> that means that mbsync didn't properly finish syncing some box(es),
> possibly already for a long time.
> 
> the upgrade path is to get the latest 1.2 code and run it on the
> boxes in question. if you see it failing, try with --noop.
> once it finishes successfully, you can start using 1.3.

Thank you Oswald! 
Trying to apply what you recomment I am noticing the following
dicrepancy between Debian's 1.2.1-2 and 1.3.0-1:

With 1.3.0-1 I do get the following errors running: 

$ mbsync mychannel

C: 0/1  B: 12/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: channel mychannel: master /Drafts cannot be opened.
C: 0/1  B: 13/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: channel mychannel: master /Junk cannot be opened.
C: 0/1  B: 14/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: channel mychannel: master /SPAM cannot be opened.
C: 0/1  B: 15/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0
Error: incompatible journal version (got 2, expected 3)
C: 1/1  B: 16/16  M: +0/0 *0/0 #0/0  S: +0/0 *0/0 #0/0

While these do not appear with 1.2.1-2 at all. 

Thanks!
P

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Oswald Buddenhagen]

On Thu, Feb 08, 2018 at 12:28:15PM +0100, Peter P. wrote:
> upgrading from to on a Debian testing box I do get the following for one
> of my channels:
> 
>  Error: incompatible journal version (got 2, expected 3)
> 
that means that mbsync didn't properly finish syncing some box(es),
possibly already for a long time.

the upgrade path is to get the latest 1.2 code and run it on the
boxes in question. if you see it failing, try with --noop.
once it finishes successfully, you can start using 1.3.

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel

Re: Error: incompatible journal version (got 2, expected 3)

[Aaron W. Swenson]

On 2018-02-08 12:28, Peter P. wrote:
> Hi list,
> 
> upgrading from to on a Debian testing box I do get the following for one
> of my channels:
> 
>  Error: incompatible journal version (got 2, expected 3)
> 
> The mailing list archive doesn't seem to know about it so far.
> 
> thanks!
> P

Same here on Gentoo. I was going to write about it, but kept forgetting
to do so.

Upgraded from 1.2.1 to 1.3.0. Is there some upgrade step we need to do?


signature.asc
Description: Digital signature
--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot___
isync-devel mailing list
isync-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/isync-devel