|
On 10/10/06, Sebastian Vieira <sebvieira@xxxxxxxxx> wrote:
I'll have tcpdump running and test some more. I'm not totally comfortable
with tcpdump but i guess it's possible to monitor the connection failure
with it. At the very least i'll be able to give some more information about
it.
Okay, i've done that (windump instead of tcpdum, but ok), and when i
powerdown the active node i see the following message repeated alot:
15:29:22.231586 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:22.231636 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:22.231692 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:22.231772 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:22.231827 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:27.241215 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:27.241269 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:27.241347 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:27.241404 arp who-has 192.168.50.110 tell 192.168.50.110
15:29:27.241471 arp who-has 192.168.50.110 tell 192.168.50.110
Funny thing is, 192.168.50.110 is the cluster ip. I'm not too familiar with
tcp (yes, i'm learning) so i don't know what this means. No more packets to
the client either are sent, so the connection just times out (did i say that
correctly? :))
Kind regards,
Sebastian
|
