Hi,
> Probably a known and fixed timing issue with registering on D-Bus. You
> are probably running Debian Testing? Please install 1.3 from
> syncevolution.org, there's an apt repository.
I was not able to use the packages from the apt repository because there
were some blocks in the dependencies. The packages are called
differently in debian ie syncevolution-http for the server. However
compiling syncevolution 1.3.99.2 from source did indeed resolve the
issue.
The phone now reports successful synchronisation of the addressbook
however after a while I am seeing this in the server log:
[DEBUG] sync: /org/syncevolution/Session/7962587831360232313: starting GET,
credentials okay, deadline in 300.0s
[DEBUG] sync: /org/syncevolution/Session/7962587831360232313: starting GET,
credentials okay, deadline in 300.0s
[DEBUG] sync: /org/syncevolution/Session/7962587831360232313: starting GET,
credentials okay, deadline in 300.0s
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: Connection
7962587831360232313: timed out after 300s (state WAITING)
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: Connection
7962587831360232313: failed: timed out after 300s (old state WAITING)
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: Connection
7962587831360232313: send abort to client (state WAITING)
[DEBUG] syncevo-http: connection
/org/syncevolution/Connection/7962587831360232313 went down, active connection
/org/syncevolution/Connection/7962587831360232313
[DEBUG] syncevo-http: destructing connection
/org/syncevolution/Connection/7962587831360232313 with code 500 message lost
connection to SyncEvolution
[ERROR] dbus.connection: Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 230, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/local/bin/syncevo-http-server", line 154, in abort
self.destruct(http.INTERNAL_SERVER_ERROR, "lost connection to
SyncEvolution")
File "/usr/local/bin/syncevo-http-server", line 133, in destruct
self.connection.Close(False, message)
File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in
__call__
**keywords)
File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in
call_blocking
message, timeout)
DBusException: org.syncevolution.InvalidCall: cannot detach from resource that
client is not attached to
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: Connection
7962587831360232313: client :1.0 closes connection
/org/syncevolution/Connection/7962587831360232313 with error: lost connection
to SyncEvolution (old state FAILED)
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: exception thrown at
src/dbus/server/client.cpp:63
[ERROR] syncevo-dbus-server: /org/syncevolution/Server: cannot detach from
resource that client is not attached to
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: Connection
7962587831360232313: done with 'syncevo-server-http.py (HTTP)' unexpectedly:
timed out after 300s (old state FAILED)
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: Connection
7962587831360232313: not sending abort to client, already done (state FAILED)
[DEBUG] syncevo-dbus-server: /org/syncevolution/Server: activating idle
termination in 600 seconds because idle
[DEBUG] sync: /org/syncevolution/Session/7962587831360232313: starting GET,
credentials okay, deadline in 300.0s
This made me wonder whether all my data really has reached the webdav
storage however everything seems to be there.
Now all I have to do is to work up some faith to try two-way sync.
> It also doesn't hurt to file bugs against Debian. It's currently in
> feature freeze, and getting things fixed depends on reporting them.
> Otherwise the current version would be seen as working and stable.
Bug for debian is filed on
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699852
Thank you very much for your great work on syncevolution. This is
awesome!
Regards
Christof
Am Dienstag, 5. Februar 2013, 21:44:00 schrieb Patrick Ohly:
> On Tue, 2013-02-05 at 21:31 +0100, Christof Schulze wrote:
> > Hello,
> > the funambol configuration works now. All I did was to manuall start
> > the synchronisation for a couple of times while limiting the sync to
> > the addressbook and then again limiting it to the calendar.
> > However funambol is a memory hog (separate database, tomcat instance,
> > java application) hence I would like to replace it with something more
> > lightweight.
> > After having received feedback about using syncevo-http-server, I
> > tried to set things up according to https://syncevolution.org/wiki/http-
> > server-howto
> > When I try to synchronize just the addressbook datasource from the
> > phone the phone states that the server Url is invalid and the server
> > prints out the following error:
> > [ERROR] twisted: Unhandled Error
> [...]
> > dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod:
> > No
> > such interface `org.syncevolution.Server' on object at path
> > /org/syncevolution/Server
> [...]
> > [DEBUG] sync: /org/syncevolution/Server: version: 1.2.99.1
> [...]
> > What went wrong?
--
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against proprietary attachments
_______________________________________________
SyncEvolution mailing list
[email protected]
http://lists.syncevolution.org/listinfo/syncevolution
