[xmppd-dev] Jabberd14 1.6.1.1 does not listen on any ports after startup

[Petr Pisar]

On 2007-11-21, Guido Winkelmann <guido-j14 at unknownsite.de> wrote:
> The problem has been solved. The server worked after I provided an actual IP 
> address to the "<ip>" configuration elements of the s2s and c2s service (i.e. 
> changing <ip port="5222"/> to <ip port="5222">{ip address}</ip>).
>
> I think this ought to be treated as a bug, though, because the comments in the 
> config file say that it /will/ work without specifying an IP address.
>

I've met similar problem after upgrade from 1.4.4. to 1.6.1.1. Using empty <tls port="5223/> allows me to run
the server until TLS negotiation on port 5223 (e.g. with openssl
s_client). After that the server sends SIGABRT itself, terminates and
the master server process panics because it can't read data from the
pipe.

Adding IN6ADDR_ANY address (<tls port="5223">::</tls>) fixes it.

-- Petr