Your message dated Fri, 6 Aug 2010 01:40:14 -0400
with message-id <[email protected]>
and subject line Re: [Pkg-telepathy-maintainers] Bug#577726: telepathy-gabble:
can not connect
has caused the Debian Bug report #577726,
regarding telepathy-gabble: can not connect
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
577726: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=577726
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: telepathy-gabble
Version: 0.9.8-1
Severity: normal
Hello.
Since some weeks one account can not connect anymore. When I noticed the
problem the sever (jabber.rwth-aachen.de) had some problems. But now the
server is working and gajim as client can connect without any problems.
Following the debug documentation I did "GABBLE_PERSIST=1 GABBLE_DEBUG=all
WOCKY_DEBUG=xmpp LM_DEBUG=net /usr/lib/telepathy/telepathy-gabble 2>&1 | tee
gabble.log" and I found following lines in it:
(telepathy-gabble:3449): wocky-DEBUG: _error: wocky-xmpp-reader.c:552: Parsing
failed StartTag: invalid element name
(telepathy-gabble:3449): wocky-DEBUG: wocky_xmpp_writer_write_stanza:
Serializing stanza:
* iq xmlns='jabber:client' type='get' to='jabber.rwth-aachen.de'
id='100368764243'
* query xmlns='jabber:iq:auth'
* username
"dirk.meul"
(telepathy-gabble:3449): gabble-DEBUG: connector_error_disconnect: connection
failed: Jabber Auth Fields: Connection has been closed for reading stanzas
Thanks in advance,
Dirk
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.33.2-ck1 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages telepathy-gabble depends on:
ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.2.24-1 simple interprocess messaging syst
ii libdbus-glib-1-2 0.86-1 simple interprocess messaging syst
ii libglib2.0-0 2.24.0-1 The GLib library of C routines
ii libgnutls26 2.8.6-1 the GNU TLS library - runtime libr
ii libsoup2.4-1 2.30.0-1 an HTTP library implementation in
ii libtelepathy-glib0 0.11.2-1 Telepathy framework - GLib library
ii libuuid1 2.16.2-0 Universally Unique ID library
ii libxml2 2.7.7.dfsg-1 GNOME XML library
telepathy-gabble recommends no packages.
telepathy-gabble suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi.
On Wed, Apr 14, 00:24:18 +0200, Dirk Meul wrote:
> Since some weeks one account can not connect anymore. When I noticed the
> problem the sever (jabber.rwth-aachen.de) had some problems. But now the
> server is working and gajim as client can connect without any problems.
>
> Following the debug documentation I did "GABBLE_PERSIST=1 GABBLE_DEBUG=all
> WOCKY_DEBUG=xmpp LM_DEBUG=net /usr/lib/telepathy/telepathy-gabble 2>&1 | tee
> gabble.log" and I found following lines in it:
> (telepathy-gabble:3449): wocky-DEBUG: _error: wocky-xmpp-reader.c:552:
> Parsing failed StartTag: invalid element name
> (telepathy-gabble:3449): wocky-DEBUG: wocky_xmpp_writer_write_stanza:
> Serializing stanza:
> * iq xmlns='jabber:client' type='get' to='jabber.rwth-aachen.de'
> id='100368764243'
> * query xmlns='jabber:iq:auth'
> * username
> "dirk.meul"
> (telepathy-gabble:3449): gabble-DEBUG: connector_error_disconnect: connection
> failed: Jabber Auth Fields: Connection has been closed for reading stanzas
So, I just tried connecting to said server to see what would happen,
and indeed I got Network Error. I got a log myself and had a
look. Here are the interesting parts:
gabble-DEBUG: _gabble_connection_connect: letting SRV lookup decide server
and port
gabble-DEBUG: _gabble_connection_connect: require-encryption is False;
flipping ignore_ssl_errors to True
gabble-DEBUG: _gabble_connection_connect: Start connecting
tp-glib/connection-DEBUG: tp_base_connection_change_status: was 4294967295,
now 1, for reason 1
tp-glib/connection-DEBUG: tp_base_connection_change_status: emitting
status-changed to 1, for reason 1
gabble-DEBUG: connection_status_changed_cb: adding callbacks
gabble-DEBUG: connection_status_changed_cb: adding callbacks
gabble-DEBUG: connection_status_changed_cb: adding callbacks
wocky-DEBUG: tcp_srv_connected: wocky-connector.c:847: SRV connect failed:
Unknown error on connect
wocky-DEBUG: abort_connect_error: wocky-connector.c:337: connector: 0xa0170a8
gabble-DEBUG: connector_error_disconnect: connection failed: Bad SRV record:
Unknown error on connect
tp-glib/connection-DEBUG: tp_base_connection_change_status: was 1, now 2, for
reason 2
tp-glib/connection-DEBUG: tp_base_connection_change_status: emitting
status-changed to 2, for reason 2
Ah, bad SRV record you say? Let's see what this said record is:
% dig srv _xmpp-client._tcp.jabber.rwth-aachen.de
; <<>> DiG 9.7.1-P2 <<>> srv _xmpp-client._tcp.jabber.rwth-aachen.de
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65463
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;_xmpp-client._tcp.jabber.rwth-aachen.de. IN SRV
;; ANSWER SECTION:
_xmpp-client._tcp.jabber.rwth-aachen.de. 172480 IN CNAME
vm01.jabber.rwth-aachen.de.
;; AUTHORITY SECTION:
rwth-aachen.de. 10480 IN SOA zs1.rz.rwth-aachen.de.
hostmaster.rwth-aachen.de. 2010080501 43200 7200 1814400 10800
;; Query time: 4 msec
;; SERVER: 128.59.59.70#53(128.59.59.70)
;; WHEN: Fri Aug 6 01:36:24 2010
;; MSG SIZE rcvd: 130
Uh oh. Compare that to a valid lookup:
% dig srv _xmpp-client._tcp.jabber.org
; <<>> DiG 9.7.1-P2 <<>> srv _xmpp-client._tcp.jabber.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50847
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 3
;; QUESTION SECTION:
;_xmpp-client._tcp.jabber.org. IN SRV
;; ANSWER SECTION:
_xmpp-client._tcp.jabber.org. 300 IN SRV 30 30 5222 hermes.jabber.org.
;; AUTHORITY SECTION:
jabber.org. 300 IN NS ns2.jeremie.com.
jabber.org. 300 IN NS ns1.jeremie.com.
;; ADDITIONAL SECTION:
hermes.jabber.org. 300 IN A 208.68.163.220
ns1.jeremie.com. 514 IN A 208.68.163.244
ns2.jeremie.com. 514 IN A 208.68.163.251
;; Query time: 50 msec
;; SERVER: 128.59.59.70#53(128.59.59.70)
;; WHEN: Fri Aug 6 01:36:29 2010
;; MSG SIZE rcvd: 178
See that? So, jabber.org has an SRV record to port 5222 on
hermes.jabber.org for XMPP clients, whereas jabber.rwth-aachen.de has,
well, I just don't know.
If I forced Empathy to use jabber.rwth-aachen.de as the server and
5222 as the port, then I got a much nicer response when I tried to
connect.
So, yeah, your SRV looks broken. Try getting that fixed and force the
server in the meantime.
Cheers,
--
Jonny Lamb, UK
[email protected]
--- End Message ---
