Alan Chandler wrote:
I have just upgraded my server from lenny to unstable and I now find a
tomcat application server backed has stopped working (front end on
another machine has the jk_mod installed and links through using ajp on
port 8009).
Using netstat --listening on the tomcat machine I find that tomcat is
only listening with the ip6 protocol and not ip4. Net result it has
stopped working.
I haven't changed anything during the upgrade, and I can't see anywhere
where it is defined what protocols tomcat is listening (at least there
doesn't appear to be anything in server.xml).
How can I fix this so that tomcat listens using ip4 and not ip6?
Netstat output
owl:/var/log/tomcat5.5# netstat --listening
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State
tcp 0 0 *:rsync *:* LISTEN
tcp 0 0 localhost:mysql *:* LISTEN
tcp 0 0 *:6543 *:* LISTEN
tcp 0 0 *:6544 *:* LISTEN
tcp 0 0 *:ssh *:* LISTEN
tcp 0 0 localhost:ipp *:* LISTEN
tcp 0 0 localhost:postgresql *:* LISTEN
tcp6 0 0 [::]:8009 [::]:* LISTEN
tcp6 0 0 [::]:rsync [::]:* LISTEN
tcp6 0 0 [::]:www [::]:* LISTEN
tcp6 0 0 [::]:auth [::]:* LISTEN
tcp6 0 0 [::]:8180 [::]:* LISTEN
tcp6 0 0 [::]:ssh [::]:* LISTEN
tcp6 0 0 localhost:ipp [::]:* LISTEN
tcp6 0 0 localhost:postgresql [::]:* LISTEN
tcp6 0 0 [::]:https [::]:* LISTEN
udp 0 0 *:mdns *:*
udp 0 0 255.255.255.255:1900 *:*
udp 0 0 239.255.255.250:1900 *:*
udp 0 0 *:ipp *:*
udp 0 0 *:ntp *:*
udp 0 0 *:33154 *:*
udp 0 0 *:6549 *:*
udp 0 0 *:323 *:*
udp 0 0 *:bootpc *:*
udp6 0 0 [::]:40262 [::]:*
udp6 0 0 [::]:mdns [::]:*
The strange thing here is that apache is listening only on the ip6 port
80, but it is seeing requests from my browser
--
Alan Chandler
http://www.chandlerfamily.org.uk
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
