FC5: Can't copy file /etc/sysconfig/network [message #2267] |
Tue, 28 March 2006 01:42 ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
duswil
Messages: 77 Registered: January 2006
|
Member |
|
|
This is when trying to run Fedora Core 5 when setting a hostname and nameserver. When I didn't have the hostname and nameserver defined, it worked just fine.
vzctl create 1401 --ostemplate fedora-core-5-i386-minimal --ipadd 172.16.4.1
Works just fine:
root@elyssa:~# vzctl start 1401
Starting VPS ...
VPS is mounted
Adding IP address(es): 172.16.4.1
arpsend: 172.16.4.1 is detected on another computer : 00:07:84:46:74:0a
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 172.16.4.1 eth0 FAILED
Setting CPU units: 1000
VPS start in progress...
vzctl set 1401 --save --hostname something.somewhere.com --nameserver 172.16.4.254
This doesn't work:
root@elyssa:~# vzctl start 1401
Starting VPS ...
vzquota : (warning) Quota is running for id 1401 already
VPS is mounted
Adding IP address(es): 172.16.4.1
arpsend: 172.16.4.1 is detected on another computer : 00:07:84:46:74:0a
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 172.16.4.1 eth0 FAILED
ERROR: Can't copy file /etc/sysconfig/network
/bin/cp: preserving times for `/etc/sysconfig/network.29642': Function not implemented
Setting CPU units: 1000
Set hostname: something.somewhere.com
ERROR: Can't copy file /etc/sysconfig/network
/bin/cp: preserving times for `/etc/sysconfig/network.29649': Function not implemented
VPS start in progress...
|
|
|
|
Re: FC5: Can't copy file /etc/sysconfig/network [message #2323 is a reply to message #2281] |
Wed, 29 March 2006 03:08 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) ![Go to next message Go to next message](/theme/ovz3/images/down.png) |
duswil
Messages: 77 Registered: January 2006
|
Member |
|
|
Attached is the out.gz file.
root@elyssa:~# strace -f -o out vzctl start 1401
Starting VPS ...
vzquota : (warning) Quota is running for id 1401 already
VPS is mounted
Adding IP address(es): 172.16.4.1
arpsend: 172.16.4.1 is detected on another computer : 00:07:84:46:74:0a
vps-net_add WARNING: arpsend -c 1 -w 1 -D -e 172.16.4.1 eth0 FAILED
It just stops there. Pressing CTRL-C does nothing. It just sits there like it's doing something, but it's not doing anything.
If I press CTRL-Z, I get the expected [1]+ Stopped strace -f -o out vzctl start 1401
If I , it goes back to its "just sitting there" state.
If I , it just sits there, but in the background instead.
If while it is in the background and I try , I get .
I can't kill the strace process, except for (2140 being the PID, of course)
If after -9'ing the process, I can do this (and get the following response):
root@elyssa:~# vzctl enter 1401
entered into VPS 1401
bash-3.1# exit
logout
exited from VPS 1401
[1]+ Killed strace -f -o out vzctl start 1401
If while entered in the VPS, I get this when I type:
bash-3.1# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:683989 errors:0 dropped:0 overruns:0 frame:0
TX packets:683989 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:772211126 (736.4 MiB) TX bytes:772211126 (736.4 MiB)
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.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 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) . As you can see, there is no venet0 for the 172.16.4.1 IP address like usual. I was expecting to get something more like this (from a VPS running FC4 instead of FC5):
bash-3.00# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:683998 errors:0 dropped:0 overruns:0 frame:0
TX packets:683998 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:772211730 (736.4 MiB) TX bytes:772211730 (736.4 MiB)
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.1 P-t-P:127.0.0.1 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:252 (252.0 b)
venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet addr:192.168.1.1 P-t-P:192.168.1.1 Bcast:192.168.1.1 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
I notice in the FC5 VPS, there is no /etc/resolv.conf file. But in my FC4 VPS, there is.
In the FC5 VPS:
bash-3.1# ll /etc/hosts*
-rw-r--r-- 1 root root 42 Mar 29 06:45 /etc/hosts
-rw-r--r-- 1 root root 42 Mar 29 06:45 /etc/hosts.31561
-rw-r--r-- 1 root root 161 Jan 13 2000 /etc/hosts.allow
-rw-r--r-- 1 root root 347 Jan 13 2000 /etc/hosts.deny
What is this hosts.31561? Is that a temp file from a process that isn't running/working properly, maybe? FC4 doesn't have it.
Diskspace:
bash-3.1# df -h
Filesystem Size Used Avail Use% Mounted on
simfs 1.0G 135M 890M 14% /
-
Attachment: out.gz
(Size: 32.52KB, Downloaded 331 times)
|
|
|
|
Re: FC5: Can't copy file /etc/sysconfig/network [message #2355 is a reply to message #2267] |
Thu, 30 March 2006 11:34 ![Go to previous message Go to previous message](/theme/ovz3/images/up.png) |
Tellerdreher
Messages: 13 Registered: October 2005
|
Junior Member |
|
|
Same for me....
workaround:
replace
/bin/cp -fp ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
with
/bin/cp -f ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
and
/bin/cp -fp ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
with
/bin/cp -f ${file} ${file}.$$ || error "Can't copy file $file" $VZ_FS_NO_DISK_SPACE
in put_param() resp. put_param2() in /etc/sysconfig/vz-scripts/dists/scripts/functions. This will touch /etc/hosts and /etc/sysconfig/network each time you start the VPS and modify the access time (filesystem inside the VPS); I can live with that ![Wink](images/smiley_icons/icon_wink.gif)
Looks like there is something fishy with the cooperation of the /bin/cp from FC5 and OpenVZ framework.
[Updated on: Thu, 30 March 2006 11:35] Report message to a moderator
|
|
|