On Mi, 2011-04-20 at 15:43 +0100, Tobias Pfaff wrote: > 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
Right, the content *is* logged. I missed that in the source of SyncEvolution. > Maybe this special calendar entry #409 is corrupted? Can I find out > which one it is? You can run the sync with loglevel=4, then you'll get a longer -log.html which contains data dumps. But note that the SyncML message which triggers the error is likely to contain multiple events, so it won't be clear which of them triggers the error. Is there really nothing in the server logs? That's where you need to debug this problem. I suggest asking the Horde developers for help. Feel free to CC me. -- 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. _______________________________________________ SyncEvolution mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution
