On Wed, Mar 29, 2006 at 06:17:33PM +0200, Gerhard Hofmann wrote: > Herbert Poetzl wrote: > > > >check that the symbolic links inside the config > >tree exist and point to the proper places and > >that the /dev files and /proc dir is there > > > >most likely your tool configurations differ > >slightly and this is not given > > > >also the (longer) output of --debug (for startup) > >might shed some light on it ... > > > > I have rebooted my (backup) vserver host in the meantime and all of a > sudden the vserver guests have been successfully started! > > Maybe the vserver startup script has fixed some things that were not OK? > The startup messages showed some like "fixing /proc visibility for all > vservers"...
I doubt it, if the following was true: >>> Of course I have tested VServer environment on backvserv. >>> I can create and run new VServer guests without any problems. because the proc visibility and startup scripts are relevant for all guests ... > Will do some further testing with my rsync scripts. would be interesting to find the real cause of your previous issues ... > Thanks for your help! best, Herbert > Regards > Gerhard > > _______________________________________________ > 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
