|
|
|
|
|
Re: Compatibility: FC9 [message #32594 is a reply to message #31289] |
Mon, 18 August 2008 17:13 |
neutrino38
Messages: 3 Registered: August 2008 Location: Grenoble, France
|
Junior Member |
|
|
Well I went one step further:
Using cat /proc/user_beancounters I was able to determine that there is not enough dcachemem available.
I edited /etc/vz/conf/101.conf and increased the parameter.
Then I was able to start the VPS but the network was not started and when I start it using
/usr/sbin/vzctl exec 101 /etc/init.d/network start
I get some error messages:
[root@erp ~]# /etc/init.d/network restart
Shutting down interface venet0: [ OK ]
Shutting down loopback interface: [ OK ]
Cannot find device "sit0"
Bringing up loopback interface: Error, some other host already uses address 127.0.0.1.
[FAILED]
Bringing up interface venet0: SIOCADDRT: No such process
[ OK ]
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
RTNETLINK answers: File exists
I am able to launch sshd then and connnect using SSH. But the internet access does not work although it works on the node. Here are a few more information:
[root@erp ~]# netstat -r
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.0.2.0 * 255.255.255.0 U 0 0 0 venet0
link-local * 255.255.0.0 U 0 0 0 venet0
172.21.0.0 * 255.255.0.0 U 0 0 0 venet0
default 192.0.2.1 0.0.0.0 UG 0 0 0 venet0
[root@erp ~]# /sbin/ifconfig -a
lo Link encap:Local Loopback
LOOPBACK MTU:16436 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
venet0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:127.0.0.3 P-t-P:127.0.0.3 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:884 errors:0 dropped:0 overruns:0 frame:0
TX packets:754 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:68416 (66.8 KiB) TX bytes:102968 (100.5 KiB)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:172.21.100.7 P-t-P:172.21.100.7 Bcast:172.21.100.7 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
I do not understand why the default gateway and the routing tables are setup like this. Anyway, I fail to access the Internet from the VPS.
--
Emmanuel
|
|
|
Re: Compatibility: FC9 - problem partially solved [message #32600 is a reply to message #32594] |
Mon, 18 August 2008 20:46 |
neutrino38
Messages: 3 Registered: August 2008 Location: Grenoble, France
|
Junior Member |
|
|
Ok,
After stopping IP tables on the VPS, I was able to access the outside network and all the rest despite all the ugly error message s associated with network startup.
But then something strange happens:
1/ I had to launch ssh manually in the VPS (using vzctl exec)
1/ yum hangs. When we interrupt it with CTRL-C, here is the backtrace generated
[root@erp ~]# yum install vim
Traceback (most recent call last):
File "/usr/bin/yum", line 4, in <module>
import yum
File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 40, in <module>
import rpmsack
File "/usr/lib/python2.5/site-packages/yum/rpmsack.py", line 22, in <module>
import misc
File "/usr/lib/python2.5/site-packages/yum/misc.py", line 13, in <module>
import tempfile
File "/usr/lib64/python2.5/tempfile.py", line 33, in <module>
from random import Random as _Random
File "/usr/lib64/python2.5/random.py", line 838, in <module>
_inst = Random()
File "/usr/lib64/python2.5/random.py", line 94, in __init__
self.seed(x)
File "/usr/lib64/python2.5/random.py", line 108, in seed
a = long(_hexlify(_urandom(16)), 16)
File "/usr/lib64/python2.5/os.py", line 736, in urandom
bytes += read(_urandomfd, n - len(bytes))
KeyboardInterrupt
2/ rpm basic commands do not work. For instance rpm -q -a reports NOTHING !!! Trying install a RPM downloaded manually basically does NOTHING.
I am pretty confused.
--
Emmanuel
|
|
|
Re: Compatibility: FC9 - solved [message #32601 is a reply to message #32600] |
Mon, 18 August 2008 20:54 |
neutrino38
Messages: 3 Registered: August 2008 Location: Grenoble, France
|
Junior Member |
|
|
Issue #2 resolved:
/dev/urandom was a regular file. Had to rerecate it:
# rm /dev/urandom
rm: remove regular empty file `/dev/urandom'? o
# mknod -m 0644 /dev/urandom c 1 9
It fixed the rpm issue too !!!!!!
But it it ... its working isn't it?
--
Emmanuel
|
|
|