Re: [vserver] cannot find vserver-setup

On Wednesday, September 28, 2011, Herbert Poetzl wrote:
> On Wed, Sep 28, 2011 at 06:26:08AM -0400, Chuck wrote:
>
> > i have a running vserver that works perfectly but today i
> > cannot enter it. i can enter others but not this one meaning i
> > also cannot shut it down manually. i get the following error:
>
> > enterprise vservers # vserver cacti enter Can not find a
> > vserver-setup at '/etc/vservers/cacti/'.
>
> depending on the kernel, check for stray barrier at
> unexpected places and/or run the enter with --debug
> and provide us with the output
>

no barrier anywhere that i can find.. here is the debug output.

enterprise etc # vserver --debug cacti enter
+ shift
+ true
+ case "$1" in
+ shift
+ break
+ OPTION_ALL=($OPTION_SILENT $OPTION_VERBOSE $OPTION_DEBUG $OPTION_DEFAULTTTY)
+ SELF=("$0" "${OPTION_ALL[@]}")
+ vserver=cacti
+ cmd=enter
+ test enter '!=' build
+ allow_legacy=
+ vserver=cacti
+ case "$vserver" in
++ vuname --get --xid cacti
+ context='/etc/vservers/cacti Linux cacti 2.6.35-vs2.3.0.36.32-gentoo #3 SMP Fri Aug 19
16:44:57 EDT 2011 x86_64 (none)'
+ test -d '/etc/vservers/cacti Linux cacti 2.6.35-vs2.3.0.36.32-gentoo #3 SMP Fri Aug 19
16:44:57 EDT 2011 x86_64 (none)'
+ VSERVER_DIR=/etc/vservers/cacti
+ do_legacy=
+ test '!' -e /etc/vservers/cacti/legacy
+ test -d /etc/vservers/cacti -o '!' -e /etc/vservers/cacti.conf
+ test -z ''
+ test -d /etc/vservers/cacti
+ _setVserverName
++ basename /etc/vservers/cacti
+ VSERVER_NAME=cacti
+ test enter '!=' start -o -n ''
+ test enter '!=' enter -a enter '!=' stop
+ test -n ''
+ isAvoidNamespace /etc/vservers/cacti
+ local cfgdir
+ /usr/sbin/vserver-info - FEATURE namespace
++ /usr/sbin/vserver-info /etc/vservers/cacti CFGDIR
+ cfgdir=/etc/vservers/cacti
+ test '!' -e /etc/vservers/cacti/namespace
+ test -e /etc/vservers/.defaults/nonamespace -o -e /etc/vservers/cacti/nonamespace
+ isVserverRunning /etc/vservers/cacti
+ local _ivr_ctx _ivr_procnum
+ getVserverStatus /etc/vservers/cacti _ivr_ctx _ivr_procnum 1
+ test -r /etc/vservers/cacti/run
+ local _gvs_ctx
+ read _gvs_ctx
+ eval '_ivr_ctx=$_gvs_ctx'
++ _ivr_ctx=3910
++ /usr/sbin/vuname -g --xid 3910 context
+ test /etc/vservers/cacti = /etc/vservers/cacti
+ test -n _ivr_procnum
+ local _gvs_tmp
+ _getProcNumberCount 3910 _gvs_tmp
+ local _gp_var=_gvs_tmp
+ local _gp_procnr_cnt=0
+ test -d /proc/virtual
++ /bin/grep '^Tasks:' /proc/virtual/3910/status
+ set -- Tasks: 122
+ _gp_procnr_cnt=122
+ let _gp_procnr_cnt=_gp_procnr_cnt+0
+ eval '_gvs_tmp=$_gp_procnr_cnt'
++ _gvs_tmp=122
+ eval '_ivr_procnum=$_gvs_tmp'
++ _ivr_procnum=122
+ test 122 = 0
+ return 0
+ test 122 '!=' 0
+ test -z ''
+ return 0
+ exec /usr/sbin/vspace --mount --fs --enter /etc/vservers/cacti -- /usr/sbin/vserver ----
nonamespace --debug cacti enter
+ shift
+ true
+ case "$1" in
+ shift
+ break
+ OPTION_ALL=($OPTION_SILENT $OPTION_VERBOSE $OPTION_DEBUG $OPTION_DEFAULTTTY)
+ SELF=("$0" "${OPTION_ALL[@]}")
+ vserver=cacti
+ cmd=enter
+ test enter '!=' build
+ allow_legacy=
+ vserver=cacti
+ case "$vserver" in
++ vuname --get --xid cacti
+ context=
+ test -d ''
+ VSERVER_DIR=/etc/vservers/cacti
+ do_legacy=
+ test '!' -e /etc/vservers/cacti/legacy
+ test -d /etc/vservers/cacti -o '!' -e /etc/vservers/cacti.conf
+ test -z ''
+ test -d /etc/vservers/cacti
+ echo 'Can not find a vserver-setup at '\''/etc/vservers/cacti/'\''.

Possible solutions:
* fix the spelling of the '\''cacti'\'' vserver name
* read '\''vserver cacti build --help'\'' about ways to create a new vserver
* see '\''vserver --help'\'' for the syntax of this command
'
Can not find a vserver-setup at '/etc/vservers/cacti/'.

Possible solutions:
* fix the spelling of the 'cacti' vserver name
* read 'vserver cacti build --help' about ways to create a new vserver
* see 'vserver --help' for the syntax of this command

+ exit 5

here is the 'root' content of the /etc/vservers/cacti directory

drwxr-xr-x 7 root root 408 2010-07-31 10:28 .
drwxrwxrwx 35 root root 872 2011-09-28 05:11 ..
drwxr-xr-x 3 root root 72 2008-11-19 11:49 apps
-rw-r--r-- 1 root root 26 2009-01-27 15:22 bcapabilities
lrwxrwxrwx 1 root root 39 2011-09-22 17:41 cache ->
/etc/vservers/.defaults/cachebase/cacti
-rw-r--r-- 1 root root 10 2009-01-27 15:21 ccapabilities
-rw-r--r-- 1 root root 5 2008-11-19 11:49 context
drwxr-xr-x 2 root root 48 2008-11-19 11:49 cpuset
-rw-r--r-- 1 root root 41 2008-11-19 12:22 flags
-rw-r--r-- 1 root root 251 2008-11-19 12:23 fstab
drwxr-xr-x 4 root root 96 2008-11-19 22:24 interfaces
-rw-r--r-- 1 root root 6 2008-11-19 11:49 name
lrwxrwxrwx 1 root root 23 2011-09-22 17:41 run -> /var/run/vservers/cacti
drwxr-xr-x 2 root root 112 2008-11-19 12:22 scripts
drwxr-xr-x 2 root root 72 2008-11-19 11:49 uts
lrwxrwxrwx 1 root root 38 2011-09-22 17:41 vdir ->
/etc/vservers/.defaults/vdirbase/cacti

> > Possible solutions: * fix the spelling of the 'cacti' vserver
> > name * read 'vserver cacti build --help' about ways to create
> > a new vserver * see 'vserver --help' for the syntax of this
> > command
>
> > i compared the contents of that dir with others and it looks
> > the same.
>
> well, an ls -la /etc/vservers/cacti/ might helpt
> here as well ...
>
> > any clues where to look?
>
> see above, best,
> Herbert
>
> > there was a host crash that was hardware related but it is
> > back up and everything works. i had to rename some dirs in a
> > vserver and copy their contents into the new dir because i kept
> > getting an apache message 'not a valid directory' however that
> > is fixed. i thought this problem may be similar but renaming
> > and copying contents did not help.
>
> > --
>
> > Chuck
>

-- 
Chuck