[Vserver] I think I goofed
i just copied my template into 3 other vservers using hard link cloning along
with copying real files into the etc and var. they run ok however I now get
an error on start I never got before. I hope I didn't goof using the setattr
command. error listed next
davin etc # /etc/init.d/vservers start
* Starting all vservers ...
chroot-shopen("/etc/mtab"): Permission denied
secure-mount: open(): Permission denied
Failed to update mtab-file
secure-mount: open(): Permission denied
Failed to update mtab-file
secure-mount: open(): Permission denied
Failed to update mtab-file
i just tried setting the attrs mount option on my host / to see if that cures
it. didn't have this until I made the 3 other vservers.
finished reboot and that didn't cure anything :(
I will say this though in converting my 3 vservers into hard linked clones
all 4 servers including the template now take up 1/3 the amount of space they
did before this :)
--
Chuck
"...and the hordes of M$*ft users descended upon me in their anger,
and asked 'Why do you not get the viruses or the BlueScreensOfDeath
or insecure system troubles and slowness or pay through the nose
for an OS as *we* do?!!', and I answered...'I use Linux'. "
The Book of John, chapter 1, page 1, and end of book
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] strange yum build errror
Hi there, on Donnerstag, 15. September 2005 at 18:31 on the list was posted: > somehow looks like a broken repository ... looks more like _no_ repository beeing used although they are placed in the util-vserver configuration. Btw: placing the "yum" files into /etc/vservers/.distributions/fc4/yum/... does not change this error. > sounds like external vs. internal package management > again, just guessing ... As this is the "build" option beeing used, it should completely beeing build by external package management. So you're right, ther's not necessarely anything inside the gust. Checking the .pkg dir reveals everything beeing there as it should: /vsr/.pkg/xxx/yum contains "cache" and "etc", "etc" containing the conf and a proper link to the repos dir. So everything looking fine, except yum not beeing able to find the repos - even more strange now than before -- regards, Guenther Fuchs ___ Vserver mailing list Vserver@list.linux-vserver.org http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] strange yum build errror
On Thu, Sep 15, 2005 at 02:26:40PM +0200, Guenther Fuchs wrote:
> Hi there,
>
> although I remember having successfully built guests I cannot manage
> to reproduce this for some unknown reason.
>
> Sys: Amd64/vs 2.0/tools 0.30.208 (with and w/o fix02)
>
> build command:
> # vserver xxx build -m yum --hostname xxx.example.com -- -d fc4
>
> Error from that:
> > No Repositories Available to Set Up
> > No Match for argument: glibc
> > No Repositories Available to Set Up
> > No Match for argument: filesystem
> > No Repositories Available to Set Up
> > No Match for argument: coreutils
> > No Match for argument: setup
> > chroot-shopen("/etc/sysconfig/network"): No such file or directory
> > chroot-shopen("etc/inittab"): No such file or directory
somehow looks like a broken repository ... but I'm
not very good with yum so I might be completely wrong
here, Enrico?
> Checking sources: /lib/util-vserver/distributions/fc4/ has it's
> repositories proper setup at yum.repos.de/*.repo - they where copied
> from a working fc4 host dir ...
>
> Strange, very strange - checking the result: /vsr/xxx/etc/ has no
> yum.repos.de and no yum.conf getting copied
sounds like external vs. internal package management
again, just guessing ...
> Anoyone any ideas?
best,
Herbert
> --
> regards,
>
> Guenther Fuchs
>
> ___
> Vserver mailing list
> Vserver@list.linux-vserver.org
> http://list.linux-vserver.org/mailman/listinfo/vserver
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
Re: [Vserver] Proc Security in V2.0
Onsdag 14 september 2005 16:22, skrev Herbert Poetzl: > On Wed, Sep 14, 2005 at 09:52:58AM +0200, Tor Rune Skoglund wrote: > > linuxserver ~ # ./vserver-oppsett/testme.sh > > Linux-VServer Test [V0.13] Copyright (C) 2003-2005 H.Poetzl > > chcontext is working. > > chbind is working. > > Linux 2.6.13-vs2.1.0-pre5-gentoo i686/0.30.208/0.30.208 [Ea] (0) > > VCI: 0002:0001 273 03110036 > > --- > > [000]# succeeded. > > [001]# succeeded. > > [011]# succeeded. > > [031]# succeeded. > > [101]# succeeded. > > [102]# succeeded. > > [201]# succeeded. > > [202]# succeeded. > > hmm ... not conclusive yet, if you are interested in tracking > down this issue, you might pay a visit to the irc channel > #vserver @ irc.oftc.net Hello Herbert, OK, I can confirm that the problem is still there on a pre8 kernel. (uname btw says pre7...) No change, it might be some Gentoo specially somewhere, but finding this is beyond my capabilities... If you like, Herbert, I can give you ssh access to a server with a testinstalled server with the problem. Let me know by mail if you like to check it out. Best regards Tor Rune > > Onsdag 14 september 2005 00:56, skrev Herbert Poetzl: > > > On Tue, Sep 13, 2005 at 11:39:10PM +0200, Tor Rune Skoglund wrote: > > > > Søndag 11 september 2005 04:08, skrev Herbert Poetzl: > > > > > > "A timeout occured while waiting for the vserver to finish and it > > > > > > was > > > > > > killed by sending a SIGKILL signal. Please investigate the reasons > > > > > > and/or increase the timeout in apps/vshelper/sync-timeout." > > > > > > > > > > > > on vserver xxx stop. I'm not sure how to debug this. > > > > > > > > > > well, for some reason the guest has still programs > > > > > running after a shutdown, best check with 'vps auxwww' > > > > > and look for processes inside your guest (while waiting > > > > > for the timeout to occur) > > > > > > > > OK, you experts have a look at this: > > > > > > > > First, minimizing the processes in the vserver to: > > > > > > > > templategentoo / # ps ax > > > > PID TTY STAT TIME COMMAND > > > > 1 ?S 0:00 init [3] > > > > 17335 pts/1S 0:00 /bin/bash -login > > > > 17429 pts/1R+ 0:00 ps ax > > > > templategentoo / # > > > > > > > > Then checking vps on the host: > > > > > > > > linuxserver ~ # vps auxwww | grep 100 > > > > root 1008 0 MAIN 0.0 0.0 1444 468 ?S > > > Sep11 > > > > 0:00 udevd > > > > root 16616 100 templategentoo 0.0 0.0 1464 496 ?Ss > > > > 23:17 > > > > 0:00 init [3] > > > > root 17335 100 templategentoo 0.0 0.1 2328 1368 pts/1S+ > > > > 23:17 > > > > 0:00 /bin/bash -login > > > > root 17460 0 MAIN 0.0 0.0 1484 452 pts/8S+ > > > > 23:20 > > > > 0:00 grep 100 > > > > > > > > Stopping the vserver from the host: > > > > > > > > linuxserver ~ # vserver templategentoo stop > > > > A timeout occured while waiting for the vserver to finish and it was > > > > killed by sending a SIGKILL signal. Please investigate the reasons > > > > and/or increase the timeout in apps/vshelper/sync-timeout. > > > > > > > > Before that timeout arrives, checking vps repeatedly from the host: > > > > > > > > linuxserver ~ # vps auxwww | grep 100 > > > > root 1008 0 MAIN 0.0 0.0 1444 468 ?S > > > Sep11 > > > > 0:00 udevd > > > > root 16616 100 templategentoo 0.0 0.0 1464 496 ?Ss > > > > 23:17 > > > > 0:00 init [3] > > > > root 17335 100 templategentoo 0.0 0.1 2328 1368 pts/1S+ > > > > 23:17 > > > > 0:00 /bin/bash -login > > > > root 17556 0 MAIN 0.0 0.010828 pts/6S+ > > > > 23:20 > > > > 0:00 /usr/sbin/vwait --timeout 20 --terminate --status-fd 3 100 > > > > root 17612 0 MAIN 0.0 0.0 1484 448 pts/8S+ > > > > 23:20 > > > > 0:00 grep 100 > > > > > > > > vwait just waits 20 seconds, and then the vserver is killed. > > > > > > > > So I checked to see if it stops the services gracefully first: It > > > > doesn't. It > > > > just > > > > goes into that timeout directly without the stopping the init.d scripts: > > > > > > > > linuxserver ~ # vps auxwww | grep 100 > > > > root 1008 0 MAIN 0.0 0.0 1444 468 ?S > > > Sep11 > > > > 0:00 udevd > > > > root 17832 100 templategentoo 0.0 0.0 1468 500 ?Ss > > > > 23:29 > > > > 0:00 init [3] > > > > root 18403 100 templategentoo 0.0 0.0 1712 664 ?Ss > > > > 23:29 > > > > 0:00 /usr/sbin/syslog-ng > > > > root 18499 100 templategentoo 0.0 0.1 3944 1644 ?Ss > > > > 23:29 > > > > 0:00 /usr/sbin/sshd > > > > root 18522 100 templategentoo 0.0 0.3 7652 3296 ?Ss > > > > 23:29 > > > > 0:00 /usr/sbin/apache2 -k start > > > > apache 18558 100 templategentoo 0.0 0.3 7596 3252 ?S > > > > 23
[Vserver] strange yum build errror
Hi there,
although I remember having successfully built guests I cannot manage
to reproduce this for some unknown reason.
Sys: Amd64/vs 2.0/tools 0.30.208 (with and w/o fix02)
build command:
# vserver xxx build -m yum --hostname xxx.example.com -- -d fc4
Error from that:
> No Repositories Available to Set Up
> No Match for argument: glibc
> No Repositories Available to Set Up
> No Match for argument: filesystem
> No Repositories Available to Set Up
> No Match for argument: coreutils
> No Match for argument: setup
> chroot-shopen("/etc/sysconfig/network"): No such file or directory
> chroot-shopen("etc/inittab"): No such file or directory
Checking sources: /lib/util-vserver/distributions/fc4/ has it's
repositories proper setup at yum.repos.de/*.repo - they where copied
from a working fc4 host dir ...
Strange, very strange - checking the result: /vsr/xxx/etc/ has no
yum.repos.de and no yum.conf getting copied
Anoyone any ideas?
--
regards,
Guenther Fuchs
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
