Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
On Fri, Mar 23, 2007 at 03:06:39PM +0100, Sjoerd Simons wrote: > > Obviously, it's not reasonable to enable IPv6 support at the *expense of* > > IPv4 support. > Uhm, by default on linux if you listen on the IPv6 wildcard address, you'll > get > IPv4 automagically too. For example my output for ssh is the same: > $ lsof -p 16733 | grep -i listen > sshd16733 root3u IPv6 5141804TCP *:ssh (LISTEN) > And i can assure you, that works with ipv4 too :) Right, I had this explained to me after the fact. > > The IPv6 support in jabber seems to need a total rework. In the meantime, > > I'll prepare an NMU to revert this change from the -3.1 NMU. > I can agree with that, the code isn't really good. But thanks to the fact > that linux listens on both IPv4 and IPv6 on an IPv6 socket it doesn't break > IPv4 compatibility. > I just tested that you can even listening on multiple ipv4 addresses even > works fine (Not the IP protocol vs. the address): > $ lsof -n -p 9152 | grep -i listen > jabberd 9152 jabber7u IPv6 6744306 TCP 127.0.0.1:xmpp-client (LISTEN) > jabberd 9152 jabber8u IPv6 6744307 TCP 145.120.11.130:xmpp-client > (LISTEN) > jabberd 9152 jabber 11u IPv6 6744310 TCP *:xmpp-server (LISTEN) > So imho the NMU which disables ipv6 should be reverted and probably an > modprobe > ipv6 added to the init script. On a normal Debian system, the ipv6 module is auto-loaded for you whether you want it or not. AFAICS, the reason for the reported failures is that users were running unofficial kernels without ipv6 support. You can't fix that with a modprobe, certainly. So I think the NMU reverting this change is still the correct course of action for etch, because: - enabling the ipv6 support does cause a regression in support for ipv4 systems, so is not a change that should be made during a freeze - the change was made in an NMU, so again, regressions are not appropriate unless the changes have been specifically ok'ed by the maintainer. I think this would be a perfectly reasonable change to reintroduce at the beginning of the lenny cycle, preferably with discussion on debian-devel on the appropriate way to handle ipv6 support (which might, e.g., result in someone offering a better patch). Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
On Fri, Mar 02, 2007 at 03:23:53AM -0800, Steve Langasek wrote: > Ok -- the IPv6 support in jabber *is* a problem; loading ipv6 support in the > kernel is not an adequate workaround, because when IPv6 support is compiled > into jabber, it *only* listens on IPv6: > > $ sudo lsof -p 2918|grep TCP > jabberd 2918 jabber7u IPv6 7526 TCP *:xmpp-client (LISTEN) > jabberd 2918 jabber 10u IPv6 7531 TCP *:xmpp-server (LISTEN) > > Obviously, it's not reasonable to enable IPv6 support at the *expense of* > IPv4 support. Uhm, by default on linux if you listen on the IPv6 wildcard address, you'll get IPv4 automagically too. For example my output for ssh is the same: $ lsof -p 16733 | grep -i listen sshd16733 root3u IPv6 5141804TCP *:ssh (LISTEN) And i can assure you, that works with ipv4 too :) > The IPv6 support in jabber seems to need a total rework. In the meantime, > I'll prepare an NMU to revert this change from the -3.1 NMU. I can agree with that, the code isn't really good. But thanks to the fact that linux listens on both IPv4 and IPv6 on an IPv6 socket it doesn't break IPv4 compatibility. I just tested that you can even listening on multiple ipv4 addresses even works fine (Not the IP protocol vs. the address): $ lsof -n -p 9152 | grep -i listen jabberd 9152 jabber7u IPv6 6744306 TCP 127.0.0.1:xmpp-client (LISTEN) jabberd 9152 jabber8u IPv6 6744307 TCP 145.120.11.130:xmpp-client (LISTEN) jabberd 9152 jabber 11u IPv6 6744310 TCP *:xmpp-server (LISTEN) So imho the NMU which disables ipv6 should be reverted and probably an modprobe ipv6 added to the init script. Sorry for commenting so late, but hopefully it can still be fixed for etch... Sjoerd -- The best defense against logic is ignorance. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
tags 405565 patch
thanks
Attached is the trivial patch for this bug.
Since this bug was introduced in an NMU, I'm taking the liberty of uploading
the fix straight to incoming as a 0-day NMU.
Thanks,
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
[EMAIL PROTECTED] http://www.debian.org/
diff -u jabber-1.4.3/debian/rules jabber-1.4.3/debian/rules
--- jabber-1.4.3/debian/rules
+++ jabber-1.4.3/debian/rules
@@ -17,7 +17,7 @@
build: build-stamp
build-stamp: patch-stamp
dh_testdir
- ./configure --enable-ssl --enable-ipv6
+ ./configure --enable-ssl
$(MAKE)
# cd docs ; ${MAKE} html
touch build-stamp
diff -u jabber-1.4.3/debian/changelog jabber-1.4.3/debian/changelog
--- jabber-1.4.3/debian/changelog
+++ jabber-1.4.3/debian/changelog
@@ -1,3 +1,14 @@
+jabber (1.4.3-3.3) unstable; urgency=high
+
+ * Non-maintainer upload.
+ * High-urgency upload for RC bugfix.
+ * Revert the change in -3.1 to enable IPv6 support, because jabberd
+currently only supports IPv4 *or* IPv6, you can't enable both at the
+same time -- and obviously we need IPv4 support to work.
+Closes: #405565, reopens: #334414.
+
+ -- Steve Langasek <[EMAIL PROTECTED]> Fri, 2 Mar 2007 03:24:58 -0800
+
jabber (1.4.3-3.2) unstable; urgency=high
* Non-maintainer upload.
Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
Ok -- the IPv6 support in jabber *is* a problem; loading ipv6 support in the kernel is not an adequate workaround, because when IPv6 support is compiled into jabber, it *only* listens on IPv6: $ sudo lsof -p 2918|grep TCP jabberd 2918 jabber7u IPv6 7526 TCP *:xmpp-client (LISTEN) jabberd 2918 jabber 10u IPv6 7531 TCP *:xmpp-server (LISTEN) Obviously, it's not reasonable to enable IPv6 support at the *expense of* IPv4 support. The IPv6 support in jabber seems to need a total rework. In the meantime, I'll prepare an NMU to revert this change from the -3.1 NMU. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
>From the strace, I've determined that this is a bug that only affects jabber when running on systems without ipv6 support in the kernel. IPv6 support is certainly enabled in the kernel now by default, so I'm not sure that this bug should be considered RC at all. Anyway, the immediate workaround is to load ipv6 support in the kernel, AFAICS. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
* Olivier ([EMAIL PROTECTED]) [070104 06:49]: > Jabberd fails to start: > > 20070104T14:39:43: [notice] (-internal): initializing server > 20070104T14:39:43: [alert] (-internal): io_select unable to listen on 5222 > [0.0.0.0]: jabberd already running or invalid interface? > 20070104T14:39:43: [alert] (-internal): io_select unable to listen on 5269 > [0.0.0.0]: jabberd already running or invalid interface? I cannot reproduce this on amd64 - can you please strace jabber, and send the log and the ip-parts of your configuration file? (sudo -u jabber strace -o logfile /usr/sbin/jabberd), and make sure jabber can write to it's log directory. Cheers, Andi -- http://home.arcor.de/andreas-barth/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#405565: jabber: fails to start/bind since last apt-get update (libc6 or sparc issue?)
Package: jabber Version: 1.4.3-3.1 Severity: grave Justification: renders package unusable Jabberd fails to start: 20070104T14:39:43: [notice] (-internal): initializing server 20070104T14:39:43: [alert] (-internal): io_select unable to listen on 5222 [0.0.0.0]: jabberd already running or invalid interface? 20070104T14:39:43: [alert] (-internal): io_select unable to listen on 5269 [0.0.0.0]: jabberd already running or invalid interface? It's similar to bug #386601, but using 0.0.0.0 doesn't help anymore. Same without any IP or with the "real" server IP. No config change since several months. Ports are unused and jabberd is not running. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.24-sparc64 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages jabber depends on: ii jabber-common0.4 Jabber server and transport (commo ii libc62.3.6.ds1-9 GNU C Library: Shared libraries ii libexpat11.95.8-3.4 XML parsing C library - runtime li ii libpth20 2.0.7-4 The GNU Portable Threads ii libssl0.9.8 0.9.8c-4SSL shared libraries ii procps 1:3.2.7-3 /proc file system utilities jabber recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
