Yes, I have that problem since version 0.26 sh -x ./vserver VSLPFRA1 stop:
+ /DBA/users/lang72/UTIL/sbin/chbind --ip 145.228.183.185 --bcast 145.228.205.255 /DBA/users/lang72/UTIL/sbin/chcontext --cap CAP_NET_RAW --secure --ctx 49153 /DBA/users/lang72/UTIL/lib/util-vserver/capchroot . /sbin/init 6 ipv4root is now 145.228.183.185 Can't set the new security context : Operation not permitted + test '' + echo sleeping 5 seconds sleeping 5 seconds + sleep 5 + echo Killing all processes Killing all processes + /DBA/users/lang72/UTIL/sbin/chbind --silent --ip 145.228.183.185 --bcast 145.228.205.255 /DBA/users/lang72/UTIL/sbin/chcontext --cap CAP_NET_RAW --secure --silent --ctx 49153 /DBA/users/lang72/UTIL/lib/util-vserver/vserverkillall Can't set the new security context : Operation not permitted And the same with "enter": + sh -x ./vserver VSLPFRA1 enter ++ dirname ./vserver + : ./util-vserver-vars + test -e ./util-vserver-vars + . ./util-vserver-vars ++ PKGLIBDIR=/DBA/users/lang72/UTIL/lib/util-vserver ++ SBINDIR=/DBA/users/lang72/UTIL/sbin ++ VROOTDIR=/vservers + USR_SBIN=/DBA/users/lang72/UTIL/sbin + USR_LIB_VSERVER=/DBA/users/lang72/UTIL/lib/util-vserver + VSERVER_CMD=/DBA/users/lang72/UTIL/sbin/vserver + CHBIND_CMD=/DBA/users/lang72/UTIL/sbin/chbind + CHCONTEXT_CMD=/DBA/users/lang72/UTIL/sbin/chcontext + SAVE_S_CONTEXT_CMD=/DBA/users/lang72/UTIL/lib/util-vserver/save_s_context + CAPCHROOT_CMD=/DBA/users/lang72/UTIL/lib/util-vserver/capchroot + VSERVERKILLALL_CMD=/DBA/users/lang72/UTIL/lib/util-vserver/vserverkillall + DEFAULTPATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin + SILENT= + NODEV= + true + '[' VSLPFRA1 = --silent ']' + '[' VSLPFRA1 = --nodev ']' + break + '[' 2 -lt 2 ']' + '[' enter = build ']' + '[' '!' -f /etc/vservers/VSLPFRA1.conf ']' + '[' '!' -d /vservers/VSLPFRA1/. ']' + '[' enter = start ']' + '[' enter = running ']' + '[' enter = status ']' + '[' enter = stop ']' + '[' enter = restart ']' + '[' enter = suexec ']' + '[' enter = exec ']' + '[' enter = enter ']' + testperm VSLPFRA1 + return + exec ./vserver VSLPFRA1 exec /bin/bash -login ipv4root is now 145.228.183.185 Can't set the new security context : Operation not permitted and the capbset: + grep CapBset /proc/self/status CapBset: 00000000fffffeff Regards Christian > -----Urspr�ngliche Nachricht----- > Von: Enrico Scholz [mailto:[EMAIL PROTECTED] > Gesendet: Donnerstag, 19. Februar 2004 14:20 > An: [EMAIL PROTECTED] > Betreff: Re: AW: [Vserver] still problems with util-vserver > 0.26 > > [EMAIL PROTECTED] writes: > > > The /vserver filesystem, where the images reside was mounted as > reiserfs. > > After changing it to ext2 (or ext3) I can start the vservers without > > problems. So it seems like reiserfs doesn't work with the util-vserver > > > 0.26. > > Have you tested 0.27 and 0.28 already? Are they failing too? > > What is the stop-command (execute 'sh -x `which vserver` ... stop' and > tell the line before 'Operation not permitted')? > > What gives 'grep CapBset /proc/self/status' in the shell executing the > 'vserver' command? > > > > Enrico > _______________________________________________ > Vserver mailing list > [EMAIL PROTECTED] > http://list.linux-vserver.org/mailman/listinfo/vserver _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
