Thank you for replying Herbert.
Herbert Poetzl wrote:
> 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?
>
[toor util-vserver-0.30.210]# ./testme.sh
Linux-VServer Test [V0.15] Copyright (C) 2003-2006 H.Poetzl
chcontext is working.
chbind is working.
Linux 2.6.17.7-vs2.0.2-rc28 #2 SMP Fri Aug 11 14:05:42 EDT 2006 i686
Ea 0.30.210 273/glibc (DSa) <v13,net>
VCI: 0002:0001 273 03000076 (TbLgnP)
---
[000]# succeeded.
[001]# succeeded.
[011]# succeeded.
[031]# succeeded.
[101]# succeeded.
[102]# succeeded.
[201]# succeeded.
[202]# succeeded.
>> 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)
>>
8< --- sorry about that --- 8<
> 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
>
That's just it. I didn't change anything. I am following the same
process that I did when I created the other servers.
I install with CentOS 4.3, don't update, and follow the process on those
mentioned links.
I am about to try running a downloaded vserver on this machine.
Is there a way to activate more detailed debugging to give more info as
to why it's failing the yum?
TIA, (hadn't used this one before, assuming "Thanks In Advance")
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
Received on Mon Aug 14 15:58:14 2006