opensync-users

[Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

Hi, I'm trying to sync my Sharp SL-5500 running the GPE version of
OpenZaurus 3.5.4.1 and Evolution 2.6.1 on a Debian unstable system. The
gpe-sync plugin is configured to the Zaurus' IP address and my username,
port 22 and use_ssh is 1. evo2-sync is using the default config. SSH'ing
into the Zaurus works fine. I checked the code out of the SVN repo just
about an hour ago. Here is the output of 'msynctool --sync zaurus':

Synchronizing group "zaurus"
The previous synchronization was unclean. Slow-syncing
Member 1 of type gpe-sync just connected
Member 2 of type evo2-sync just connected
All clients connected or error
Received a entry pas-id-44522C6900000000 with data of size 4 from member
2. Changetype ADDED
Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
from member 2. Changetype ADDED
andrew@192.168.129.201's password: Received a entry
20060517T004749Z-3935-1000-1-5@r51 with data of size 4 from member 2.
Changetype ADDED
Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
from member 2. Changetype ADDED
Member 2 of type evo2-sync just sent all changes

Member 1 of type gpe-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
contact: (null)
Mapping Write Error: Couldn't commit contact: (null)
Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
Member 2 of type evo2-sync committed all changes.
Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
Couldn't commit event: (null)
Mapping Write Error: Couldn't commit event: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
Couldn't commit todo: (null)
Mapping Write Error: Couldn't commit todo: (null)
Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
Couldn't commit todo: (null)
Mapping Write Error: Couldn't commit todo: (null)
Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
Couldn't commit todo: (null)
Mapping Write Error: Couldn't commit todo: (null)
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Member 1 of type gpe-sync committed all changes.
All clients have written
The profile contains the unsupported custom attribute X-LIC-LOCATION.
The profile contains the unsupported custom attribute X-LIC-LOCATION.
The profile contains the unsupported custom attribute X-LIC-LOCATION.
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Member 1 of type gpe-sync just disconnected
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

Between the lines "Member 2 of type evo2-sync just sent all changes" and
"Member 1 of type gpe-sync just sent all changes" it stops and waits for
me to type my SSH password for the Zaurus.

I have tried deleting the PIM database files on the Zaurus and starting
again--the Zaurus is supposed to be empty. There are records in
Evolution that I want copied to the Zaurus on this first sync.

Any help would be greatly appreciated.

Regards,
Andrew Barr

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Martin F. <ma...@si...>]

Hello there,

I am the author of al this, so I should know what the problem is. I
was not yet able, to reproduce your error (but others though), but
this might be due to the old evolution plugin I have. Unfortunately I
can't compile the newer one. I am experiencing the same bug as
described under http://www.opensync.org/ticket/167 .

I will have a look at it this. I saw that I set in gpe_sync.c at about
line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what
threadsafe is, but I guess the plugin is not. This might be the cause
for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;"
and give it a go.
But I'll have a check for it.

So long,
Martin

On 5/17/06, Andrew Barr <and...@gm...> wrote:
> Hi, I'm trying to sync my Sharp SL-5500 running the GPE version of
> OpenZaurus 3.5.4.1 and Evolution 2.6.1 on a Debian unstable system. The
> gpe-sync plugin is configured to the Zaurus' IP address and my username,
> port 22 and use_ssh is 1. evo2-sync is using the default config. SSH'ing
> into the Zaurus works fine. I checked the code out of the SVN repo just
> about an hour ago. Here is the output of 'msynctool --sync zaurus':
>
> Synchronizing group "zaurus"
> The previous synchronization was unclean. Slow-syncing
> Member 1 of type gpe-sync just connected
> Member 2 of type evo2-sync just connected
> All clients connected or error
> Received a entry pas-id-44522C6900000000 with data of size 4 from member
> 2. Changetype ADDED
> Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
> from member 2. Changetype ADDED
> andrew@192.168.129.201's password: Received a entry
> 20060517T004749Z-3935-1000-1-5@r51 with data of size 4 from member 2.
> Changetype ADDED
> Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
> from member 2. Changetype ADDED
> Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
> from member 2. Changetype ADDED
> Member 2 of type evo2-sync just sent all changes
>
> Member 1 of type gpe-sync just sent all changes
> All clients sent changes or error
> All conflicts have been reported
> Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
> contact: (null)
> Mapping Write Error: Couldn't commit contact: (null)
> Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> Member 2 of type evo2-sync committed all changes.
> Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
> Couldn't commit event: (null)
> Mapping Write Error: Couldn't commit event: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
> Couldn't commit todo: (null)
> Mapping Write Error: Couldn't commit todo: (null)
> Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
> Couldn't commit todo: (null)
> Mapping Write Error: Couldn't commit todo: (null)
> Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
> Couldn't commit todo: (null)
> Mapping Write Error: Couldn't commit todo: (null)
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Member 1 of type gpe-sync committed all changes.
> All clients have written
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Member 1 of type gpe-sync just disconnected
> The profile contains the unsupported custom attribute X-LIC-LOCATION.
> Member 2 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to write one or more objects
> Error synchronizing: Unable to write one or more objects
>
> Between the lines "Member 2 of type evo2-sync just sent all changes" and
> "Member 1 of type gpe-sync just sent all changes" it stops and waits for
> me to type my SSH password for the Zaurus.
>
> I have tried deleting the PIM database files on the Zaurus and starting
> again--the Zaurus is supposed to be empty. There are records in
> Evolution that I want copied to the Zaurus on this first sync.
>
> Any help would be greatly appreciated.
>
> Regards,
> Andrew Barr
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEanpWhuM+Z62a52oRAvNLAJ0eqNhROBkT9vhVCqwGtXXqUhdtuACgoWSZ
> fpu9ileKJZzqlMzQaPR/VEU=3D
> =3DtiGn
> -----END PGP SIGNATURE-----
>
>
>

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

On Thu, 2006-05-18 at 14:58 +1200, Martin Felis wrote:
> Hello there,
>=20
> I am the author of al this, so I should know what the problem is. I
> was not yet able, to reproduce your error (but others though), but
> this might be due to the old evolution plugin I have.=20

Well, I'm using the latest evolution-data-server software available in
Debian, which is 1.6.1. The evo2-sync plugin was compiled against this.

> I will have a look at it this. I saw that I set in gpe_sync.c at about
> line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what
> threadsafe is, but I guess the plugin is not. This might be the cause
> for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;"
> and give it a go.

Unfortunately this didn't change anything. The output of msynctool is
the same. Thanks for the tip though.

Regards,
Andrew Barr

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Martin F. <ma...@si...>]

Hi,

I can't tell why you are having that problem, but as far as I know are
you not the only one. I updated the plugin so that the errors will now
be reported correctly. Maybe you can give it a try and send again the
output.

Thank you!
Martin

On 5/19/06, Andrew Barr <and...@gm...> wrote:
> Well, I'm using the latest evolution-data-server software available in
> Debian, which is 1.6.1. The evo2-sync plugin was compiled against this.
>
> > I will have a look at it this. I saw that I set in gpe_sync.c at about
> > line 206 "info->is_threadsafe =3D TRUE;". I have no real clue what
> > threadsafe is, but I guess the plugin is not. This might be the cause
> > for the problem. If you can, set it to "info->is_threadsafe =3D FALSE;"
> > and give it a go.
>
> Unfortunately this didn't change anything. The output of msynctool is
> the same. Thanks for the tip though.
>
> Regards,
> Andrew Barr
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEbHijhuM+Z62a52oRAtYeAJ9FaEb5J2RgVEOmTJ/sF5B8bFpTOgCgxZAi
> 3OVerqziEhGn0/y60MNGeuU=3D
> =3D0wD6
> -----END PGP SIGNATURE-----
>
>
>

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Andrew B. <and...@gm...>]

On Fri, 2006-05-19 at 14:35 +1200, Martin Felis wrote:
> Maybe you can give it a try and send again the
> output.

Here is the output of the updated plugin:

andrew@r51:~$ msynctool --sync zaurus
Synchronizing group "zaurus"
The previous synchronization was unclean. Slow-syncing
Member 1 of type gpe-sync just connected
Member 2 of type evo2-sync just connected
All clients connected or error
andrew@192.168.129.201's password: Received a entry
pas-id-44522C6900000000 with data of size 4 from member 2. Changetype
ADDED
Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004749Z-3935-1000-1-5@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005050Z-3935-1000-1-8@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004922Z-3935-1000-1-6@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T155339Z-4054-1000-1-0@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004703Z-3935-1000-1-4@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T004615Z-3935-1000-1-3@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T113610Z-4076-1000-1-0@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005034Z-3935-1000-1-7@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005145Z-3935-1000-1-9@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005343Z-3935-1000-1-12@r51 with data of size 4
from member 2. Changetype ADDED
Received a entry 20060517T005215Z-3935-1000-1-10@r51 with data of size 4
from member 2. Changetype ADDED
Member 2 of type evo2-sync just sent all changes

Member 1 of type gpe-sync just sent all changes
All clients sent changes or error
All conflicts have been reported
Member 2 of type evo2-sync committed all changes.
Error writing entry pas-id-44522C6900000000 to member 1: Couldn't commit
contact:  invalid Base64 sequence
Mapping Write Error: Couldn't commit contact:  invalid Base64 sequence
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004525Z-3935-1000-1-2@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004749Z-3935-1000-1-5@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Error writing entry 20060517T005050Z-3935-1000-1-8@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004922Z-3935-1000-1-6@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004703Z-3935-1000-1-4@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T004615Z-3935-1000-1-3@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Error writing entry 20060517T005034Z-3935-1000-1-7@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005145Z-3935-1000-1-9@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005343Z-3935-1000-1-12@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T005215Z-3935-1000-1-10@r51 to member 1:
Couldn't commit todo:  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit todo:  invalid value in attribute
LAST-MODIFIED
Error writing entry 20060517T155339Z-4054-1000-1-0@r51 to member 1:
Couldn't commit event  invalid value in attribute LAST-MODIFIED
Mapping Write Error: Couldn't commit event  invalid value in attribute
LAST-MODIFIED
The profile contains the unsupported custom attribute X-LIC-LOCATION.
Error writing entry 20060517T113610Z-4076-1000-1-0@r51 to member 1:
Couldn't commit event  invalid format for type "date/time" in attribute
DTSTART
Mapping Write Error: Couldn't commit event  invalid format for type
"date/time" in attribute DTSTART
Member 1 of type gpe-sync committed all changes.
All clients have written
Member 1 of type gpe-sync just disconnected
Member 2 of type evo2-sync just disconnected
All clients have disconnected
The sync failed: Unable to write one or more objects
Error synchronizing: Unable to write one or more objects

Hope this helps,
Andrew Barr

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Martin F. <ma...@si...>]

Hello again,

yes it definitely helps. The problem is probably libmimedir on the gpe
side which refuses to parse dates that are not in the format
libmimedir expects.

I have the same problem here. I will let you know if I have a solution.

Cheers,
Martin

On 5/20/06, Andrew Barr <and...@gm...> wrote:
> On Fri, 2006-05-19 at 14:35 +1200, Martin Felis wrote:
> > Maybe you can give it a try and send again the
> > output.
>
> Here is the output of the updated plugin:
>
> andrew@r51:~$ msynctool --sync zaurus
> Synchronizing group "zaurus"
> The previous synchronization was unclean. Slow-syncing
> Member 1 of type gpe-sync just connected
> Member 2 of type evo2-sync just connected
> All clients connected or error
> andrew@192.168.129.201's password: Received a entry
> pas-id-44522C6900000000 with data of size 4 from member 2. Changetype
> ADDED
> Received a entry 20060517T004525Z-3935-1000-1-2@r51 with data of size 4
> from member 2. Changetype ADDED

[...]

> Mapping Write Error: Couldn't commit event  invalid format for type
> "date/time" in attribute DTSTART
> Member 1 of type gpe-sync committed all changes.
> All clients have written
> Member 1 of type gpe-sync just disconnected
> Member 2 of type evo2-sync just disconnected
> All clients have disconnected
> The sync failed: Unable to write one or more objects
> Error synchronizing: Unable to write one or more objects
>
> Hope this helps,
> Andrew Barr
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.3 (GNU/Linux)
>
> iD8DBQBEbfnohuM+Z62a52oRAqE2AJ9DlyK/Mfr/DlgoawtzacPJDPaX/ACgvTYG
> FcVdUG0BQxu2466lUapCRAM=3D
> =3DBnoY
> -----END PGP SIGNATURE-----
>
>
>

Re: [Opensync-users] Sync fails between Evo2 and GPE

[Koen K. <ko...@do...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Martin Felis schreef:
> Hello again,
> 
> yes it definitely helps. The problem is probably libmimedir on the gpe
> side which refuses to parse dates that are not in the format
> libmimedir expects.
> 
> I have the same problem here. I will let you know if I have a solution.

Neal Walfield recently sent a patch[1] to Sebastian about date parsing,
maybe it can be of some help here as well.

regards,

Koen

[1] http://ewi546.ewi.utwente.nl/tmp/mimedir-duration.diff
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)

iD8DBQFEcC4HMkyGM64RGpERAjbLAKCmvopIqL3WLWlmt2aakSAC5gXDSACggtPi
xB0GsNNc7fa2vuSPrBNVlbk=
=aYoj
-----END PGP SIGNATURE-----