9:46 p.m.
http://bugzilla.moblin.org/show_bug.cgi?id=7655
Summary: Comparison was impossible
Classification: Moblin Projects
Product: SyncEvolution
Version: upstream
Platform: Generic
OS/Version: Other
Status: NEW
Severity: minor
Priority: Undecided
Component: SyncEvolution
AssignedTo: patrick.ohly(a)intel.com
ReportedBy: gassauer(a)kde.org
QAContact: yanshuang.zheng(a)intel.com
CC: shuang.wan(a)intel.com, syncevolution(a)lists.intel.com
SyncEvolution 0.9+0.9.1beta2 on OpenSuSE 11.1 x86_64
KDE 4.3.2 KOrganizer 4.3.2 Rel. 5
these messages are issued (only?) before any changes in the data are made.
Local data changes to be applied to server during synchronization:
*** addressbook ***
Comparison was impossible.
*** calendar ***
Comparison was impossible.
*** memo ***
Comparison was impossible.
*** todo ***
Comparison was impossible.
Synchronization successful.
Changes applied during synchronization:
+---------------|-------ON CLIENT-------|-------ON SERVER-------|-CON-+
| | rejected / total | rejected / total | FLI |
| Source | NEW | MOD | DEL | NEW | MOD | DEL | CTS |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| addressbook | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| two-way, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 907 before sync, 907 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| calendar | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| two-way, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 531 before sync, 531 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| memo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| two-way, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 0 before sync, 0 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| todo | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0/0 | 0 |
| two-way, 0 KB sent by client, 0 KB received |
| item(s) in database backup: 4 before sync, 4 after it |
+---------------+-------+-------+-------+-------+-------+-------+-----+
| start Sat Oct 31 11:31:08 2009, duration 0:13min |
| synchronization completed successfully |
+---------------+-------+-------+-------+-------+-------+-------+-----+
Changes applied to client during synchronization:
*** addressbook ***
no changes
*** calendar ***
no changes
*** memo ***
no changes
*** todo ***
no changes
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
1:27 a.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2009-10-31 07:27:05 ---
(In reply to comment #0)
SyncEvolution 0.9+0.9.1beta2 on OpenSuSE 11.1 x86_64
KDE 4.3.2 KOrganizer 4.3.2 Rel. 5
these messages are issued (only?) before any changes in the data are made.
Local data changes to be applied to server during synchronization:
*** addressbook ***
Comparison was impossible.
*** calendar ***
Comparison was impossible.
*** memo ***
Comparison was impossible.
*** todo ***
Comparison was impossible.
The comparison here depends on a database dump made during the previous sync.
If there is no such database dump available (logdir not set, first sync, old
database dumps deleted, ...), then "Comparison was impossible" is reported.
This is not an error by itself. Because the exact reason why the previous dump
isn't where it is expected is unknown, being more specific in the error message
is impossible. Feel free to suggest a different wording, though.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
4:25 a.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #2 from ferdinand <gassauer(a)kde.org> 2009-11-01 09:25:45 ---
wording
"No previous local database found - comparison not posible"
interstingly this message comeas again and again - are the db dumps removed
occasionally ?
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
5:56 a.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #3 from pohly <patrick.ohly(a)intel.com> 2009-11-01 10:56:12 ---
(In reply to comment #2)
wording
"No previous local database found - comparison not posible"
I'll check whether that fits for all error cases.
interstingly this message comeas again and again - are the db dumps
removed
occasionally ?
Check your "logdir" and "maxlogdirs" settings. "--print-sessions
funambol" will
tell you where the previous database dumps should be.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
7:54 p.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #4 from ferdinand <gassauer(a)kde.org> 2009-11-02 00:54:39 ---
--print-sessions output
/home/myhome/.cache/syncevolution/chricar funambol-2009-11-02-09-50
and see this error
synchronization failed (status code 500)
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
8:23 p.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #5 from ferdinand <gassauer(a)kde.org> 2009-11-02 01:23:48 ---
BTW this error seems to happen always if the command is run from cron, or also
if started manualy after a cron run.
seems that cron is massing up somthing
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
9:10 p.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2009-11-02 02:10:44 ---
(In reply to comment #4)
--print-sessions output
/home/myhome/.cache/syncevolution/chricar funambol-2009-11-02-09-50
"chricar funambol" - really a space in the name? Just wondering.
What is your maxlogdir setting? I would expect more than one directory if you
use the default settings.
(In reply to comment #5)
BTW this error seems to happen always if the command is run from
cron, or also
if started manualy after a cron run.
seems that cron is massing up somthing
Are you perhaps running into this problem:
http://www.estamos.de/blog/2009/05/08/running-syncevolution-as-cron-job/
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
10:05 p.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #7 from ferdinand <gassauer(a)kde.org> 2009-11-02 03:05:43 ---
"chricar funambol" - really a space in the name? Just wondering.
yes - I think used the GUI - but am not sure as this was some 9 month ago
What is your maxlogdir setting? I would expect more than one directory if you
use the default settings
maxlogdir - I see 10 directories.
Are you perhaps running into this problem:
http://www.estamos.de/blog/2009/05/08/running-syncevolution-as-cron-job/
propably - have to check tomorrow
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
9:47 p.m.
New subject: [Bug 7655] Comparison was impossible
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #8 from ferdinand <gassauer(a)kde.org> 2009-11-03 02:47:46 ---
yes
adapting the cronjob command solves the problem
Do you think it's possible to check + error message or better start dbus-launch
directly out of syncevolution to allow a userfrienldy configuration.
I assume people will usually want to run syncevolution as a cronjob.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
10:27 p.m.
New subject: [Bug 7655] running under cron: fails without proper error message
http://bugzilla.moblin.org/show_bug.cgi?id=7655
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |P2
Status|NEW |ASSIGNED
Target Milestone|--- |0.9.1
Summary|Comparison was impossible |running under cron: fails
| |without proper error
| |message
Severity|minor |normal
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2009-11-03 03:27:57 ---
(In reply to comment #8)
Do you think it's possible to check + error message
There should have been the "GConf Error" that was quoted in the blog article. I
need to check why that is not printed by 0.9.x. Perhaps because we redirect
stderr.
or better start dbus-launch
directly out of syncevolution to allow a userfrienldy configuration.
SyncEvolution doesn't get a proper error code and thus cannot detect the
problem. Always launching D-Bus is not right when it isn't needed, which is
also hard to detect reliably (among others, depends on the version of the
external libraries).
I assume people will usually want to run syncevolution as a cronjob.
I don't think it is that common. It is also not reliable right now. Concurrent
modifications to the data in Evolution can be dangerous. We have several issues
open to improve this (bug #6378, bug #3479).
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12:36 a.m.
New subject: [Bug 7655] running under cron: fails without proper error message
http://bugzilla.moblin.org/show_bug.cgi?id=7655
--- Comment #10 from pohly <patrick.ohly(a)intel.com> 2009-11-03 05:36:01 ---
(In reply to comment #9)
(In reply to comment #8)
> Do you think it's possible to check + error message
There should have been the "GConf Error" that was quoted in the blog article.
I
need to check why that is not printed by 0.9.x. Perhaps because we redirect
stderr.
Yes, that's the reason. The problem is that several of the libraries which are
used by SyncEvolution spew out quite a bit of useless (for command line users
of SyncEvolution) noise via stderr. So we capture that and dump it into a log
as "informational" messages, if the log level is high enough. In your case it
probably didn't even get into the logs.
It is possible to disable this by setting SYNCEVOLUTION_DEBUG.
So what do we do about this problem? The only solution that I can think of is
to detect "severe" error reports on stderr and log them with severity ERROR,
which means that they would show up on the normal output.
Detecting "severe" error reports could be done by searching for the word
"error", ignoring its case. As long as the error messages aren't localized
(which doesn't seem to be the case here) this works.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12:46 a.m.
New subject: [Bug 7655] running under cron: fails without proper error message
http://bugzilla.moblin.org/show_bug.cgi?id=7655
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Depends on| |5014
--- Comment #11 from pohly <patrick.ohly(a)intel.com> 2009-11-03 05:46:11 ---
I have a patch pending in the syncevolution-0-9-x branch. To reproduce the
problem, run "syncevolution" without parameters on a system with GNOME >=
2.24
after unsetting DBUS_SESSION_BUS_ADDRESS and DISPLAY.
Because output is not going through the logging code (wishlist bug #5014), the
redirected error messages show up after the output operations which triggered
them. IMHO that's okay for the time being.
--
Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
4702
days inactive
4705
days old
syncevolution-issues@syncevolution.org
11 comments
1 participants
participants (1)
-
bugzilla＠moblin.org