| Activated NFS and now the ve won't bring up network [message #15233] |
Mon, 23 July 2007 15:02  |
 |
JimL
Messages: 116
Registered: February 2007
|
Senior Member |
|
|
I followed the steps in http://wiki.openvz.org/NFS to enable the NFS client. When I rebooted the ve after setting the features, it no longer has a network connection:
[root@50dom0 ~]# vzctl enter 1002
entered into VE 1002
root@walnut:/# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING 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.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:110 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:30826 (30.1 KiB) TX bytes:0 (0.0 b)
dmesg | head
Linux version 2.6.18-ovz028stab035.1-smp (root@centos-32-build) (gcc version 3.4.4 20050721 (Red Hat 3.4.4-2)) #1 SMP Sat Jun 9 12:15:32 MSD 2007
There are no errors reported by /proc/user_beancounters.
There are no error messages in /var/log/vz
2007-07-23T10:53:47-0400 vzctl : VE 1002 : Starting VE ...
2007-07-23T10:53:47-0400 vzctl : VE 1002 : VE is mounted
2007-07-23T10:53:47-0400 vzctl : VE 1002 : Adding IP address(es): 192.168.2.50
2007-07-23T10:53:48-0400 vzctl : VE 1002 : Setting CPU units: 1000
2007-07-23T10:53:48-0400 vzctl : VE 1002 : Set hostname: walnut
2007-07-23T10:53:48-0400 vzctl : VE 1002 : VE start in progress...
I commented out the features line in the /etc/vz/conf/1002.conf file but it still doesn't work.
Any suggestions?
Thanks,
Jim.
I did a little more testing. If I reboot ve0 and leave nsf off in the config file 1002 comes back up almost OK with networking. The only catch is that ssh daemon didn't start. No errors in any log I could find.
I then re enabled the nfs features line and stopped and started the ve 1002. No network. I commented out the features and restarted and no network. So the only way i can get the network back again is to reboot the system.
[Updated on: Mon, 23 July 2007 15:23] Report message to a moderator |
|
|
|
|
|
| Re: Activated NFS and now the ve won't bring up network [message #15347 is a reply to message #15249] |
Fri, 27 July 2007 12:32  |
khorenko
Messages: 533
Registered: January 2006
Location: Moscow, Russia
|
Senior Member |
|
|
Hello Jim,
well, i tried to reproduce your problem but failed.
i paste here the exact log of what i did, could you please check again this commands' sequence and if it again fails for you, paste your log here?
10.0.14.190 - address of the neighbour physical node
10.0.14.189 - address of the eth0 on the Hardware Node
10.0.14.188 - address of the VE on the Hardware Node
[root@dhcp0-12 ~]# uname -a
Linux dhcp0-12.sw.ru 2.6.18-ovz028stab035.1-smp #1 SMP Sat Jun 9 12:15:32 MSD 2007 i686 i686 i386 GNU/Linux
[root@dhcp0-12 ~]# vzctl
vzctl version 3.0.18
...
[root@dhcp0-12 ~]# chkconfig --list |grep nfs
nfs 0:off 1:off 2:off 3:off 4:off 5:off 6:off
nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off
# add to the /etc/sysctl.conf folow line:
kernel.ve_allow_kthreads = 1
[root@dhcp0-12 ~]# modprobe nfs
[root@dhcp0-12 ~]# echo 1 > /proc/sys/kernel/ve_allow_kthreads
[root@dhcp0-12 ~]# ip a l
... eth0: 10.0.14.189/26 ...
[root@dhcp0-12 ~]# vzlist -a 102
VEID NPROC STATUS IP_ADDR HOSTNAME
102 - stopped - -
[root@dhcp0-12 ~]# vzctl set 102 --ipadd 10.0.14.188 --save
Saved parameters for VE 102
[root@dhcp0-12 ~]# vzctl start 102
Starting VE ...
VE is mounted
Adding IP address(es): 10.0.14.188
Setting CPU units: 1000
Configure meminfo: 49152
VE start in progress...
[root@dhcp0-12 ~]# vzctl set 102 --features "nfs:on" --save
Configure meminfo: 49152
Saved parameters for VE 102
[root@dhcp0-12 ~]# vzctl enter 102
entered into VE 102
[root@dhcp0-12 /]# ping 10.0.14.189
PING 10.0.14.189 (10.0.14.189) 56(84) bytes of data.
64 bytes from 10.0.14.189: icmp_seq=1 ttl=64 time=1.21 ms
--- 10.0.14.189 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.211/1.211/1.211/0.000 ms
[root@dhcp0-12 /]# ping 10.0.14.190
PING 10.0.14.190 (10.0.14.190) 56(84) bytes of data.
64 bytes from 10.0.14.190: icmp_seq=1 ttl=63 time=47.2 ms
--- 10.0.14.190 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 47.234/47.234/47.234/0.000 ms
[root@dhcp0-12 /]# logout
exited from VE 102
[root@dhcp0-12 ~]# vzctl restart 102
Restarting VE
Stopping VE ...
VE was stopped
VE is unmounted
Starting VE ...
VE is mounted
Adding IP address(es): 10.0.14.188
Setting CPU units: 1000
Configure meminfo: 49152
VE start in progress...
[root@dhcp0-12 ~]# ip a l
... eth0: 10.0.14.189/26 ...
[root@dhcp0-12 ~]# ip r l
10.0.14.188 dev venet0 scope link
10.0.14.128/26 dev eth0 proto kernel scope link src 10.0.14.189
default dev eth0
[root@dhcp0-12 ~]# ping 10.0.14.190
PING 10.0.14.190 (10.0.14.190) 56(84) bytes of data.
64 bytes from 10.0.14.190: icmp_seq=1 ttl=64 time=3.11 ms
--- 10.0.14.190 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 3.119/3.119/3.119/0.000 ms
Thank you,
Konstantin.
If your problem is solved - please, report it!
It's even more important than reporting the problem itself...
|
|
|
|
|
|
|
|
OpenVZ Forum
Members
Search
Help
Register
Login
Home
