3:09 a.m.
https://bugs.freedesktop.org/show_bug.cgi?id=57004
Priority: highest
Bug ID: 57004
CC: syncevolution-issues(a)syncevolution.org
Assignee: patrick.ohly(a)intel.com
Summary: preventing slow syncs must not cause slow syncs
Severity: normal
Classification: Unclassified
OS: All
Reporter: patrick.ohly(a)gmx.de
Hardware: Other
Status: ASSIGNED
Version: unspecified
Component: SyncML
Product: SyncEvolution
When one source in a sync with multiple sources encounters a slow sync and thus
aborts the sync, the other sources must not be affected. What happens instead
is that they are forced into a slow sync in the next sync.
Steps to reproduce:
syncevolution --configure preventslowsync=1 memotoo_1
syncevolution memotoo_1 eds_contact eds_event
cp -a ~/.config/syncevolution/ ~/.config/syncevolution_old
syncevolution memotoo_1 eds_contact
rm -rf ~/.config/syncevolution
mv ~/.config/syncevolution_old ~/.config/syncevolution
syncevolution memotoo_1 eds_contact
=> prevents slow sync due to wrong anchors on client, as expected
syncevolution memotoo_1 eds_event
=> works
syncevolution memotoo_1 eds_event eds_contact
=> prevents slow sync for eds_contact
syncevolution memotoo_1 eds_event
=> should have worked, but now also encounters slow sync
--
You are receiving this mail because:
You are on the CC list for the bug.
3:11 a.m.
New subject: [Bug 57004] preventing slow syncs must not cause slow syncs
https://bugs.freedesktop.org/show_bug.cgi?id=57004
--- Comment #1 from Patrick Ohly <patrick.ohly(a)gmx.de> ---
/home/nightly/.cache/syncevolution/memotoo__1@client_+test_+memotoo_+1-2012-11-12-02-43-a
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| eds_event | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| two-way, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 1 before sync, 1 after it |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Mon Nov 12 02:43:53 2012, duration 0:02min |
| synchronization completed successfully |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
/home/nightly/.cache/syncevolution/memotoo__1@client_+test_+memotoo_+1-2012-11-12-02-44
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| eds_contact | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| slow, 0 KB sent by client, 0 KB received |
| unexpected slow sync (local, status 22000) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| eds_event | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| two-way, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 1 before sync, 1 after it |
| aborted on behalf of user (local, status 20017) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Mon Nov 12 02:44:01 2012, duration 0:02min |
| aborted on behalf of user (local, status 20017) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: unexpected slow sync (local, status 22000)
/home/nightly/.cache/syncevolution/memotoo__1@client_+test_+memotoo_+1-2012-11-12-02-44-a
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| eds_event | 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 Mon Nov 12 02:44:10 2012, duration 0:01min |
| unexpected slow sync (local, status 22000) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: unexpected slow sync (local, status 22000)
--
You are receiving this mail because:
You are on the CC list for the bug.
4:01 a.m.
New subject: [Bug 57004] preventing slow syncs must not cause slow syncs
https://bugs.freedesktop.org/show_bug.cgi?id=57004
--- Comment #2 from Patrick Ohly <patrick.ohly(a)gmx.de> ---
The problem here, with Memotoo, was on the server side.
The client correctly aborts the session 2012-11-12-02-44 and in the
2012-11-12-02-44-a session sends (almost) the same Alert as before.
First session:
* [2012-11-12 02:44:01.869] (Saved) Last Local Client
Anchor='20121112T024353Z', (generated) Next Local
Client Anchor='20121112T024401Z' (sent to server as
<last>/<next> in
<alert>)
* [2012-11-12 02:44:01.869] Created command 'Alert' (outgoing)
* [2012-11-12 02:44:01.869] eds_event: ALERTING server for normal Sync
Second session:
* [2012-11-12 02:44:10.840] (Saved) Last Local Client
Anchor='20121112T024353Z', (generated) Next Local
Client Anchor='20121112T024410Z' (sent to server as
<last>/<next> in
<alert>)
* [2012-11-12 02:44:10.840] Alerting resume of last sync session (original
alert code = 200)
* [2012-11-12 02:44:10.840] Created command 'Alert' (outgoing)
* [2012-11-12 02:44:10.840] eds_event: ALERTING server for RESUMED normal
Sync
Note that the anchor hasn't changed. What has changed is that the client
considers this resuming the aborted normal two-way sync (<Data>225</Data> in
the Alert).
The server then rejects that mode and forces a slow sync:
[2012-11-12 02:44:11.937] Alerted (code=201) for Resumed two-way Slow Sync
Either the server doesn't support resuming a sync, or it did not handle the
suspending of the aborted session correctly.
On a related note, the "eds_event" gets prepared (including pre and post data
dumps) completely in the sync where "eds_contact" causes the sync to be
aborted.
I'm not sure how to handle this. Several options exist:
- avoid the "resume normal sync" in favor of doing a regular "normal
sync"
if the sync gets aborted early;
not sure whether this is possible here, because the local store was
initialized and may have changed state
- continue the sync with just the stores which are in an okay state;
I suspect that SyncML is not prepared to handle this, and even if it is,
servers probably were never used and thus tested for this
- only sync one source at a time at the SyncML level
I think the right solution is the third one. It makes each SyncML session a lot
easier. The downside is that some servers might impose a limit on the number of
sessions. Not combining multiple sources into a single session increases the
number of required sessions.
--
You are receiving this mail because:
You are on the CC list for the bug.
4:01 a.m.
New subject: [Bug 57004] preventing slow syncs must not cause slow syncs
https://bugs.freedesktop.org/show_bug.cgi?id=57004
--- Comment #3 from Patrick Ohly <patrick.ohly(a)gmx.de> ---
The original report was for Funambol. When I tried to test with Funambol today,
I couldn't connect and thus tested with Memotoo instead.
--
You are receiving this mail because:
You are on the CC list for the bug.
10:34 a.m.
New subject: [Bug 57004] preventing slow syncs must not cause slow syncs
https://bugs.freedesktop.org/show_bug.cgi?id=57004
Patrick Ohly <patrick.ohly(a)gmx.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|patrick.ohly(a)intel.com |syncevolution-issues@syncev
| |olution.org
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
7:37 a.m.
New subject: [Bug 57004] preventing slow syncs must not cause slow syncs
https://bugs.freedesktop.org/show_bug.cgi?id=57004
GitLab Migration User <gitlab-migration(a)fdo.invalid> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution|--- |MOVED
--- Comment #4 from GitLab Migration User <gitlab-migration(a)fdo.invalid> ---
-- GitLab Migration Automatic Message --
This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.
You can subscribe and participate further through the new bug through this link
to our GitLab instance:
https://gitlab.freedesktop.org/SyncEvolution/libsynthesis/issues/4.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
838
days inactive
2999
days old
syncevolution-issues@syncevolution.org
5 comments
1 participants
participants (1)
-
bugzilla-daemon＠freedesktop.org