[vserver] xid=__ vshelper.init: can not determine xid of vserver

From: Ekkard Gerlach <ekkardgerlach_at_aiai.de>
Date: Tue 06 Dec 2011 - 15:37:30 GMT
Message-ID: <20111206153730.GE20816@rex4>

Hello,

I try to start a Suse 11.1 that ist installed with rsync.

root@squeeze64:/var/lib/vservers/suse111/etc/init.d# vserver suse111 start
vshelper.init: can not determine xid of vserver 'suse111'; returned value was ''

This usually means that you're using an init-less init-style, but the
guest isn't configured to start any service. Try enabling a service,
changing the init-style, or making the contexts persistent.

An error occured after executing the vserver startup sequence. This
means that some processes may exist in the created context and the
manual execution of
  /usr/sbin/vserver '/etc/vservers/suse111' stop
is recommended to fix this.

# vserver --debug suse111 start
[...]
++ /usr/sbin/vserver-info - FEATURE vshelper
++ test -n ''
++ return 0
++ local xid
+++ /usr/sbin/vserver-info /etc/vservers/suse111 CONTEXT false
++ xid=
++ warning 'vshelper.init: can not determine xid of vserver '\''suse111'\''; returned value was '\'''\''

This usually means that you'\''re using an init-less init-style, but the
[...]

root@squeeze64:/etc/vservers/suse111# cat context
1099

I installed suse111 using rsync an deleting some boot- and hardware-scripts in /etc/init.d/:

# vserver suse111 build --context 1099 --hostname suse111 --interface \
 suse111=eth0:192.168.0.99/24 -m rsync -- --source /mnt/

root@squeeze64:~# ls /var/lib/vservers/suse111/ -l
insgesamt 96
drwxr-xr-x 2 root root 4096 5. Dez 19:38 bin
drwxr-xr-x 3 root root 4096 5. Dez 19:56 boot
drwxr-xr-x 2 root root 4096 6. Dez 13:19 dev
drwxr-xr-x 107 root root 12288 6. Dez 14:30 etc
drwxr-xr-x 3 root root 4096 5. Dez 20:00 home
drwxr-xr-x 16 root root 12288 5. Dez 19:44 lib
drwx------ 2 root root 4096 5. Dez 19:25 lost+found
drwxr-xr-x 3 root root 4096 6. Dez 12:30 media
drwxr-xr-x 2 root root 4096 3. Dez 2008 mnt
drwxr-xr-x 3 root root 4096 9. Dez 2008 opt
dr-xr-xr-x 2 root root 4096 6. Dez 12:28 proc
drwx------ 8 root root 4096 6. Dez 12:45 root
drwxr-xr-x 3 root root 12288 5. Dez 19:42 sbin
drwxr-xr-x 4 root root 4096 9. Dez 2008 srv
drwxr-xr-x 2 root root 4096 6. Dez 12:28 sys
drwxrwxrwt 12 root root 4096 6. Dez 12:47 tmp
drwxr-xr-x 12 root root 4096 9. Dez 2008 usr
drwxr-xr-x 15 root root 4096 9. Dez 2008 var

root@squeeze64:~# df
Dateisystem 1K‐Blöcke Benutzt Verfügbar Ben% Eingehängt auf
[...]
/dev/mapper/vg--prax1-suse111
                      20642428 3624736 15969116 19% /var/lib/vservers/suse111
[...]

root@squeeze64:~# cat /etc/vservers/suse111/fstab
none /proc proc defaults 0 0
#none /tmp tmpfs size=16m,mode=1777 0 0
#none /dev/pts devpts gid=5,mode=620 0 0

Any ideas? In http://linux-vserver.org/Installing_an_openSUSE_vserver_guest
there are some hints concerning SUSE, but it's a vserver problem here, isn't?
A Suse11.2 ist running on another machine without problems, I never patched
vserver.start.

tia
Ekkard
Received on Tue Dec 6 15:38:22 2011

[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Tue 06 Dec 2011 - 15:38:22 GMT by hypermail 2.1.8