On Fri, Aug 11, 2006 at 12:51:35PM -0400, Gregory L Miller-Kramer wrote:
> TWIMC, (To Whom It May Concern)
>
> I have done this before (VServers and CentOS) and I have created
> quite a few VServers in the past. So, I am retracing familiar steps.
>
> I installed CentOS 4.3, NO SELinux, and no GUI. I followed the best
> set of steps for creating a CentOS VServer Host.
> (http://linux-vserver.org/CentOS_HowTo and
> http://linux-vserver.org/Step-by-Step+Guide+2.6) I do the step where I
> will be taking a coffee break :-) while the host downloads (and
> installs) all the RPM's via Yum and it fails. So, no coffee :-( .
>
> vserver min-centos4 build -m yum --hostname domain.com --interface
> domain=eth0:192.168.0.136/24 --initstyle sysv --context 500 --force -- -d
> centos4
>
> I get this...
> rpm-fake-resolver: vc_ctx_migrate(): No such process
> rpm-fake.so: failed to initialize communication with resolver
could you run testme.sh and add the output here too?
> I have looked throughout google and the vserver lists but nothing
> useful. This did work about 2 months ago because I followed the steps
> and was able to do it when I created another machine. The machines are
> physically different but I don't see how that would cause this.
>
> I used dietlibc and when I did the configure of 0.30.210 (util-vserver)
> I get this. ( it is long, sorry)
> [root@SysNm util-vserver-0.30.210]# ./configure --prefix=/usr
> --sysconfdir=/etc --with-vrootdir=/vservers
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for gawk... gawk
> checking whether make sets $(MAKE)... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking build system type... i686-pc-linux-gnu
> checking host system type... i686-pc-linux-gnu
> checking for g++... g++
> checking for C++ compiler default output file name... a.out
> checking whether the C++ compiler works... yes
> checking whether we are cross compiling... no
> checking for suffix of executables...
> checking for suffix of object files... o
> checking whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking for style of include used by make... GNU
> checking dependency style of g++... gcc3
> checking for gcc... gcc
> checking whether we are using the GNU C compiler... yes
> checking whether gcc accepts -g... yes
> checking for gcc option to accept ANSI C... none needed
> checking dependency style of gcc... gcc3
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether ln -s works... yes
> checking whether gcc and cc understand -c and -o together... yes
> checking whether g++ is a C++ compiler... yes
> checking whether gcc is a C99 compiler... yes
> checking for awk... /bin/awk
> checking for cat... /bin/cat
> checking for chown... /bin/chown
> checking for cmp... /usr/bin/cmp
> checking for cp... /bin/cp
> checking for dirname... /usr/bin/dirname
> checking for egrep... /bin/egrep
> checking for env... /bin/env
> checking for grep... /bin/grep
> checking for ln... /bin/ln
> checking for mkdir... /bin/mkdir
> checking for mkfifo... /usr/bin/mkfifo
> checking for mktemp... /bin/mktemp
> checking for mount... /bin/mount
> checking for mv... /bin/mv
> checking for nice... /bin/nice
> checking for ps... /bin/ps
> checking for rm... /bin/rm
> checking for rmdir... /bin/rmdir
> checking for sed... /bin/sed
> checking for sh... /bin/sh
> checking for tac... /usr/bin/tac
> checking for tar... /bin/tar
> checking for touch... /bin/touch
> checking for tty... /usr/bin/tty
> checking for umount... /bin/umount
> checking for wc... /usr/bin/wc
> checking for ip... /sbin/ip
> checking for iptables... /sbin/iptables
> checking for modprobe... /sbin/modprobe
> checking for nameif... /sbin/nameif
> checking for nohup... /usr/bin/nohup
> checking for rmmod... /sbin/rmmod
> checking for vconfig... /sbin/vconfig
> checking for wget... /usr/bin/wget
> checking for doxygen... /usr/bin/doxygen
> checking for xsltp... no
> checking for xsltproc... /usr/bin/xsltproc
> checking whether the C-compiler accepts -Werror -W... yes
> checking whether gcc accepts -std=c99... yes
> checking whether gcc accepts -Wall... yes
> checking whether gcc accepts -pedantic... yes
> checking whether gcc accepts -W... yes
> checking whether the C++-compiler accepts -Werror -W... yes
> checking whether g++ accepts -ansi... yes
> checking whether g++ accepts -Wall... yes
> checking whether g++ accepts -pedantic... yes
> checking whether g++ accepts -W... yes
> checking whether g++ accepts -fmessage-length=0... yes
> checking whether to enable extra optimizations... yes
> checking whether gcc accepts -funit-at-a-time... yes
> checking whether g++ accepts -funit-at-a-time... yes
> checking whether to enable debug-code in library... no
> checking whether to enable expensive tests... no
> checking for declarations in <linux/personality.h>...
> checking whether MMAP_PAGE_ZERO is declared... yes
> checking whether ADDR_LIMIT_32BIT is declared... yes
> checking whether SHORT_INODE is declared... yes
> checking whether WHOLE_SECONDS is declared... yes
> checking whether STICKY_TIMEOUTS is declared... yes
> checking whether ADDR_LIMIT_3GB is declared... yes
> checking whether PER_LINUX is declared... yes
> checking whether PER_LINUX_32BIT is declared... yes
> checking whether PER_SVR4 is declared... yes
> checking whether PER_SVR3 is declared... yes
> checking whether PER_SCOSVR3 is declared... yes
> checking whether PER_OSR5 is declared... yes
> checking whether PER_WYSEV386 is declared... yes
> checking whether PER_ISCR4 is declared... yes
> checking whether PER_BSD is declared... yes
> checking whether PER_SUNOS is declared... yes
> checking whether PER_XENIX is declared... yes
> checking whether PER_LINUX32 is declared... yes
> checking whether PER_LINUX32_3GB is declared... yes
> checking whether PER_IRIX32 is declared... yes
> checking whether PER_IRIXN32 is declared... yes
> checking whether PER_IRIX64 is declared... yes
> checking whether PER_RISCOS is declared... yes
> checking whether PER_SOLARIS is declared... yes
> checking whether PER_UW7 is declared... yes
> checking whether PER_HPUX is declared... yes
> checking whether PER_OSF4 is declared... yes
> checking for initrddir... $(sysconfdir)/init.d
> checking whether to enable release-mode... no
> checking whether to enable dietlibc... yes (autodetected, 0.28)
> checking whether dietlibc supports C99... yes
> checking whether to use alternative _syscallX macros... yes
> checking whether dietlibc needs '-lcompat'... no
> checking for a sed that does not truncate output... /bin/sed
> checking for egrep... grep -E
> checking for ld used by gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/bin/ld option to reload object files... -r
> checking for BSD-compatible nm... /usr/bin/nm -B
> checking how to recognise dependent libraries... pass_all
> checking how to run the C preprocessor... gcc -E
> checking for ANSI C header files... yes
> checking for sys/types.h... yes
> checking for sys/stat.h... yes
> checking for stdlib.h... yes
> checking for string.h... yes
> checking for memory.h... yes
> checking for strings.h... yes
> checking for inttypes.h... yes
> checking for stdint.h... yes
> checking for unistd.h... yes
> checking dlfcn.h usability... yes
> checking dlfcn.h presence... yes
> checking for dlfcn.h... yes
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... g77
> checking whether we are using the GNU Fortran 77 compiler... yes
> checking whether g77 accepts -g... yes
> checking the maximum length of command line arguments... 32768
> checking command to parse /usr/bin/nm -B output from gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if gcc static flag works... yes
> checking if gcc supports -fno-rtti -fno-exceptions... no
> checking for gcc option to produce PIC... -fPIC
> checking if gcc PIC flag -fPIC works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the gcc linker (/usr/bin/ld) supports shared
> libraries... yes
> checking whether -lc should be explicitly linked in... no
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared
> libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> appending configuration tag "F77" to libtool
> checking if libtool supports shared libraries... yes
> checking whether to build shared libraries... yes
> checking whether to build static libraries... no
> checking for g77 option to produce PIC... -fPIC
> checking if g77 PIC flag -fPIC works... yes
> checking if g77 supports -c -o file.o... yes
> checking whether the g77 linker (/usr/bin/ld) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> checking whether stripping libraries is possible... yes
> checking which vserver-rootdir is to use... /vservers
> checking for cvs2cl... no
> checking for rcs2log... rcs2log
> checking whether to use internal kernel headers... yes
> checking for supported APIs... v13,net
> checking for number of syscall 'vserver'... 273/glibc
> checking for syscall(2) invocation method... auto
> checking which syscall(2) invocation works... fast
> checking for ext2fs-headers... e2fsprogs
> checking ext2fs/ext2_fs.h usability... yes
> checking ext2fs/ext2_fs.h presence... yes
> checking for ext2fs/ext2_fs.h... yes
> checking for vserver... no
> checking whether MS_MOVE is declared... no
> checking for xid_t... no
> checking for nid_t... no
> checking sys/capability.h usability... yes
> checking sys/capability.h presence... yes
> checking for sys/capability.h... yes
> checking beecrypt/beecrypt.h usability... yes
> checking beecrypt/beecrypt.h presence... yes
> checking for beecrypt/beecrypt.h... yes
> checking for hashFunctionContextInit in -lbeecrypt... yes
> configure: creating ./config.status
> config.status: creating util-vserver.spec
> config.status: creating Makefile
> config.status: creating distrib/Makefile
> config.status: creating lib/apidoc/Doxyfile
> config.status: creating config.h
> config.status: config.h is unchanged
> config.status: executing depfiles commands
> configure:
>
the part below is usually sufficient, and you
can easily get it with vserver-info - SYSINFO
(JFYI)
> util-vserver 0.30.210
>
> Features:
> CC: gcc, gcc (GCC) 3.4.5 20051201 (Red Hat 3.4.5-2)
> CXX: g++, g++ (GCC) 3.4.5 20051201 (Red Hat 3.4.5-2)
> CPPFLAGS: ''
> CFLAGS: '-g -O2 -std=c99 -Wall -pedantic -W
> -funit-at-a-time'
> CXXFLAGS: '-g -O2 -ansi -Wall -pedantic -W
> -fmessage-length=0 -funit-at-a-time'
> build/host: i686-pc-linux-gnu/i686-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#: 273/glibc
>
> Paths:
> prefix: /usr
> sysconf-Directory: /etc
> cfg-Directory: /etc/vservers
> initrd-Directory: $(sysconfdir)/init.d
> pkgstate-Directory: ${prefix}/var/run/vservers
> vserver-Rootdir: /vservers
>
> I should also note, it's the same version for kernel, vserver patch and
> util-vserver as the previous machines I have working.
so _what_ exactly changed?
TIA,
Herbert
> Please help.
>
> Thank you,
> Greg
>
>
> --
> This message has been scanned for viruses and
> dangerous content, and is believed to be clean.
>
> _______________________________________________
> 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
Received on Mon Aug 14 04:40:15 2006