Hello,

I followed the bug-report (http://bugs.gentoo.org/show_bug.cgi?id=138468) and remerged the dietlibc. Because of "-fno-stack-protector-all" in 0.28 i had to unmask >0.30 too. It didn't work - the same error appeared. While writing this email, i remerged util-vserver too. It works now!

What i want to say: It is necessary to reinstall the util-vserver after upgrading dietlibc.


PS: Why doesn't google find the bug-track :D

Greetings- Thomas


[ebuild R ] sys-cluster/util-vserver-0.30.211 USE="-bash-completion -legacy" 0 kB
[ebuild   R   ] dev-libs/dietlibc-0.30-r2  USE="-debug" 0 kB

Versions:
                  Kernel: 2.6.15-vs2.0.1-gentoo-r5
                  VS-API: 0x00020001
            util-vserver: 0.30.211; Oct 16 2006, 14:03:40

Features:
CC: x86_64-pc-linux-gnu-gcc, x86_64-pc-linux-gnu-gcc (GCC) 4.1.1 (Gentoo 4.1.1) CXX: x86_64-pc-linux-gnu-g++, x86_64-pc-linux-gnu-g++ (GCC) 4.1.1 (Gentoo 4.1.1)
                CPPFLAGS: ''
CFLAGS: '-O3 -pipe -fomit-frame-pointer -march=athlon64 -std=c99 -Wall -pedantic -W -funit-at-a-time' CXXFLAGS: '-O3 -pipe -fomit-frame-pointer -march=athlon64 -ansi -Wall -pedantic -W -fmessage-length=0 -funit-at-a-time'
              build/host: x86_64-pc-linux-gnu/x86_64-pc-linux-gnu
            Use dietlibc: yes
      Build C++ programs: yes
      Build C99 programs: yes
          Available APIs: v13,net
           ext2fs Source: e2fsprogs
   syscall(2) invocation: alternative
     vserver(2) syscall#: 236/glibc

Paths:
                  prefix: /usr
       sysconf-Directory: /etc
           cfg-Directory: /etc/vservers
        initrd-Directory: /etc/init.d
      pkgstate-Directory: /var/run/vservers
         vserver-Rootdir: /vservers



On Mon, Oct 16, 2006 at 03:30:19PM +0200, Thomas Duif wrote:
Hello,

I followed a vserver gentoo howto (http://www.gentoo.org/doc/en/vserver-howto.xml).
Everything was fine till vserver start:

~ # vserver gentoo-main start
exec-ulimit: execv(): Bad address

An error occured while executing the vserver startup sequence; when
there are no other messages, it is very likely that the init-script
(/sbin/init) failed.

Common causes are:
* /etc/rc.d/rc on Fedora Core 1 and RH9 fails always; the 'apt-rpm'
  build method knows how to deal with this, but on existing
  installations, appending 'true' to this file will help.


Failed to start vserver 'gentoo-main'

I dont have any idea what to do - google doesn't help.

_______________________________________________
Vserver mailing list
[email protected]
http://list.linux-vserver.org/mailman/listinfo/vserver

Reply via email to