On Mi, 2011-04-20 at 13:48 +0100, Tobias Pfaff wrote:
tobias@telemach:~$ syncevolution --sync refresh-from-client horde
[ERROR] unexpected reply from server; might be a temporary problem,
Synchronization failed, see
I can't see the server's "unexpected replies", if
they are logged
somewhere, I will be happy to provide them here.
They might be logged in the -log.html file mentioned above. Search for
"unexpected content type". The root cause is that the server replies to
an HTTP POST with a reply which is not a SyncML message. The invalid
reply itself is not logged by SyncEvolution. Might be worthwhile to add
Most likely there was an internal failure in the server. I suggest that
you check your server logs. If you don't see anything there, you'll have
to start a network dump to see what the server sends.
Can I tell syncevolution to just send a limited number of entries
SyncEvolution and SyncML don't support that. You could move your events
out of the main calendar, then add them again in chunks while syncing
You can use the SyncEvolution command line for that (untested):
# make a backup with one file per event
syncevolution --export items horde calendar
# delete all events
syncevolution --delete-items horde calendar '*'
syncevolution --sync refresh-from-client horde calendar
# import some of them
for i in `seq 1 100`; do \
syncevolution --import items/$i horde calendar \
syncevolution horde calendar
Best Regards, Patrick Ohly
The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.