Msg06308.html: Difference between revisions
(Restored content from Wayback Machine) |
(No difference)
|
Latest revision as of 23:10, 10 November 2025
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Vserver] chroot - permission denied[edit]
- From: Schlomo Schapiro
- Date: Wed, 25 Feb 2004 14:42:35 +0100 (CET)
Hi all,
I just installed VServer on my SuSE9.0 box and compiled a new 2.4.25 kernel with the OpenWall patches included.
The vserver kernel subsystems seems to be there (checked with e.g. vps -ax)
I then downloaded the debian vserver to start testing and it won't start with this message:
----------------------------------------------------------------------------------- # vserver debian start Starting the virtual server debian Server debian is not running ipv4root is now 10.1.1.34 Host name is now gss34.mikado.local Domain name is now New security context is 49175 Can't chroot to directory . (Operation not permitted) -----------------------------------------------------------------------------------
I started to play around with the chcontext tool and got a very strange thing: The CAP_SYS_CHROOT capability is not present !:
--------------------------------------------------------------------------------
# /usr/sbin/chcontext --ctx 49176 bash -c 'getpcaps $$'
New security context is 49176
Capabilities for `4337': = cap_chown,cap_dac_override,cap_dac_read_search,cap_setgid,cap_setuid,cap_net_broadcast,cap_sys_resource,cap_sys_time,cap_sys_tty_config,cap_mknod,cap_lease+ep
---------------------------------------------------------------------------------
When I do not give the --ctx parameter, all capabilities are present: --------------------------------------------------------------------------------- # /usr/sbin/chcontext bash -c 'getpcaps $$' New security context is 49176 Capabilities for `4334': =ep cap_setpcap-ep ----------------------------------------------------------------------------------
That seems to be the reason why the vserver start command does not work.
Do you have any ideas what yould be the problem ?
Some more questions:
* What about virtualized localhosts ? How can I give each vserver a private localhost(127.0.0.1) ?
* I am running samba in a chbind environment, however nmbd complains about not beeing able to bind to the IPs of the other vservers and doesn't start when I have any IP aliases defined. The error log looks like this:
------------------------------------------------------------------------------------
[2004/02/25 12:51:03, 0] nmbd/nmbd.c:main(795)
Netbios nameserver version 2.2.8a-SuSE started.
Copyright Andrew Tridgell and the Samba Team 1994-2002
[2004/02/25 12:51:03, 1] lib/debug.c:debug_message(258)
INFO: Debug class all level = 1 (pid 3587 from pid 3587)
[2004/02/25 12:51:03, 0] lib/util_sock.c:open_socket_in(804)
bind failed on port 137 socket_addr = 10.1.1.34.
Error = Cannot assign requested address
[2004/02/25 12:51:03, 0] nmbd/nmbd_subnetdb.c:make_subnet(139)
nmbd_subnetdb:make_subnet()
Failed to open nmb socket on interface 10.1.1.34 for port 137. Error was Cann
ot assign requested address
[2004/02/25 12:51:03, 0] nmbd/nmbd.c:main(873)
ERROR: Failed when creating subnet lists. Exiting.
------------------------------------------------------------------------------------
10.1.1.34 is the IP alias added by the debian vserver I tried to run. I thought that chbind was supposed to prevent vservers from seeing other IPs ? Is there a solution to this nmb problem ?
Thanks a lot for any help, Schlomo
- Prev by Date: Re: [Vserver] doesnt compile :( sparc64 - linux-2.6.3 + patch-2.6.3-vs0.09.diff
- Next by Date: [Vserver] vshelper works!
- Previous by thread: [Vserver] doesnt compile :( sparc64 - linux-2.6.3 + patch-2.6.3-vs0.09.diff
- Next by thread: Re: [Vserver] chroot - permission denied
- Index(es):