FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

 
 
LinkBack Thread Tools
 
Old 03-11-2010, 08:17 PM
Tomas Pospisek
 
Default Bug#570382: more datapoints on vserver start failure

So once again I had to upgrade kernels and I noticed:

* that only my -686 kernel based machines failed to start the vservers
(guests) correctly. The amd64 machine started them without problems. I
see that Florian.Dufour@inria.fr also has an 686 machine. I'm Cc:ing Dan
to see whether that's also the case for him.

* on one of the machines the *first* of the vserver actually did start
all others not and on the other machine all vservers did not start
correctly. So it's not either all vservers fail to start or none. Might
a ressource pressure problem?

* stopping and starting the vservers one after the other "fixed" the
problem, the vservers started correctly

*t




--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: alpine.DEB.2.00.1003112212200.2586@tpo-laptop">http://lists.debian.org/alpine.DEB.2.00.1003112212200.2586@tpo-laptop
 
Old 03-11-2010, 10:31 PM
Dan Gardner
 
Default Bug#570382: more datapoints on vserver start failure

On Thu, Mar 11, 2010 at 10:17:40PM +0100, Tomas Pospisek wrote:
> So once again I had to upgrade kernels and I noticed:
>
> * that only my -686 kernel based machines failed to start the vservers
> (guests) correctly. The amd64 machine started them without problems. I
> see that Florian.Dufour@inria.fr also has an 686 machine. I'm Cc:ing Dan
> to see whether that's also the case for him.

Yes, also the case for me. I haven't tried an amd64 vserver kernel.

> * on one of the machines the *first* of the vserver actually did start
> all others not and on the other machine all vservers did not start
> correctly. So it's not either all vservers fail to start or none. Might
> a ressource pressure problem?

I found the same thing - it wasn't reproducible 100% of the time.

> * stopping and starting the vservers one after the other "fixed" the
> problem, the vservers started correctly

Again, my findings were similar. The problem only seemed to exhibit
itself using "/etc/init.d/vserver start" - starting vservers with
"vserver foo start" would always work.

-dan



--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100311233100.GB28706@hercules.pureserver.info">h ttp://lists.debian.org/20100311233100.GB28706@hercules.pureserver.info
 

Thread Tools




All times are GMT. The time now is 06:42 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org