[Bug 6369] New: Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
3:10 a.m.
http://bugs.meego.com/show_bug.cgi?id=6369
Summary: Error reporting in HTTP server is sucky (Or: HTTP
server ignores LogOutput dbus signals)
Classification: MeeGo Projects
Product: SyncEvolution
Version: unspecified
Platform: All
Architecture: ---
Status: NEW
Severity: normal
Priority: Undecided
Component: SyncEvolution
AssignedTo: syncevolution-bugs(a)meego.bugs
ReportedBy: matthijs(a)stdin.nl
QAContact: jingke.zhang(a)intel.com
CC: syncevolution-bugs(a)meego.bugs,
syncevolution-default-bugs(a)meego.bugs
Estimated Hours: 0.0
I've been trying to get the HTTP server running, but I got the following output
after connecting with a client.
matthijs@login:~$ syncevo-http-server http://localhost:9000/sync
POST from 178.226.74.128 config type application/vnd.syncml+wbxml session None
args {} length 1795
requesting new session
SessionChanged: /org/syncevolution/Session/7414306401283853336 1
connection /org/syncevolution/Connection/7414306401283853336 went down
ERROR:dbus.connection:Exception in handler for D-Bus signal:
Traceback (most recent call last):
File "/var/lib/python-support/python2.5/dbus/connection.py", line 214, in
maybe_handle_message
self._handler(*args, **kwargs)
File "/usr/bin/syncevo-http-server", line 68, in abort
self.destruct(http.INTERNAL_SERVER_ERROR, "lost connection to
SyncEvolution")
File "/usr/bin/syncevo-http-server", line 60, in destruct
self.connection.Close(False, message)
File "/var/lib/python-support/python2.5/dbus/proxies.py", line 140, in
__call__
**keywords)
File "/var/lib/python-support/python2.5/dbus/connection.py", line 607, in
call_blocking
message, timeout)
DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method "Close" with
signature "bs" on interface "org.syncevolution.Connection" doesn't
exist
This seems like there is something wrong with the dbus interface specs or
something. However, it turns out there is a really simple configuration
problem. Running dbus-monitor shows the real error (the first two signals are
relevant).
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=LogOutput
object path "/org/syncevolution/Session/7414306401283853336"
string "SHOW"
string "First ERROR encountered: no sources active, check configuration"
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=LogOutput
object path "/org/syncevolution/Session/7414306401283853336"
string "SHOW"
string "
"
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=LogOutput
object path "/org/syncevolution/Session/7414306401283853336"
string "DEBUG"
string "done with connection to 'syncevo-server-http.py (HTTP)'
unexpectedly"
signal sender=:1.46 -> dest=(null destination)
path=/org/syncevolution/Connection/7414306401283853336;
interface=org.syncevolution.Connection; member=Abort
signal sender=:1.46 -> dest=(null destination)
path=/org/syncevolution/Session/7414306401283853336;
interface=org.syncevolution.Session; member=StatusChanged
string "done"
uint32 10500
array [
dict entry(
string "addressbook"
struct {
string "none"
string "idle"
uint32 0
}
)
dict entry(
string "calendar"
struct {
string "none"
string "idle"
uint32 0
}
)
dict entry(
string "memo"
struct {
string "none"
string "idle"
uint32 0
}
)
dict entry(
string "todo"
struct {
string "none"
string "idle"
uint32 0
}
)
]
signal sender=:1.46 -> dest=(null destination) path=/org/syncevolution/Server;
interface=org.syncevolution.Server; member=SessionChanged
object path "/org/syncevolution/Session/7414306401283853336"
boolean false
method call sender=:1.51 -> dest=:1.46
path=/org/syncevolution/Connection/7414306401283853336;
interface=org.syncevolution.Connection; member=Close
boolean false
string "lost connection to SyncEvolution"
error sender=:1.46 -> dest=:1.51
error_name=org.freedesktop.DBus.Error.UnknownMethod reply_serial=17
string "Method "Close" with signature "bs" on interface
"org.syncevolution.Connection" doesn't exist
It seems like the dbus server uses signals to return log lines, but the http
server does not seem to show them, making them lost in the void. This makes
setting up the HTTP server a bit of challenge :-)
--
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:33 a.m.
New subject: [Bug 6369] Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
http://bugs.meego.com/show_bug.cgi?id=6369
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|Undecided |High
Status|NEW |ASSIGNED
CC| |patrick.ohly(a)intel.com
Severity|normal |major
--- Comment #1 from pohly <patrick.ohly(a)intel.com> 2010-09-07 04:33:55 PDT ---
(In reply to comment #0)
I've been trying to get the HTTP server running, but I got the
following output
after connecting with a client.
matthijs@login:~$ syncevo-http-server http://localhost:9000/sync
POST from 178.226.74.128 config type application/vnd.syncml+wbxml session None
args {} length 1795
requesting new session
SessionChanged: /org/syncevolution/Session/7414306401283853336 1
connection /org/syncevolution/Connection/7414306401283853336 went down
ERROR:dbus.connection:Exception in handler for D-Bus signal:
[...]
DBusException: org.freedesktop.DBus.Error.UnknownMethod: Method
"Close" with
signature "bs" on interface "org.syncevolution.Connection"
doesn't exist
I suspect that the syncevo-http-server does not need to call "Close" here, but
it probably isn't smart enough to know that and always tries. If it wasn't
necessary, then the only negative effect is this error message here.
This seems like there is something wrong with the dbus interface
specs or
something. However, it turns out there is a really simple configuration
problem. Running dbus-monitor shows the real error (the first two signals are
relevant).
As you probably noticed, the syncevo-http-server is not particularly
user-friendly. It started its life as a debugging utility and later got
packaged because users started to find it useful.
Right now, the expectation is that the syncevo-dbus-server is started manually
and that its output is used to diagnose issues. The HOWTO implicitly describes
that in the part about setting up client configs in the server, which depends
on detecting the device ID of new clients (see also bug #1360).
The LogOutput feature was added later. I agree, syncevo-dbus-server should
print these messages.
It also should avoid the unnecessary Close method and probably be less verbose.
Patches welcome, as always :-/ Anything assigned to
syncevolution-bugs(a)meego.bugs is not currently being worked on.
--
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:38 a.m.
New subject: [Bug 6369] Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
http://bugs.meego.com/show_bug.cgi?id=6369
--- Comment #2 from matthijs <matthijs(a)stdin.nl> 2010-09-07 04:38:43 PDT ---
(In reply to comment #1)
The LogOutput feature was added later. I agree, syncevo-dbus-server
should
print these messages.
I assume you mean syncevo-http-server here?
--
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:45 p.m.
New subject: [MeeGo Projects - Bug 6369] Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
http://bugs.meego.com/show_bug.cgi?id=6369
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |NEEDINFO
--- Comment #3 from pohly <patrick.ohly(a)intel.com> 2010-12-27 13:45:05 PST ---
I'm improving syncevo-http-server output. syncevo-http-server output for the
case where a client connects which has no config yet:
[INFO] sync: ./syncevo-dbus-server: ready to run
[INFO] syncevo-http: new SyncML session for 127.0.0.1
[ERROR] sync: no configuration found for deviceID foobar
How was the "no sources active, check configuration" error triggered? I'd
like
to ensure that it is logged properly and that the excessive close() call is
avoided, but my first naive approach (ask for unknown URI) did not lead to the
error.
Instead I got in the client:
[INFO] vcard30: server database not found, check URI 'foobar'
The server later times out, which did trigger the excessive close() call (error
for that now suppressed).
--
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:36 p.m.
New subject: [MeeGo Projects - Bug 6369] Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
http://bugs.meego.com/show_bug.cgi?id=6369
--- Comment #4 from matthijs <matthijs(a)stdin.nl> 2010-12-27 14:36:38 PST ---
I think I got that error by creating a new peer without specifying any sources
to make active. In other words, I had sync = disabled in
~/.config/syncevolution/default/peers/<peername>/sources/*/config.ini
At least I think I did, I haven't actually tried to trigger the error again.
Let me know if this doesn't work, then I'll try a little harder.
--
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.
1:31 a.m.
New subject: [MeeGo Projects - Bug 6369] Error reporting in HTTP server is sucky (Or: HTTP server ignores LogOutput dbus signals)
http://bugs.meego.com/show_bug.cgi?id=6369
pohly <patrick.ohly(a)intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |RESOLVED
Resolution| |FIXED
--- Comment #5 from pohly <patrick.ohly(a)intel.com> 2010-12-28 00:31:25 PST ---
(In reply to comment #4)
I think I got that error by creating a new peer without specifying
any sources
to make active. In other words, I had sync = disabled in
~/.config/syncevolution/default/peers/<peername>/sources/*/config.ini
When I try that, I get the same error in the client as for an invalid URI:
[INFO] vcard30: server database not found, check URI 'addressbook'
At least I think I did, I haven't actually tried to trigger the
error again.
Let me know if this doesn't work, then I'll try a little harder.
Perhaps the code has changed. Never mind, I think we can consider this issue
resolved. Some testing and confirmation once I am done with revamping the
syncevo-http-server would be nice.
--
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.
3997
days inactive
4109
days old
syncevolution-issues@syncevolution.org
5 comments
1 participants
participants (1)
-
bugzilla＠meego.com