Subject: Re: [vserver] Guest - problem on networking and exit
From: Herbert Poetzl <herbert@13thfloor.at>
Date: Thu, 28 Aug 2008 10:51:47 +0200

On Thu, Aug 28, 2008 at 02:46:52PM +0800, Stephen Liu wrote:
> 
> --- Nicolas Cadou <ncadou@cobi.net> wrote:
> 
> > > Please advise how to fix the problem.  Thanks
> > 
> > Some init scripts in your guest shouldn't be called. I use the
> > following 
> > command to clean my guests, at installation time, and also on a
> > regular basis 
> > because some updates seem to put back the rc symlinks once in a
> > while:
> > 
> > for s in \
> >   klogd hwclock.sh setserial urandom networking umountfs halt reboot
> > \
> >   mountvirtfs mountall.sh mountnfs.sh ifupdown; \
> > do \
> >     vserver <guest> exec update-rc.d -f $s remove
> > done
> 
> 
> # vserver vserver1 exec update-rc.d -f $s remove
> perl: warning: Setting locale failed.
> perl: warning: Please check that your locale settings:
>         LANGUAGE = (unset),
>         LC_ALL = (unset),
>         LANG = "en_US.UTF-8"

you are bringing your locale (en_US.UTF-8) into
a guest which doesn't have support for that

either update your util-vserver or install the
locales in your guest, or simply do:

 export LC_ALL=C LANG=C

>     are supported and installed on your system.
> perl: warning: Falling back to the standard locale ("C").
> usage: update-rc.d [-n] [-f] <basename> remove
>        update-rc.d [-n] <basename> defaults [NN | SS KK]
>        update-rc.d [-n] <basename> start|stop NN runlvl [runlvl] [...]
> .
>                 -n: not really
>                 -f: force
> done

> # vserver vserver1 stop
> Saving the system clock.
> Cannot access the Hardware Clock via any known method.
> Use the --debug option to see the details of our search for an access
> method.
> Stopping enhanced syslogd: rsyslogd.
> Asking all remaining processes to terminate...done.
> All processes ended within 1 seconds....done.
> Deconfiguring network interfaces...done.
> Cleaning up ifupdown....
> Unmounting temporary filesystems...umount: none: not found
> umount: /tmp: must be superuser to umount
> umount: none: not found
> umount: /tmp: must be superuser to umount
> failed.
> Deactivating swap...Not superuser.
> failed.
> mount: permission denied
> Will now restart.
> ifdown: shutdown eth0: Permission denied
> ifdown: shutdown eth0: Permission denied

the guest isn't cleaned up properly, you want to
remove any hardware related runlevel scripts,
including network and filesystem stuff

> Are those failure considered normal?  Thanks

for a 'raw' (not cleaned up) guest, yes

> > > Furthermore if I want to run update/upgrade with another website
> > other
> > > than http://ftp.de.debian.org/debian whether run;
> > >
> > > # vserver vserver1 exec apt-get update(or upgrade)
> > > http//ftp.xx.debian.org/debian ?
> > 
> > Yes, that's it. You could also used vapt-get on the host, which I
> > sometimes 
> > use to update all vservers at once, like this:
> > 
> > vapt-get --all -- update
> > vapt-get --all -- dist-upgrade
> 
> I can't find vpt-get on current Debian repo.

> $ which vapt-get
> No printout
> 
> $ apt-cache search vapt
> No printout
> 
> Which repo I have to add to get this package.  TIA

vapt-get is part of util-vserver (it's a wrapper)
if you are missing that one, please complain to
your debian maintainer ...

best,
Herbert

> B.R.
> Stephen
> 
> Send instant messages to your online friends http://uk.messenger.yahoo.com