Bug 27554

Summary:	telepathy-butterfly crashed with gaierror in query()
Product:	papyon	Reporter:	Sebastien Bacher <seb128>
Component:	general	Assignee:	Telepathy bugs list <telepathy-bugs>
Status:	RESOLVED FIXED	QA Contact:	Telepathy bugs list <telepathy-bugs>
Severity:	normal
Priority:	medium	Keywords:	patch
Version:	unspecified
Hardware:	Other
OS:	All
URL:	http://git.collabora.co.uk/?p=user/jonny/papyon.git;a=shortlog;h=refs/heads/conn
Whiteboard:	review+
i915 platform:		i915 features:

Description Sebastien Bacher 2010-04-09 06:26:04 UTC

The bug has been opened on https://bugs.launchpad.net/ubuntu/+source/telepathy-butterfly/+bug/467217 and has quite some duplicates:

The descriptions don't seem to be really useful, it seems to just show at random time when doing other things


Stracktrace on 0.5.7

"Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/papyon/service/SOAPService.py", line 215, in _response_handler
    handler(callback, errback, response, user_data)
  File "/usr/lib/pymodules/python2.6/papyon/service/SingleSignOn.py", line 198, in _HandleRequestMultipleSecurityTokensResponse
    callback[0](result, *callback[1:])
  File "/usr/lib/pymodules/python2.6/papyon/service/SingleSignOn.py", line 104, in sso_callback
    func(object, user_callback, user_errback, *user_args, **user_kwargs)
  File "/usr/lib/pymodules/python2.6/papyon/service/AddressBook/ab.py", line 353, in __soap_request
    self._soap_request(method, (scenario, token), args, callback, errback)
  File "/usr/lib/pymodules/python2.6/papyon/service/SOAPService.py", line 196, in _soap_request
    user_data)
  File "/usr/lib/pymodules/python2.6/papyon/service/SOAPService.py", line 183, in _send_request
    transport.request(resource, http_headers, request, 'POST')
  File "/usr/lib/pymodules/python2.6/papyon/gnet/protocol/HTTP.py", line 154, in request
    self._process_queue()
  File "/usr/lib/pymodules/python2.6/papyon/gnet/protocol/HTTP.py", line 131, in _process_queue
    self._setup_transport()
  File "/usr/lib/pymodules/python2.6/papyon/gnet/protocol/HTTP.py", line 84, in _setup_transport
    self._transport.open()
  File "/usr/lib/pymodules/python2.6/papyon/gnet/io/iochannel.py", line 141, in open
    self._open(self._host, self._port)
  File "/usr/lib/pymodules/python2.6/papyon/gnet/io/iochannel.py", line 90, in _open
    resolver.query(host, (self.__open, host, port))
  File "/usr/lib/pymodules/python2.6/papyon/gnet/resolver.py", line 58, in query
    result = socket.getaddrinfo(host, None, socket.AF_INET, socket.SOCK_STREAM)
gaierror: [Errno -5] No address associated with hostname"

Other stacktrace example:
http://launchpadlibrarian.net/43373915/Traceback.txt
http://launchpadlibrarian.net/38568384/Traceback.txt

Comment 1 Jonny Lamb 2010-04-09 06:46:38 UTC

This error just looks like internet connectivity was lost. Perhaps we should be nicer about it though. I don't really understand why this code path yet though.

Comment 2 Jonny Lamb 2010-04-12 07:28:16 UTC

I came across a similar traceback recently:

Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.6/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/lib/python2.6/dist-packages/butterfly/connection.py", line 161, in Connect
    self._msn_client.login(*self._account)
  File "/usr/lib/pymodules/python2.6/papyon/client.py", line 256, in login
    self._transport.establish_connection()
  File "/usr/lib/pymodules/python2.6/papyon/transport.py", line 253, in establish_connection
    self._transport.open()
  File "/usr/lib/pymodules/python2.6/papyon/gnet/io/iochannel.py", line 141, in open
    self._open(self._host, self._port)
  File "/usr/lib/pymodules/python2.6/papyon/gnet/io/iochannel.py", line 90, in _open
    resolver.query(host, (self.__open, host, port))
  File "/usr/lib/pymodules/python2.6/papyon/gnet/resolver.py", line 58, in query
    result = socket.getaddrinfo(host, None, socket.AF_INET, socket.SOCK_STREAM)
gaierror: [Errno -5] No address associated with hostname

I wrote a patch for butterfly to catch this exception and signal a network error[0], but actually I think this is a papyon bug and if it's fixed in papyon in both of these cases then it'll magically fix both bugs.

0. http://git.collabora.co.uk/?p=user/jonny/telepathy-butterfly.git;a=commitdiff;h=9e870de38

Comment 3 Jonny Lamb 2010-04-12 08:27:41 UTC

Right, I've fixed this in my conn branch -- a pretty simple patch.

An easy test for this is to run butterfly with this papyon branch and change the server parameter to something that clearly won't work.

Note that butterfly now defaults to trying a HTTP connection when direct doesn't work, so it will actually connect, but observe that butterfly outputs in its log that the direct connection failed and it's trying HTTP now.

Get reviewin'!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.