Patrick Ohly schrieb:
> On Mi, 2011-04-20 at 13:48 +0100, Tobias Pfaff wrote:
>> tobias@telemach:~$ syncevolution --sync refresh-from-client horde calendar
> [...]
>> [ERROR] unexpected reply from server; might be a temporary problem, try
>> again later
> [...]
>> Synchronization failed, see
>> /home/tobias/.cache/syncevolution/horde-2011-04-19-18-47/syncevolution-log.html
>> for details.
> [...]
>> 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
> that.

Okay, I've found it:

# [2011-04-19 18:48:20.674] calendar: sent 409/1913
# [2011-04-19 18:48:26.745] unexpected content type 'text/html;
charset=UTF-8' in reply, 183 bytes: Fatal error: Call to a member
function timestamp() on a non-object in
horde/kronolith/lib/Driver/sql.php on line 960

Maybe this special calendar entry #409 is corrupted? Can I find out
which one it is?

>> Can I tell syncevolution to just send a limited number of entries per
>> run initially?
> 
> 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
> repeatedly.
> 
> You can use the SyncEvolution command line for that (untested):
> 
> # make a backup with one file per event
> mkdir items
> syncevolution --export items horde calendar
> ls items
> # 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 \
> done
> syncevolution horde calendar
> # repeat...

Looks like a reasonable way, I could give it a try.

-- 
Tobias Pfaff
Bochum
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution

Reply via email to