9:48 p.m.
syncevolution-evolution_1.1.1-2_i386 0.6.2maverick1
Horde 3.3.11
Evolution 2.30.3/Ubuntu
I'm trying to sync my calendar and contacts from Evolution with Horde
(My goal is to keep my Android phone synced with Evolution, but that'll
be the next step.)
Syncing contacts seems to work fine, but there appears to be a timeout
when syncing the calendar. According to syncevolution's output it sends
more than 400 entries to Horde, but in Horde's database there are only
114 entries.
This is syncevolution's output:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
tobias@telemach:~$ syncevolution horde
[INFO] todo: inactive
[INFO] memo: inactive
[INFO] addressbook: inactive
[INFO] calendar: starting first time sync, two-way
[INFO] calendar: first time sync done unsuccessfully
[ERROR] unexpected slow sync (local, status 22000)
Synchronization failed, see
/home/tobias/.cache/syncevolution/horde-2011-04-19-18-44/syncevolution-log.html
for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| unexpected slow sync (local, status 22000) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Tue Apr 19 18:44:53 2011, duration 0:06min |
| unexpected slow sync (local, status 22000) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: unexpected slow sync (local, status 22000)
Doing a slow synchronization may lead to duplicated items or
lost data when the server merges items incorrectly. Choosing
a different synchronization mode may be the better alternative.
Restart synchronization of affected source(s) with one of the
following sync modes to recover from this problem:
slow, refresh-from-server, refresh-from-client
Analyzing the current state:
syncevolution --status horde calendar
Running with one of the three modes:
syncevolution --sync [slow|refresh-from-server|refresh-from-client]
horde calendar
[ERROR] command line execution failure
tobias@telemach:~$ syncevolution --sync refresh-from-client horde calendar
[INFO] todo: inactive
[INFO] memo: inactive
[INFO] addressbook: inactive
[INFO] calendar: starting first time sync from client
Local data changes to be applied remotely during synchronization:
*** calendar ***
Comparison was impossible.
[INFO] calendar: sent 1/1913
[INFO] calendar: sent 2/1913
(... and so forth ...)
[INFO] calendar: sent 408/1913
[INFO] calendar: sent 409/1913
[ERROR] unexpected reply from server; might be a temporary problem, try
again later
[INFO] resend previous message, retry #1
[ERROR] unexpected reply from server; might be a temporary problem, try
again later
[INFO] resend previous message, retry #2
[ERROR] unexpected reply from server; might be a temporary problem, try
again later
[INFO] resend previous message, retry #3
[ERROR] unexpected reply from server; might be a temporary problem, try
again later
[INFO] Transport giving up after 3 retries and 6:04min
[ERROR] transport failed, retry period exceeded
[INFO] calendar: first time sync done unsuccessfully
[ERROR] aborted on behalf of user (local, status 20017)
Synchronization failed, see
/home/tobias/.cache/syncevolution/horde-2011-04-19-18-47/syncevolution-log.html
for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-client, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 1913 before sync, 1913 after it |
| aborted on behalf of user (local, status 20017) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Tue Apr 19 18:47:53 2011, duration 6:54min |
| external transport failure (local, status 20043) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: unexpected reply from server; might be a
temporary problem, try again later
Data modified locally during synchronization:
*** calendar ***
no changes
[ERROR] command line execution failure
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I can't see the server's "unexpected replies", if they are logged
somewhere, I will be happy to provide them here.
Can I tell syncevolution to just send a limited number of entries per
run initially?
Regards, Tobias
--
Tobias Pfaff
Bochum
10:08 p.m.
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.
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
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...
--
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.
11:43 p.m.
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
11:53 p.m.
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.
3602
days inactive
3602
days old
syncevolution@synevolution.org
3 comments
2 participants
participants (2)
-
Patrick Ohly -
Tobias Pfaff