4:10 a.m.
http://bugs.meego.com/show_bug.cgi?id=4026
Summary: sync fails with error "(timeout by message bus)"
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: Netbook
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: nudelzebra(a)web.de
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
BUILD IMAGE: syncevolution-evolution 1:1.0.1-2 (from repo)
HARDWARE MODEL: samsung nc 10 (x86); ubuntu 10.04;
BUG DETAILED DESCRIPTIONS
===========================================================
syncing fails with built in scheduleworld profile; UI "error 10510"
---
user:~$ syncevolution --sync refresh-from-server sheduleworld
[ERROR] No configuration for server "sheduleworld" found.
[ERROR] cannot proceed without configuration
nuzeb@mobiluzeb:~$ syncevolution --sync refresh-from-server scheduleworld
[INFO] todo: starting first time sync from server
[INFO] addressbook: starting first time sync from server
[INFO] calendar: starting first time sync from server
[INFO] memo: starting first time sync from server
[ERROR] calendar: reading all items: Message did not receive a reply (timeout
by message bus)
[INFO] calendar: first time sync done unsuccessfully
[ERROR] database failure (local, status 10510)
[INFO] addressbook: first time sync done unsuccessfully
[ERROR] database failure (local, status 10510)
[INFO] memo: first time sync done unsuccessfully
[ERROR] database failure (local, status 10510)
[INFO] todo: first time sync done unsuccessfully
[ERROR] database failure (local, status 10510)
Synchronization failed, see
/home/user/.cache/syncevolution/scheduleworld-2010-07-26-19-57/syncevolution-log.html
for details.
Changes applied during synchronization:
+---------------|-----------------------|-----------------------|-CON-+
| | LOCAL | REMOTE | FLI |
| Source | NEW | MOD | DEL | ERR | NEW | MOD | DEL | ERR | CTS |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| addressbook | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-server, 0 KB sent by client, 0 KB received |
| database failure (local, status 10510) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| calendar | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-server, 0 KB sent by client, 0 KB received |
| database failure (local, status 10510) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| memo | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-server, 0 KB sent by client, 0 KB received |
| database failure (local, status 10510) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| todo | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
| refresh-from-server, 0 KB sent by client, 0 KB received |
| database failure (local, status 10510) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
| start Mon Jul 26 19:57:50 2010, duration 0:02min |
| database failure (local, status 10510) |
+---------------+-----+-----+-----+-----+-----+-----+-----+-----+-----+
First ERROR encountered: calendar: reading all items: Message did not receive a
reply (timeout by message bus)
[ERROR] command line execution failure
user:~$
REPRODUCIBILITY:
=====================================
always
OTHER COMMENTS:
===================
syncing on my desktop with same software versions (except it's a 64bit ubuntu
10.04) does work fine
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
4:48 a.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrick.ohly(a)intel.com,
| |ross(a)linux.intel.com
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2010-07-27 11:48:30 PDT ---
(In reply to comment #0)
BUILD IMAGE: syncevolution-evolution 1:1.0.1-2 (from repo)
HARDWARE MODEL: samsung nc 10 (x86); ubuntu 10.04;
[...]
[ERROR] calendar: reading all items: Message did not receive a reply
(timeout
by message bus)
That's the root cause. Access to Evolution Database Server via libecal fails.
This looks like a timing issue, perhaps related to the fact that this hardware
is less powerful than your desktop. Sorry, there's nothing that SyncEvolution
can do about this, this needs to be fixed inside libecal.
Ross, do you have an idea what might be causing this and how to fix it?
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
3:37 a.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2010-08-10 10:37:18 PDT ---
(In reply to comment #1)
(In reply to comment #0)
> BUILD IMAGE: syncevolution-evolution 1:1.0.1-2 (from repo)
> HARDWARE MODEL: samsung nc 10 (x86); ubuntu 10.04;
[...]
> [ERROR] calendar: reading all items: Message did not receive a reply (timeout
> by message bus)
That's the root cause. Access to Evolution Database Server via libecal fails.
This looks like a timing issue, perhaps related to the fact that this hardware
is less powerful than your desktop. Sorry, there's nothing that SyncEvolution
can do about this, this needs to be fixed inside libecal.
Ross, do you have an idea what might be causing this and how to fix it?
From private discussion I gathered that the asynchronous API currently
provided
libecal and used in SyncEvolution has design issues which prevent fixing
the
problem.
A new asynchronous API is planned, but not available yet.
I might resurrect the Maemo hack of increasing the default D-Bus timeout, but I
am not sure whether that is still possible or would help.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
9:48 p.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |High
Status|NEW |NEEDINFO
AssignedTo|syncevolution-bugs(a)meego.bu |jingke.zhang(a)intel.com
|gs |
Target Milestone|--- |1.1
Architecture|--- |ALL
--- Comment #3 from pohly <patrick.ohly(a)intel.com> 2010-08-24 04:48:27 PDT ---
Jingke, can you reproduce the issue in MeeGo? I suppose all that it takes is
creating lots of calendar events. Running a CPU intensive task while doing the
sync may also help to trigger this.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.
2:19 a.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |FIXED
--- Comment #4 from pohly <patrick.ohly(a)intel.com> 2010-09-03 09:19:57 PDT ---
It doesn't seem like this problem is going to be addressed in libecal and
libebook. Therefore I've resurrected the Maemo EDS-DBus hack (details below). I
have not bother about reproducing the problem first, although it probably
should be possible. nuzeb, if you are interested, then I can make experimental
builds of SyncEvolution available soon.
commit 9286d914c064f5e3966fee149224eeb78a7123c8
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Fri Sep 3 15:40:05 2010 +0200
EDS: workaround for D-Bus method timeouts (BMC #4026)
libecal/ebook implementation based on D-Bus (Evolution >= 2.30)
inevitably will run into D-Bus timeouts as the amount of data
increases.
This patch moves an earlier hack written for Maemo into the core
code and enables it by default, if the EDS backends are active.
It works by intercepting dbus_connection_send_with_reply()
and substituting timeout_milliseconds==-1 ("default timeout
of 25 seconds") with timeout_milliseconds=INT_MAX ("no timeout").
Setting SYNCEVOLUTION_DBUS_TIMEOUT to number of milliseconds
allows controlling the final timeout value.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
3:04 a.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
--- Comment #5 from nuzeb <nudelzebra(a)web.de> 2010-09-03 10:04:08 PDT ---
Yes, pohly. I would be very interested in testing your experimental build and
provide you with feedback.
(In reply to comment #4)
It doesn't seem like this problem is going to be addressed in
libecal and
libebook. Therefore I've resurrected the Maemo EDS-DBus hack (details below). I
have not bother about reproducing the problem first, although it probably
should be possible. nuzeb, if you are interested, then I can make experimental
builds of SyncEvolution available soon.
commit 9286d914c064f5e3966fee149224eeb78a7123c8
Author: Patrick Ohly <patrick.ohly(a)intel.com>
Date: Fri Sep 3 15:40:05 2010 +0200
EDS: workaround for D-Bus method timeouts (BMC #4026)
libecal/ebook implementation based on D-Bus (Evolution >= 2.30)
inevitably will run into D-Bus timeouts as the amount of data
increases.
This patch moves an earlier hack written for Maemo into the core
code and enables it by default, if the EDS backends are active.
It works by intercepting dbus_connection_send_with_reply()
and substituting timeout_milliseconds==-1 ("default timeout
of 25 seconds") with timeout_milliseconds=INT_MAX ("no timeout").
Setting SYNCEVOLUTION_DBUS_TIMEOUT to number of milliseconds
allows controlling the final timeout value.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
7:45 p.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RELEASED |REOPENED
Resolution|FIXED |
--- Comment #6 from pohly <patrick.ohly(a)intel.com> 2010-09-13 02:45:09 PDT ---
According to nuzeb on the SyncEvolution mailing list, this problem still
occurs.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
5:07 a.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |WAITING FOR UPSTREAM
--- Comment #7 from pohly <patrick.ohly(a)intel.com> 2010-09-13 12:07:08 PDT ---
(In reply to comment #6)
According to nuzeb on the SyncEvolution mailing list, this problem
still
occurs.
... and according to his log files, it is not a real timeout. Instead the
e-calendar-factory process seems to die shortly after getting the request to
list all calendar events.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
12:42 a.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING FOR UPSTREAM |NEEDINFO
--- Comment #8 from pohly <patrick.ohly(a)intel.com> 2010-09-14 07:42:20 PDT ---
Some more information based on information provided by nuzeb:
From: Patrick Ohly <patrick.ohly(a)intel.com>
Reply-to: patrick.ohly(a)intel.com
To: Nudelzebra <nudelzebra(a)web.de>
Cc: SyncEvolution <syncevolution(a)syncevolution.org>
Subject: sync fails with error "(timeout by message bus)" (MBC #4026 was
Re: [SyncEvolution] SyncEvolution 1.1 pre-release)
Date: Mon, 13 Sep 2010 14:19:41 +0200
On Fri, 2010-09-10 at 19:47 +0100, Patrick Ohly wrote:
On Fri, 2010-09-10 at 17:40 +0100, Nudelzebra wrote:
> Hi.
>
> I just tried the builds (deb) and unfortunately got the same error
> (10510) as before.
Please run "dbus-monitor >/tmp/dbus.log &" and "dbus-monitor
--profile
>/tmp/profile.log" before starting syncevolution, then send me the
files. I'd like to check what the timeouts are.
Thanks for the logs. They show that the EDS calendar server dies
(combination of monitor and profile log):
mc 1284371457 118043 73 :1.129
/org/gnome/evolution/dataserver/calendar/1671/8
org.gnome.evolution.dataserver.calendar.Cal getObjectList
method call sender=:1.129 -> dest=:1.38 serial=73
path=/org/gnome/evolution/dataserver/calendar/1671/8;
interface=org.gnome.evolution.dataserver.calendar.Cal; member=getObjectList
string "#t"
sig 1284371457 136208 5 /org/freedesktop/DBus
org.freedesktop.DBus NameOwnerChanged
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=5
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameOwnerChanged
string "org.gnome.evolution.dataserver.Calendar"
string ":1.38"
string ""
sig 1284371457 144230 16 /org/freedesktop/DBus
org.freedesktop.DBus NameOwnerChanged
signal sender=org.freedesktop.DBus -> dest=(null destination) serial=16
path=/org/freedesktop/DBus; interface=org.freedesktop.DBus;
member=NameOwnerChanged
string ":1.38"
string ":1.38"
string ""
What this probably means is that 136208 - 118043 = 18ms after receiving
the getObjectList() method call, the e-calendar-factory process
disconnects from D-Bus. It probably crashed.
That libecal turns this error into a "Message did not receive a reply
(timeout by message bus)" error has been extremely helpful :-( Not!
Can you verify this by stopping Evolution completely (exit GUI,
evolution --force-shutdown), then running e-calendar-factory under gdb
(usually installed in /usr/libexec, check with ps while Evolution runs)?
--------------------------------------------------------------------------
It turned out that e-calendar-factory did not crash; it simply leaves main()
with a return code of 1:
[New Thread 0xb612db70 (LWP 2068)]
Server is up and running...
[Thread 0xb612db70 (LWP 2068) exited]
Program exited with code 01.
....
With a break point in exit():
(gdb) thread apply all bt
Thread 2 (Thread 0xb612db70 (LWP 2087)):
#0 0xb7fe1416 in __kernel_vsyscall ()
#1 0xb7eebde6 in __poll (fds=0xb7f83ff4, nfds=1, timeout=-1)
at ../sysdeps/unix/sysv/linux/poll.c:87
#2 0xb7bc025b in g_poll () from /lib/libglib-2.0.so.0
#3 0xb7bb2bfc in ?? () from /lib/libglib-2.0.so.0
#4 0xb7bb3367 in g_main_loop_run () from /lib/libglib-2.0.so.0
#5 0xb7a7ca64 in ?? () from /usr/lib/libgio-2.0.so.0
#6 0xb7bd9eef in ?? () from /lib/libglib-2.0.so.0
#7 0xb7f8dcc9 in start_thread (arg=0xb612db70) at pthread_create.c:304
#8 0xb7efa6ae in clone ()
at ../sysdeps/unix/sysv/linux/i386/clone.S:130
Thread 1 (Thread 0xb7584720 (LWP 2084)):
#0 exit (status=0) at exit.c:100
#1 0xb7e40cef in __libc_start_main (main=0x804b030, argc=1,
ubp_av=0xbffff434, init=0x804ba80, fini=0x804ba70,
rtld_fini=0xb7ff0b80 <_dl_fini>, stack_end=0xbffff42c) at
libc-start.c:258
#2 0x08049ff1 in ?? ()
No idea what this means. I'll ask the EDS developers.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
6:48 p.m.
New subject: [Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
--- Comment #9 from pohly <patrick.ohly(a)intel.com> 2010-09-16 01:48:17 PDT ---
(In reply to comment #8)
No idea what this means. I'll ask the EDS developers.
We've discussed it on IRC, with no further hints what this could be.
nuzeb, can you run some more tests?
Start under gdb as before, but then also set breakpoints in g_main_loop_run and
g_main_loop_quit in addition to exit. Make sure you have libglib1.2-dbg and
evolution-data-server-dbg installed.
Use
thread apply all bt
cont
each time you get a gdb prompt.
My theory is that the daemon shuts down while it is still in use. The stack
back trace of g_main_loop_quit() might confirm that.
Another theory is that it is related to the content of the calendar. What
calendars do you have? "syncevolution" without parameters will show that.
Does it occur after removing the calendar.ics file mentioned in that output?
You are doing a "refresh-from-server", so I assume that you can safely wipe out
that data.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
6:39 a.m.
New subject: [MeeGo Projects - Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |WAITING FOR UPSTREAM
--- Comment #10 from pohly <patrick.ohly(a)intel.com> 2010-09-24 13:39:46 PDT ---
Got a reply via private email.
(In reply to comment #9)
(In reply to comment #8)
> No idea what this means. I'll ask the EDS developers.
We've discussed it on IRC, with no further hints what this could be.
nuzeb, can you run some more tests?
Start under gdb as before, but then also set breakpoints in g_main_loop_run and
g_main_loop_quit in addition to exit.
That turned out to be futile because all synchronous D-Bus calls use these two
functions.
Another theory is that it is related to the content of the calendar.
What
calendars do you have?
Standard local file backend.
Does it occur after removing the calendar.ics file mentioned in that
output?
Yes.
So the EDS setup is simply borked, independent of the actual data in it. I have
no further idea for investigating this via gdb.
All I can suggest is that you try different Evolution versions and/or contact
the Evolution developers.
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
7:38 p.m.
New subject: [MeeGo Projects - Bug 4026] sync fails with error "(timeout by message bus)"
http://bugs.meego.com/show_bug.cgi?id=4026
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING FOR UPSTREAM |RESOLVED
Resolution| |WORKSFORME
--
Configure bugmail: http://bugs.meego.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching someone on the CC list of the bug.
4351
days inactive
4437
days old
syncevolution-issues@syncevolution.org
11 comments
1 participants
participants (1)
-
bugzilla＠meego.com