OpenVZ Forum


Home » General » Support » Centos 5.0 problem with new kernel, nfs in VE not working.
Centos 5.0 problem with new kernel, nfs in VE not working. [message #26277] Sat, 19 January 2008 17:12 Go to next message
JimL is currently offline  JimL
Messages: 116
Registered: February 2007
Senior Member
NFS has stopped working in a VE running under Centos 5.0.

See the following:

### HN VE0 Centos.
[root@server1 ~]# uname -r
2.6.18-53.1.4.el5.028stab053.4

### be sure the file systems are exported

root@walnut:~# ssh 192.168.2.90
root@192.168.2.90's password:

root@blackie:~# exportfs
/data1/mail/www
192.168.2.50
/data1/mail/www
192.168.2.44
/data1/mail/db 192.168.2.50
/data1/mail/db 192.168.2.44
root@blackie:~# exit

### try to mount one from a VE
root@walnut:~# mount /var/lib/omega/data/
mount to NFS server '192.168.2.90' failed: server is down.
### no it isn't
root@walnut:~# ping 192.168.2.90
PING 192.168.2.90 (192.168.2.90) 56(84) bytes of data.
64 bytes from 192.168.2.90: icmp_seq=1 ttl=63 time=313 ms
64 bytes from 192.168.2.90: icmp_seq=2 ttl=63 time=0.183 ms

--- 192.168.2.90 ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 1000ms
rtt min/avg/max/mdev = 0.183/156.837/313.491/156.654 ms

### prove we are .50
root@walnut:~# ifconfig
...
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.2.50 P-t-P:192.168.2.50 Bcast:0.0.0.0 Mask:255.255.255.255
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1


### Try from another system, not a VE
root@chinaberry:~# mount /var/lib/omega/data/
root@chinaberry:~# ifconfig
eth2 Link encap:Ethernet HWaddr 00:16:E6:36:35:0A
inet addr:192.168.2.44 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::216:e6ff:fe36:350a/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10267 errors:0 dropped:0 overruns:0 frame:0
TX packets:10315 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4847869 (4.6 MiB) TX bytes:1017159 (993.3 KiB)
Interrupt:17 Base address:0xc000
root@chinaberry:~# mount| grep nfs
192.168.2.90:/data1/mail/db on /var/lib/omega/data type nfs (rw,rsize=8192,wsize=8192,timeo=14,intr,addr=192.168.2.90)

### It worked on that system, now look to see if nfs is on
[root@server1 conf]# grep -i nfs 1002.conf
FEATURES="nfs:on "
[root@server1 conf]# grep IP 1002.conf
NUMIPTENT="128:128"
IP_ADDRESS="192.168.2.50"
[root@server1 conf]#
### so nfs is on and the ip is right.

I did notice this in the /proc/userbeancounters which bothers me a bit.

numothersock 17 20 80 80 29



How can I have exceeded 80 sockets when the max is 20?

Thanks,
Jim.

Report message to a moderator

Re: Centos 5.0 problem with new kernel, nfs in VE not working. [message #26316 is a reply to message #26277] Mon, 21 January 2008 14:13 Go to previous messageGo to next message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

1. Can you provide us with strace output of mount command?
strace -f -o <OUTFILE> <MOUNT_COMMAND>
2. Please attach also dmesg output.
3. Have you any other failcnt in /proc/user_beancouters? Can you show /proc/user_beancounters? Are failcnts clear after VPS was stopped and started again? If it is possible please show /proc/user_beancouters after VPS was stopped and after VPS was started.

Thank You!

Report message to a moderator

Re: Centos 5.0 problem with new kernel, nfs in VE not working. [message #26335 is a reply to message #26316] Mon, 21 January 2008 21:18 Go to previous messageGo to next message
JimL is currently offline  JimL
Messages: 116
Registered: February 2007
Senior Member
maratrus wrote on Mon, 21 January 2008 09:13

Hi,

1. Can you provide us with strace output of mount command?
strace -f -o <OUTFILE> <MOUNT_COMMAND>
2. Please attach also dmesg output.
3. Have you any other failcnt in /proc/user_beancouters? Can you show /proc/user_beancounters? Are failcnts clear after VPS was stopped and started again? If it is possible please show /proc/user_beancouters after VPS was stopped and after VPS was started.

Thank You!

OK I've pushed back to the earlier kernel now, but I'll try again a little later. This may be related to the fact that somehow the firewall was activated during the last upgrade to the new kernel. I've since shut it off.

I'm a little confused, how do you access the beancounters of a stopped VPS? The only way I know how to do it is log into a running VPS and cat /proc/beancounters.

Thanks,
Jim.

Report message to a moderator

Re: Centos 5.0 problem with new kernel, nfs in VE not working. [message #26414 is a reply to message #26335] Wed, 23 January 2008 08:47 Go to previous message
maratrus is currently offline  maratrus
Messages: 1495
Registered: August 2007
Location: Moscow
Senior Member
Hi,

I suppose that you have an access to HN and can do "cat /proc/user_beancounters" there. I think if some "usage counters" > 0 failcnt may not be reset immediately.

Report message to a moderator

Previous Topic: Notice: Undefined variable: cat_id in /var/www/html/theme/ovz/tree.php on line 245
Next Topic: Is sharing same files between VEs possible with simfs?
Goto Forum:
  

[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Tue Sep 10 19:10:14 GMT 2024

Total time taken to generate the page: 0.04951 seconds
Powered by FUDforum Powered by Virtuozzo Containers