4:47 a.m.
https://bugs.freedesktop.org/show_bug.cgi?id=70771
Priority: medium
Bug ID: 70771
CC: syncevolution-issues(a)syncevolution.org
Assignee: syncevolution-issues(a)syncevolution.org
Summary: Problem with Sync + Network Enabled.
Severity: normal
Classification: Unclassified
OS: Linux (All)
Reporter: eugenio.parodi(a)intel.com
Hardware: x86 (IA32)
Status: NEW
Version: 1.3.99.3
Component: PIM Manager
Product: SyncEvolution
Created attachment 88012
--> https://bugs.freedesktop.org/attachment.cgi?id=88012&action=edit
Logfiles
There is a hostname request in the Logging routine that may slowdown the Sync
if The network is not available or lead to some kind of timeout service.
This is log from sync with network enabled:
[2013-10-17 15:14:48.189] ---- Hardcoded Product name: SySync SyncML
Library OpenSource Linux
[2013-10-17 15:14:48.189] ---- Configured Model/Manufacturer: SyncEvolution
/ Patrick Ohly
[2013-10-17 15:14:58.000] ---- Running on Linux,
URI/deviceID='linux:localhost.localdomain'
[2013-10-17 15:14:58.000] ---- Process ID = 2262, Thread ID = 3034576592
It’s perfect 10 seconds stall after which deviceID is displayed and it’s
contains device network name.
Here is the same fragment from log with network disabled:
[2013-10-18 10:52:54.035] ---- Hardcoded Product name: SySync SyncML
Library OpenSource Linux
[2013-10-18 10:52:54.035] ---- Configured Model/Manufacturer: SyncEvolution
/ Patrick Ohly
[2013-10-18 10:52:54.038] ---- Running on Linux,
URI/deviceID='linux:localhost.localdomain'
[2013-10-18 10:52:54.038] ---- Process ID = 19327, Thread ID = 3034973904
No stall at all (interestingly deviceID is the same as with network enabled).
Also there is second 10 seconds stall shortly after first one when network is
enabled (log is not saying much about this, but I’m thinking that reason is the
same as for the first one):
[2013-10-17 15:14:58.001] Created command 'Status' (outgoing)
–[2013-10-17 15:14:58.001] 'DSStateChange' - Datastore changes state,
datastore=remote, oldstate=idle, newstate=client_initialized [--][++] [->end]
–[2013-10-17 15:14:58.001] End of 'DSStateChange' [->top]
[2013-10-17 15:15:08.000]
[2013-10-17 15:15:08.000] =================> Starting new client session
And again log without network:
[2013-10-18 10:52:54.039] Created command 'Status' (outgoing)
–[2013-10-18 10:52:54.039] 'DSStateChange' - Datastore changes state,
datastore=remote, oldstate=idle, newstate=client_initialized [--][++] [->end]
–[2013-10-18 10:52:54.039] End of 'DSStateChange' [->top]
[2013-10-18 10:52:54.040]
[2013-10-18 10:52:54.040] =================> Starting new client session
Again no stall at all.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.