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
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
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
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
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
* 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]
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
7 matches
Mail list logo