[PVE-User] veths/gateway failing after random time.

Timh B timh at shiwebs.net
Tue Apr 17 08:36:22 CEST 2012


We've seen this as well, but only on IPv6 as we get a fair amount of
traffic over IPv4 - an "inside ping" from the vmnode actually makes it
work again, we have no idea what is causing this and for us where we are
really anxious we do a cron-scheduled ping to the "world" every 5 minutes.
It might have something to do with power-saving stuff as we haven't seen
this on older ARCH cpu's, only new ones and our current working theory is
that apm/powermanager "kills" fds/procs that has been idle for longer than

If it's not the case, then we might have a bug on our hands.


On Tue, April 17, 2012 04:32, dan wrote:
> I am running proxv2.  I have 3 containers with veths.  After boot,
> each container works properly.  After a seemingly random amount of
> time, the networking starts behaving strangely.  The containers are
> still up, and can still ping ip addresses on the same subnet.  they
> can ping the gateway.  They do not route through the default gateway
> though.  the default route is still in place and shows up in 'ip
> route'.  'service restart networking' or '/etc/init.d/networking
> restart' temporarily fixes issue.
> I am running containers based on the deb6 and cent5 templates from
> prox.  issue happens in both.
> running 3 containers, I can often see 2 or 3 of them lose networking
> at the same time.
> Thanks for any help.
> _______________________________________________
> pve-user mailing list
> pve-user at pve.proxmox.com
> http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-user

-- Timh

More information about the pve-user mailing list