It seemed I was getting close to a solution on this issue, so I'm posting this again in the hope that someone will know what's going wrong.

This IPv6 ping doesn't work, and it's causing a lengthy freeze in the tomcat start-up (see bottom).

This is on Debian Etch linux 2.6.20 - can anyone tell me what controls the config for IPv6 here?

Thanks
Adam


Adam Hardy on 23/05/08 15:47, wrote:
No, on the box that doesn't work, I get this:

[EMAIL PROTECTED]:~$ sudo ping6  ::1
Password:
PING ::1(::1) 56 data bytes
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted
ping: sendmsg: Operation not permitted

--- ::1 ping statistics ---
4 packets transmitted, 0 received, 100% packet loss, time 3000ms

I tried using sudo because of the 'Operation not permitted' message - thought it might be a user permissions thing - but apparently not.


Jim Cox on 23/05/08 15:08, wrote:
Admittedly grasping at straws here, but does an IPv6 ping to localhost work
the same on both boxes, e.g.:

[EMAIL PROTECTED]:~$ ping6 ::1
PING ::1(::1) 56 data bytes
64 bytes from ::1: icmp_seq=1 ttl=64 time=0.047 ms
64 bytes from ::1: icmp_seq=2 ttl=64 time=0.039 ms

--- ::1 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1001ms

?


On Thu, May 22, 2008 at 12:29 PM, Adam Hardy <[EMAIL PROTECTED]>
wrote:

Tell you the truth, I can only assume IPv6 stuff is configured to the
debian etch defaults - although that might have changed between the date I
installed the no-pause-box and the date I installed the problem box.

no-pause-box:
eth0      Link encap:Ethernet  HWaddr 00:10:DC:79:FF:8F
inet addr:192.168.0.234 Bcast:192.168.0.255 Mask:255.255.255.0
         inet6 addr: fe80::210:dcff:fe79:ff8f/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:606692 errors:0 dropped:0 overruns:0 frame:0
         TX packets:598681 errors:0 dropped:0 overruns:0 carrier:0
         collisions:65 txqueuelen:1000
         RX bytes:145074456 (138.3 MiB)  TX bytes:44751878 (42.6 MiB)

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:59645 errors:0 dropped:0 overruns:0 frame:0
         TX packets:59645 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:5125125 (4.8 MiB)  TX bytes:5125125 (4.8 MiB)

box-with-pause (eth1 is LAN, eth2 is internet):
eth1      Link encap:Ethernet  HWaddr 00:18:F3:98:F4:EC
         inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
         inet6 addr: fe80::218:f3ff:fe98:f4ec/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:134101 errors:0 dropped:0 overruns:0 frame:0
         TX packets:138909 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:12595060 (12.0 MiB)  TX bytes:53461584 (50.9 MiB)
         Base address:0xbc00 Memory:fe8e0000-fe900000

eth2      Link encap:Ethernet  HWaddr 00:08:54:0A:B1:E7
         inet addr:86.138.125.132  Bcast:86.138.125.132  Mask:
255.255.255.255
         inet6 addr: fe80::208:54ff:fe0a:b1e7/64 Scope:Link
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:56889 errors:0 dropped:0 overruns:0 frame:0
         TX packets:50695 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:1000
         RX bytes:42379708 (40.4 MiB)  TX bytes:6543279 (6.2 MiB)
         Interrupt:58 Base address:0xd800

lo        Link encap:Local Loopback
         inet addr:127.0.0.1  Mask:255.0.0.0
         inet6 addr: ::1/128 Scope:Host
         UP LOOPBACK RUNNING  MTU:16436  Metric:1
         RX packets:3894 errors:0 dropped:0 overruns:0 frame:0
         TX packets:3894 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:0
         RX bytes:236606 (231.0 KiB)  TX bytes:236606 (231.0 KiB)



Jim Cox on 22/05/08 14:05, wrote:

I'm assuming the pause you saw was at the following line?
 connect(11, {sa_family=AF_INET6, sin6_port=htons(48669),
inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0},
28) = -1 ETIMEDOUT (Connection timed out)

That looks like a connect attempt to the IPv6 loopback address (?) which times out, but the corresponding line from the "no-pause" box seems to do the same without delay. Do you have IPv6 enabled on both boxes, i.e. does
the output from "/sbin/ifconfig -a" look similar?

On Thu, May 22, 2008 at 8:52 AM, Adam Hardy <[EMAIL PROTECTED]>
wrote:

 I think this is the equivalent part of the strace log from another
machine
on the LAN:

socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 10
listen(10, 1)                           = 0
getsockname(10, {sa_family=AF_INET6, sin6_port=htons(54792),
inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0},
[28]) = 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 11
connect(11, {sa_family=AF_INET6, sin6_port=htons(54792),
inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0},
28) = 0
fcntl64(10, F_GETFL)                    = 0x2 (flags O_RDWR)
fcntl64(10, F_SETFL, O_RDWR|O_NONBLOCK) = 0
accept(10, {sa_family=AF_INET6, sin6_port=htons(51175),
inet_pton(AF_INET6,
"::1", &sin6_addr), sin6_flowinfo=0, sin6_scope_id=0}, [28]) = 12
shutdown(11, 2 /* send and receive */)  = 0



Jim Cox on 22/05/08 13:38, wrote:

 Can you compare that output to a capture from the box where you don't
see
the pause? I wonder if it's a difference in IPv4/IPv6 configuration
between
the boxes...

On Thu, May 22, 2008 at 8:24 AM, Adam Hardy <
[EMAIL PROTECTED]>
wrote:

 Found it! But I think my knowledge of linux system calls and kernel

functions is letting me down now. Presumably that is port 48669, which
should be open - but is it a DNS call? If it is a DNS call, then the
DNS
server on the same machine should serve it - piping it out to the net, presumably. But with my DNS server running, which up to now has worked
fine,
and with the gateway open to allow internet access, tomcat still
freezes.

So I guess it doesn't matter what the DNS call is for, the problem is
that
my DNS server is not serving it? I guess that means its config needs
tweaking to tell it to serve DNS requests on the loopback interface.


socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 10
listen(10, 1)                           = 0
getsockname(10, {sa_family=AF_INET6, sin6_port=htons(48669),
inet_pton(AF_INET6, "::", &sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0},
[28]) = 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IP) = 11
connect(11, {sa_family=AF_INET6, sin6_port=htons(48669),
inet_pton(AF_INET6, "::1", &sin6_addr), sin6_flowinfo=0,
sin6_scope_id=0},
28) = -1 ETIMEDOUT (Connection timed out)
close(10)                               = 0
close(11)                               = 0


---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to