Re: [vserver] Jessie vserver guest issue

On Tue, 3 Feb 2015 11:06:48 +0000
Phil D <splatnix@gmail.com> wrote:

> Hello all:
>
> have started testing out the Jessie build but hit an issue. First, here is
> what I have installed on a vanilla Jessie system:

i use a vanilla wheezy system for testing and deployment.

> root@jessie-test:~# dpkg -l |grep vserver
> ii libvserver0 0.30.216-pre3062-jessie0.1-1 amd64
> dynamic libraries for util-vserver
> ii linux-headers-vserver-3.18-beng 3.18.4-2.3.7.1+jessie1 amd64
> A metapackage which installs the latest Linux-Vserver patched 3.18
> linux-headers package, BenG's build.
> ii linux-image-vserver-3.18-beng 3.18.4-2.3.7.1+jessie1 amd64
> A metapackage which installs the latest Linux-Vserver patched 3.18
> linux-image package, BenG's build.
> ii util-vserver 0.30.216-pre3062-jessie0.1-1 amd64
> utilities for managing Linux-VServer guests
> ii util-vserver-build 0.30.216-pre3062-jessie0.1-1 amd64
> tools which can be used to build vservers
> ii util-vserver-core 0.30.216-pre3062-jessie0.1-1 amd64
> core utilities of util-vserver
> ii util-vserver-sysv 0.30.216-pre3062-jessie0.1-1 amd64
> initscripts for util-vserver
> ii vserver-debiantools 0.8.1 all
> Tools to manage Debian virtual servers

i have 3.18.5-vs2.3.7.1 and 0.30.216-pre3097 installed.

i previously had 0.30.216-pre3054 installed with 3.10 and 3.14, but never
0.30.216-pre3062.

> I then rebooted the system and vserver-stat responded okay. Then went on
> to build a guest:
>
> vserver base_jessie build \
> -m debootstrap \
> --context 40001 \
> --hostname vserver1.mydomain.com \
> --interface eth0:192.168.1.84/24 \
> -- -d jessie -m http://ftp.de.debian.org/debian

i haven't built a new guest with any recent util-vserver version as i just
keep using the same old (but upgraded) guest through the years, for better or
worse.

> that completed fine so I then went on to start it and this is what happens:
>
> root@jessie-test:~# vserver base_jessie start
> Using makefile-style concurrent boot in runlevel 3.
> Starting enhanced syslogd: rsyslogd.
> Starting periodic command scheduler: cron.
>
> root@jessie-test:~# vserver-stat
> WARNING: can not access /proc/uptime. Usually, this is caused by
> procfs-security. Please read the FAQ for more details
> http://linux-vserver.org/Proc-Security
> open("/proc/uptime"): No such file or directory
> root@jessie-test:~# uptime
> Error: /proc must be mounted
> To mount /proc at boot you need an /etc/fstab line like:
> proc /proc proc defaults
> In the meantime, run "mount proc /proc -t proc"
>
> Would appear that /proc is being wiped out.

i wouldn't say "wiped out" but maybe unmounted.

i definitely haven't had your problem.

maybe the output of "vserver --debug base_jessie start" would reveal
something.

corey

--
undefined@pobox.com
> How may I resolve the issue please ?
> 
> Thanks, Phil