Discussion:
after update: broken pipe
Achim Zirner
2011-02-21 22:40:12 UTC
Permalink
hi list,

Ubuntu (running 10.10) offered updates for synce-files today. After
installing, I got:

...
member 2 (evo2-sync). Changetype ADDED
Member 2 of type evo2-sync had an error while getting changes: Broken
Pipe
Member 2 of type evo2-sync had an error while disconnecting: Broken Pipe
All clients have disconnected
The sync failed: Unable to read from one of the members
DEBUG:SynCE:finalize() called
All conflicts have been reported
Error while synchronizing: Unable to read from one of the members

....

anyone have the same problem? Do I have to reapply the patch?

cheers,

achim
Mark Ellis
2011-02-22 16:49:46 UTC
Permalink
Post by Achim Zirner
hi list,
Ubuntu (running 10.10) offered updates for synce-files today. After
...
member 2 (evo2-sync). Changetype ADDED
Member 2 of type evo2-sync had an error while getting changes: Broken
Pipe
Member 2 of type evo2-sync had an error while disconnecting: Broken Pipe
All clients have disconnected
The sync failed: Unable to read from one of the members
DEBUG:SynCE:finalize() called
All conflicts have been reported
Error while synchronizing: Unable to read from one of the members
....
anyone have the same problem? Do I have to reapply the patch?
It's not a synce problem, it's an evo2-sync problem.

As far as I can tell, this could be two things.

The source for address book in evo2-sync is most often set to "default",
which doesn't always work anymore. You can try changing this to the full
path to your address book eg.

file:///home/mark/.evolution/addressbook/local/system

Beware though this will cause a complete resync of your address book,
best to do it with a new partnership, new sync group, and blank device.

The other possibility is a calendar entry that evo2-sync tries to
convert and fails poorly. I had a few of these, ended up patching
evo2-sync to print out everything it was sending so I could see where it
failed. There might be a better way, but I don't know what it is.

Mark
Iain Buchanan
2011-02-24 01:36:31 UTC
Permalink
Hi,
Post by Mark Ellis
It's not a synce problem, it's an evo2-sync problem.
As far as I can tell, this could be two things.
The source for address book in evo2-sync is most often set to "default",
which doesn't always work anymore. You can try changing this to the full
path to your address book eg.
file:///home/mark/.evolution/addressbook/local/system
I assume this path has to exist on the filesystem? I'm using evolution
2.32.2, and although syncing "used to work" with this version now I get
"broken pipe". My last fix was to remove the default address book and
calendar and re-create them, but that hasn't worked this time.

The path for evo 2.32.2 seems to be something like
file:///home/iain/.local/share/evolution/addressbook/system which
contains three files:
addressbook.db addressbook.db.summary synce-sync.changes.db

Is that the same for you?

Doing this I get a complete resync (which is fine, I can fix that later)
but I'm still getting a broken pipe. msynctool output:

DEBUG:SynCE:Connect() called
DEBUG:SynCE:get_changeinfo() called
DEBUG:SynCE:slow sync requested for Contacts
DEBUG:SynCE:slow sync requested for Calendar
DEBUG:SynCE:slow sync requested for Tasks
INFO:SynCE:initiating device synchronization
INFO:SynCE:waiting for engine to complete sync
Synchronizing group "synce-sync"
The previous synchronization was unclean. Slow-syncing
Member 2 of type synce-opensync-plugin just connected
Member 1 of type evo2-sync just connected
All clients connected or error
Received an entry 20110125T043536Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED

********* big snip *********

Received an entry 20110125T043532Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
ReceiDEBUG:SynCE:disconnect() called
ved an entry 20110125T043534Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110125T043534Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110125T043533Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110125T043533Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110125T043535Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110125T043532Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110125T043535Z-30535-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Received an entry 20110208T041416Z-3502-1001-1-***@orpheus with data of size 4 from member 1 (evo2-sync). Changetype ADDED
Member 1 of type evo2-sync had an error while getting changes: Broken Pipe
Member 1 of type evo2-sync had an error while disconnecting: Broken Pipe
Received an entry 20101130T025747Z-1813-1001-1-***@orpheus with data of size 96 from member 2 (synce-opensync-plugin). Changetype ADDED

and much more, but that's the important broken pipe bit!
Post by Mark Ellis
The other possibility is a calendar entry that evo2-sync tries to
convert and fails poorly. I had a few of these, ended up patching
evo2-sync to print out everything it was sending so I could see where it
failed. There might be a better way, but I don't know what it is.
are you able to supply that patch by any chance? It might help me find
the problemo!

thanks,
--
Iain Buchanan <iaindb at netspace dot net dot au>

Never put off till run-time what you can do at compile-time.
-- D. Gries
Loading...