On Mon, Sep 12, 2005 at 09:20:41AM +0200, Ola Lundqvist wrote:
> I do not have a recently patched kernel myself so in order to do this
> I need output from your /proc/... file.
i'm just testing kernel 2.6.15.1 + vserver 2.0.1
this working fine:
vserver v1 build --hostname v1.uvt.tuke.sk --interface eth0:10.1.5.6 \
-m debootstrap -- -d sarge -m http://ftp.sk.debian.org/debian
but newvserver fails:
newvserver error:
Must be run from the host server (security context 0)
on a "vserver/ctx-patch" enabled kernel
See: http://www.solucorp.qc.ca/miscprj/s_context.hc
vserver-stat
CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME
0 72 73.4M 17.2M 0m09s95 0m06s48 1h04m31 root server
49152 7 126.2M 20.3M 0m00s80 0m00s18 53m49s25 v1
util-vserver 0.30.209-2
vserver-debiantools 0.2.5
debootstrap 0.2.45-0.2
cat /proc/self/status
Name: cat
State: R (running)
SleepAVG: 88%
Tgid: 3512
Pid: 3512
PPid: 2462
TracerPid: 0
Uid: 0 0 0 0
Gid: 0 0 0 0
FDSize: 256
Groups: 0
VmPeak: 1576 kB
VmSize: 1576 kB
VmLck: 0 kB
VmHWM: 364 kB
VmRSS: 364 kB
VmData: 148 kB
VmStk: 88 kB
VmExe: 16 kB
VmLib: 1280 kB
VmPTE: 12 kB
Threads: 1
SigQ: 0/16383
SigPnd: 0000000000000000
ShdPnd: 0000000000000000
SigBlk: 0000000000000000
SigIgn: 0000000000000000
SigCgt: 0000000000000000
CapInh: 0000000000000000
CapPrm: 00000000fffffeff
CapEff: 00000000fffffeff
VxID: 0
ipv4root: 0
ipv4root_bcast: 0
i tried patch newvserver:
--- /usr/sbin/newvserver 2006-01-20 13:59:23.000000000 +0100
+++ /usr/sbin/newvserver2 2006-01-20 14:19:30.000000000 +0100
@@ -342,7 +342,7 @@
# Dist specific issues
##############################################################################
-if ! cat /proc/self/status | grep '^s_context:[^0-9]0$'; then
+if ! cat /proc/self/status | grep '^VxID:[^0-9]0$'; then
echo "${0##*/} error:"
echo " Must be run from the host server (security context 0)" 1>&2
echo ' on a "vserver/ctx-patch" enabled kernel' 1>&2
newvserver2 --hostname v2 --domain uvt.tuke.sk --ip 10.5.6.3
VxID: 0
E: No such script: http://ftp.uk.debian.org/debian
/usr/sbin/newvserver2: line 399:
/etc/vservers/.defaults/vdirbase/v2/etc/apt/sources.list: No such file or
directory
mv: cannot stat `/etc/vservers/.defaults/vdirbase/v2/etc/inittab': No such file
or directory
secure-mount: chdir("/tmp"): No such file or directory
/etc/vservers/v2/fstab:2:1: failed to mount fstab-entry
find: var/run: No such file or directory
fakerunlevel: open("/var/run/utmp"): No such file or directory
Failed to start vserver 'v2'
'vserver ... suexec' is supported for running vservers only; aborting...
vserver 'v2' is not running
You should now adjust the configuration in /etc/vservers/v2/
to suit your needs,
or else just go ahead and type `vserver v2 start' to start
your new virtual server. debian/rules!
again:
newvserver2 --hostname v2 --domain uvt.tuke.sk --ip 10.5.6.3
VxID: 0
/etc/vservers/.defaults/vdirbase/v2/dev
/usr/lib/util-vserver/vserver-build: line 206: -n: command not found
newvserver2: error: vserver-build failure. Cannot continue.
so newvserver script must be adjust to new requirements for vserver 2.0.x (2.x)
--
5o Peter.Mann at tuke.sk
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
