Re: Problem entering a vserver

On Mon, Aug 16, 2004 at 10:38:38AM +0200, Mike Fischer wrote:
> Greetings,
> 
> I set up a new one:
> # testme.sh
> Linux-VServer Test [V0.07] (C) 2003-2004 H.Poetzl
> chcontext is working.
> chbind is working.
> Linux 2.4.26-vs1.28 i686/0.30/0.30 [E]
> ---
> [001]# succeeded.
> [011]# succeeded.
> [031]# succeeded.
> [101]# succeeded.
> [102]# succeeded.
> [201]# failed.
> [202]# failed.

should not happen ...

Linux-VServer Test [V0.07] (C) 2003-2004 H.Poetzl
chcontext is working.
chbind is working.
Linux 2.4.26-vs1.28 i686/0.30/0.30 [E]
---
[001]# succeeded.
[011]# succeeded.
[031]# succeeded.
[101]# succeeded.
[102]# succeeded.
[201]# succeeded.
[202]# succeeded.

> # vserver test01 enter
> ipv4root is now 141.12.26.105
> Host name is now libra-iv
> New security context is 49166
> Can't chroot to directory . (Operation not permitted)

maybe the result of the broken kernel/userspace?
maybe just a simple permission issue on the
vserver directory? what does ls -lad /path/to/vserver
give?

best,
Herbert

> Any help anyone?
> 
> Kind regards,
> Mike Fischer
> -- 
> Fraunhofer Gesellschaft e.V.
> IPSI.ITI
> 
> Dolivostr. 15
> 64293 Darmstadt
> Telefon: 06151 / 869 - 845
> 
> _______________________________________________
> Vserver mailing list
> Vserver@xxxxxxxxxxxxxxxxxxxxxx
> http://list.linux-vserver.org/mailman/listinfo/vserver
_______________________________________________
Vserver mailing list
Vserver@xxxxxxxxxxxxxxxxxxxxxx
http://list.linux-vserver.org/mailman/listinfo/vserver