Hi,
about once a week we run into trouble with one of our master/vservers:
suddenly all vservers on that host seem to be offline, they do not
reply a ping request and all tcp connections get disconnected. The
master is fine, however. I can ssh to the master, enter one vserver
from there and initia
Hi,
in a previous mail I noticed that sometimes I found
the alias interface of a vserver down, thus this
vserver had lost its network connectivity. Now I
have found a way to reproduce this effect:
I've got 2 vservers (mainmx and smtp-staff) running:
master:~# vserver-stat
CTX PROCVSZRSS
On Fri, Feb 27, 2004 at 02:15:03PM +0100, Gebhardt Thomas wrote:
> Hi,
>
> in a previous mail I noticed that sometimes I found
> the alias interface of a vserver down, thus this
> vserver had lost its network connectivity. Now I
> have found a way to reproduce this effect:
>
> I've got 2 vservers
On Friday 27 February 2004 16:28, Herbert Poetzl wrote:
Hi,
> > 3: eth1: mtu 1500 qdisc pfifo_fast qlen 1000
> > link/ether 00:07:e9:06:bb:08 brd ff:ff:ff:ff:ff:ff
> > inet xxx.yyy.z.14/25 brd xxx.yyy.z.127 scope global eth1
> > inet xxx.yyy.z.35/25 brd xxx.yyy.z.127 scope global eth
On Mon, Mar 01, 2004 at 10:18:05AM +0100, Gebhardt Thomas wrote:
> On Friday 27 February 2004 16:28, Herbert Poetzl wrote:
>
> Hi,
>
> > > 3: eth1: mtu 1500 qdisc pfifo_fast qlen 1000
> > > link/ether 00:07:e9:06:bb:08 brd ff:ff:ff:ff:ff:ff
> > > inet xxx.yyy.z.14/25 brd xxx.yyy.z.127 sc
On Mon, Feb 02, 2004 at 11:05:32AM +0100, Gebhardt Thomas wrote:
> Hi,
>
> about once a week we run into trouble with one of our master/vservers:
> suddenly all vservers on that host seem to be offline, they do not
> reply a ping request and all tcp connections get disconnected. The
> master is fi
On Monday 02 February 2004 11:48, you wrote:
> > suddenly all vservers on that host seem to be offline, they do not
> > reply a ping request and all tcp connections get disconnected. The
> > master is fine, however. I can ssh to the master, enter one vserver
> hmm, that sounds like some router, w
On Tue, Feb 03, 2004 at 05:16:14PM +0100, Gebhardt Thomas wrote:
> 1. The router did not send an arp request.
> 2. The host did not receive the request for some reason
> 3. The host did not answer the request
> 4. The router did not cache the answer
tcpdump is your friend. :)
Regards,
Erik Smit
On Tuesday 03 February 2004 19:06, Erik Smit - Zylon wrote:
Hi,
> tcpdump is your friend. :)
Certainly, but a watched pot does not boil.:-)
I have tcpdump running now, filtering on arp packages.
Cheers, Thomas
___
Vserver mailing list
[EMAIL PROTECTED
On Monday 02 February 2004 11:48, you wrote:
Hi,
> hmm, that sounds like some router, which gets
> confused by many ip addresses for one MAC ...
>
> older cisco routers showed that behaviour, flushing
> their arp caches after some overflow ...
it seems that this (or a related???) bug has hit me
On Fri, Feb 13, 2004 at 01:48:25PM +0100, Gebhardt Thomas wrote:
> On Monday 02 February 2004 11:48, you wrote:
>
> Hi,
>
> > hmm, that sounds like some router, which gets
> > confused by many ip addresses for one MAC ...
> >
> > older cisco routers showed that behaviour, flushing
> > their arp c
Hi,
> sounds interesting, any chance to investigate this
> further?
well, I really hope that I do not get the chance that often :-)
Indeed, if we can't fix that, I 'll be under pressure to migrate
away from the vserver strategy.
Any idea how to further investigate that situation in
case of a fut
On Fri, Feb 13, 2004 at 04:23:37PM +0100, Gebhardt Thomas wrote:
> Hi,
>
> > sounds interesting, any chance to investigate this
> > further?
>
> well, I really hope that I do not get the chance that often :-)
> Indeed, if we can't fix that, I 'll be under pressure to migrate
> away from the vserv
13 matches
Mail list logo
