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 :::* LISTEN 31819/jabberd

Logs:
Dec 23 12:53:46 andrix jabberd14[31819]: [notice] (sessions.192.168.14.2): session manager instance 'sessions.192.168.14.2' is now responsible for domain 'localhost' Dec 23 12:53:46 andrix jabberd14[31819]: [notice] (sessions.192.168.14.2): session manager instance 'sessions.192.168.14.2' is now responsible for domain '192.168.14.2' Dec 23 12:53:46 andrix jabberd14[31819]: [notice] (sessions.192.168.14.2): session manager instance 'sessions.192.168.14.2' is now responsible for domain 'sessions.192.168.14.2' Dec 23 12:53:46 andrix jabberd14[31819]: [notice] (-internal): initializing server

No more errors anywhere....


When trying to "telnet":
$ nc -v 127.0.0.1 5222
localhost [127.0.0.1] 5222 (xmpp-client) : Connection refused

Jabberd does not say anything about the reason.

TCPDump:
# tcpdump -n -i lo
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on lo, link-type EN10MB (Ethernet), capture size 96 bytes
12:57:58.705142 IP 127.0.0.1.34516 > 127.0.0.1.5222: Flags [S], seq 207045932, win 32792, options [mss 16396,sackOK,TS val 2185940 ecr 0,nop,wscale 6], length 0 12:57:58.705159 IP 127.0.0.1.5222 > 127.0.0.1.34516: Flags [R.], seq 0, ack 207045933, win 0, length 0

How at least I can check the reason???

Thanks,
Andriy



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to