On Thu, Nov 24, 2005 at 08:48:15AM +0100, Manfred Heubach wrote: > found it at last. The directories of the vservers had the barrier > attribut set on all subdirectories. I haven't found a way to "unset" > the attribute. so i made a tar archive of the vserver, deleted the > directory structure and unpacked the archive again. this way the > barrier vanished. the servers are running :-)
hmm, how could that happen? > so i have still one question: how can i remove the barrier attribute? setattr --~barrier /path/to/dir best, Herbert > Manfred > > > Manfred, > > > > I ran out of ideas without having keyboad access to the thing. > > I would test next, if an init script within that guest fails at startup > > (I think of the nagios startup script). This may cause the whole init > > process to stop, depending on the type of init (fake?). > > > > After that, diff the config options of the vservers in /etc/vservers and > > look what's differnet ... > > > > HTH, > > Andreas > > > > > > > > > > Manfred Heubach schrieb: > >> I upgraded util-vserver to 0.30.208. Things don't work better :-( > >> > >> chxid cannot change the files (Invalid argument). I think because the > >> filesystem is not mounted with the tagxid option. This shouldn't be > >> necessary. > >> > >> Still needing help :-) > >> > >> Manfred > >> > >> > >> > >> ---snip--- > >> james:/etc/vservers# vserver-info > >> Versions: > >> Kernel: 2.6.8-vserver-686 > >> VS-API: 0x00010025 > >> util-vserver: 0.30.208; Oct 28 2005, 22:01:05 > >> > >> Features: > >> CC: gcc, gcc (GCC) 4.0.2 (Debian 4.0.2-2) > >> CXX: g++, g++ (GCC) 4.0.2 (Debian 4.0.2-2) > >> CPPFLAGS: '' > >> CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W > >> -funit-at-a-time' > >> CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > >> -fmessage-length=0 -funit-at-a-time' > >> build/host: i486-pc-linux-gnu/i486-pc-linux-gnu > >> Use dietlibc: yes > >> Build C++ programs: yes > >> Build C99 programs: yes > >> Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts > >> ext2fs Source: e2fsprogs > >> syscall(2) invocation: alternative > >> vserver(2) syscall#: 273/alternative > >> > >> Paths: > >> prefix: /usr > >> sysconf-Directory: /etc > >> cfg-Directory: /etc/vservers > >> initrd-Directory: $(sysconfdir)/init.d > >> pkgstate-Directory: /var/run/vservers > >> Kernelheaders: /usr/include > >> vserver-Rootdir: /var/lib/vservers > >> > >> > >> Assumed 'SYSINFO' as no other option given; try '--help' for more > >> information. > >> ---snip--- > >> > >> Andreas John schrieb: > >> > >>>Hi Manfred! > >>> > >>>Just some hints: > >>> > >>>1.) You wrote: > >>>/lib/modules/2.6.10-1-686-smp/build/include > >>> ^ ^ ^ > >>>and: Kernel: 2.6.8-vserver-686 > >>> ^ ^ ^ ^ > >>> Huh? > >>> > >>>2.) The util-vserver is quite old and known to be buggy. .209 is the > >>>current. Debian sid ships .208 thats why I am using sid as host. Maybe > >>>you can apt-get source util-vserver and dpkg-buildpackage on sarge? > >>> > >>>3.) There was a nagios thread recently ... maybe you need Capabilty > >>>RAW_NET or remove 127.0.0.1 in nagios confs (But I dont think thats the > >>>problem here .. ) > >>> > >>>4.) Did you change the xid/context? Maybe the servers root has the wrong > >>>one now -> chxid ? > >>> > >>>rgds, > >>>Andreas > >>> > >>>Manfred Heubach wrote: > >>> > >>> > >>>>Hi there, > >>>> > >>>>I've got a strange problem. I have upgraded my root server today and > >>>>changed all vservers to the legacy method. > >>>> > >>>>All are running fine except two. When I try to start them, I get a > >>>>"vcontext: chroot(): Permission denied" message (see below). > >>>> > >>>>The config directory of these vservers are exactly the same as the > >>>> other > >>>>vservers' config directories. > >>>> > >>>>I have no idea why exactly these vservers aren't running. Maybe it's > >>>>something within them? > >>>> > >>>>Some information about the system is below (vserver-info). It's Debian > >>>>Sarge. > >>>> > >>>>The working vservers have been installed some years ago. The vservers > >>>>which are not working are about 5 months old. So they have beend > >>>>installed with a newer version of vserver-debiantools. > >>>> > >>>>Anybody any ideas? > >>>> > >>>>Regards > >>>>Manfred > >>>> > >>>>---snip--- > >>>> > >>>>james:/var/lib/vservers/nagios# vserver nagios start > >>>>vcontext: chroot(): Permission denied > >>>> > >>>>An error occured while executing the vserver startup sequence; when > >>>>there are no other messages, it is very likely that the init-script > >>>>(/etc/init.d/rc 3) failed. > >>>> > >>>>Common causes are: > >>>>* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm' > >>>> build > >>>> method knows how to deal with this, but on existing installations, > >>>> appending 'true' to this file will help. > >>>> > >>>> > >>>>Failed to start vserver 'nagios' > >>>>---snip--- > >>>> > >>>>james:/var/run# vserver-info > >>>>Versions: > >>>> Kernel: 2.6.8-vserver-686 > >>>> VS-API: 0x00010025 > >>>> util-vserver: 0.30.204; May 24 2005, 22:22:03 > >>>> > >>>>Features: > >>>> CC: gcc, gcc (GCC) 3.3.5 (Debian 1:3.3.5-5) > >>>> CXX: g++, g++ (GCC) 3.3.5 (Debian 1:3.3.5-5) > >>>> CPPFLAGS: '' > >>>> CFLAGS: '-Wall -g -O2 -std=c99 -Wall -pedantic -W' > >>>> CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W > >>>>-fmessage-length=0' > >>>> build/host: i386-pc-linux-gnu/i386-pc-linux-gnu > >>>> Use dietlibc: yes > >>>> Build C++ programs: yes > >>>> Build C99 programs: yes > >>>> Available APIs: compat,v11,v13,fscompat,net,oldproc,olduts > >>>> ext2fs Source: e2fsprogs > >>>> syscall(2) invocation: fast > >>>> vserver(2) syscall#: 273/glibc > >>>> > >>>>Paths: > >>>> prefix: /usr > >>>> sysconf-Directory: /etc > >>>> cfg-Directory: /etc/vservers > >>>> initrd-Directory: $(sysconfdir)/init.d > >>>> pkgstate-Directory: /var/run/vservers > >>>> Kernelheaders: /lib/modules/2.6.10-1-686-smp/build/include > >>>> vserver-Rootdir: /var/lib/vservers > >>>> > >>>> > >>>>Assumed 'SYSINFO' as no other option given; try '--help' for more > >>>>information. > >>>>_______________________________________________ > >>>>Vserver mailing list > >>>>[email protected] > >>>>http://list.linux-vserver.org/mailman/listinfo/vserver > >>>> > >>> > >>>_______________________________________________ > >>>Vserver mailing list > >>>[email protected] > >>>http://list.linux-vserver.org/mailman/listinfo/vserver > >> > >> _______________________________________________ > >> Vserver mailing list > >> [email protected] > >> http://list.linux-vserver.org/mailman/listinfo/vserver > >> > > > > _______________________________________________ > > Vserver mailing list > > [email protected] > > http://list.linux-vserver.org/mailman/listinfo/vserver > > > > _______________________________________________ > Vserver mailing list > [email protected] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [email protected] http://list.linux-vserver.org/mailman/listinfo/vserver
