Miguel Landaeta wrote:
2010/1/6 Andriy Lesyuk :
Maybe you can do this way: disable IPv6 in saying 1.6.1.1-5 and turn it on
back when there will be fixed upstream version?
Nope,
The problem is caused by the new default setting of net.ipv6.bindv6only = 1
on squeeze and sid.
Please, cou
2010/1/6 Andriy Lesyuk :
> Maybe you can do this way: disable IPv6 in saying 1.6.1.1-5 and turn it on
> back when there will be fixed upstream version?
Nope,
The problem is caused by the new default setting of net.ipv6.bindv6only = 1
on squeeze and sid.
Please, could you set that setting to 0 an
I figured out that this is somehow related to IPv6 support which was
"fixed to work" in 1.6.1.1-4... I guess disabling corresponding patch
will help. I found many similar reports in Google in other distributions
so it looks to be the upstream bug.
Maybe you can do this way: disable IPv6 in say
Workaround does not work for me... Explicitly setting:
127.0.0.1
does not help:
Dec 23 23:12:25 andrix jabberd14[21718]: [alert] (-internal): mio unable
to listen on 5222 [127.0.0.1]: jabberd already running or invalid interface?
And no Jabberd is really running! Nothing on port 5222 either.
tags 561705 - moreinfo unreproducible + confirmed
thanks
Thanks for your report.
Finally, I could reproduce this.
This bug is causing the following problems:
* By default, jabberd only will listen on :: IPv6 address.
* If you configure jabberd to explicitly listen on any wildcard address like
:
Hi!
I can confirm that after upgrade I'm not able to connect to the Jabber
server any more... while all looks fine:
# netstat -lnp | grep jabber
tcp6 0 0 :::5269 :::*
LISTEN 31819/jabberd
tcp6 0 0 :::5222 :::*
Miguel Landaeta wrote:
> Using the default configuration I could not reproduce this bug.
> With default configuration jabberd just start and listen in ports 5222 and
> 5269
> without any error.
I tried purging jabberd14, reinstalling, and it listens. Then I tried
copying in the config file I was
Hi,
Using the default configuration I could not reproduce this bug.
With default configuration jabberd just start and listen in ports 5222 and 5269
without any error.
mig...@xanadu:~# netstat -tln
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Addre
Package: jabberd14
Version: 1.6.1.1-4
Severity: normal
I upgraded, it was working, server was rebooted, no workee.
With the default configuration, this is all that is logged now:
Dec 19 09:38:42 wren jabberd14[24234]: [notice] (sessions.kitenet.net): session
manager instance 'sessions.kitenet.n
9 matches
Mail list logo
