Hi
Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1
Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server.
When i try and mount the NFS share on the CentOS box i get the following error
# mount /mnt/cvs mount to NFS server 'Server Name' failed: server is down.
Now i know the server is not down as the 7.3 client is connected fine. Anyone seen this before or know a work around? Nothing in any logs from client or server to give me any hints?
thanks
On 28/09/05, Tom Brown tom.brown@goodtechnology.com wrote:
Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1
Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server.
When i try and mount the NFS share on the CentOS box i get the following error
# mount /mnt/cvs mount to NFS server 'Server Name' failed: server is down.
Now i know the server is not down as the 7.3 client is connected fine. Anyone seen this before or know a work around? Nothing in any logs from client or server to give me any hints?
You'll need portmap and nfslock services started on the client at the absolute minimum. To check run:
chkconfig --list | grep -E 'portmap|nfslock'
If you're mounting by name in /etc/fstab then you should probably have an entry for the server in /etc/hosts rather than relying on DNS. Can the client ping the server?
Is the new client machine running iptables or using SELinux? If it's local firewalling and you want to leave it on NFS can be a pain but it's do-able with some changes on the server. See:
https://www.redhat.com/archives/fedora-list/2004-November/msg08461.html
and
http://nfs.sourceforge.net/nfs-howto/security.html#CLIENT.SECURITY
You might want to check the iptables and/or TCP Wrappers setup on the server too. /etc/hosts.allow and /etc/hosts.deny
Will.
On 28/09/05, Will McDonald wmcdonald@gmail.com wrote:
On 28/09/05, Tom Brown tom.brown@goodtechnology.com wrote:
Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1
Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server.
When i try and mount the NFS share on the CentOS box i get the following error
Oh, and don't forget to check /etc/exports on the server. :)
Will.
On 28/09/05, Will McDonald wmcdonald@gmail.com wrote:
On 28/09/05, Tom Brown tom.brown@goodtechnology.com wrote:
Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1
Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server.
When i try and mount the NFS share on the CentOS box i get the following error
Oh, and don't forget to check /etc/exports on the server. :)
Yep thanks for the tips all - It turned out that the mount command was to 'blame' - Using mount from the CentOS 4.1 box gave that error but copying the mount command from the previous 7.3 box and using that to mount the share worked fine.
Odd and a bit hacky but at least it works - Seems mount has changed somewhat and newer versions don't like talking to older server.
On Thu, 29 Sep 2005 at 10:03am, Tom Brown wrote
On 28/09/05, Will McDonald wmcdonald@gmail.com wrote:
On 28/09/05, Tom Brown tom.brown@goodtechnology.com wrote:
Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1
Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server.
When i try and mount the NFS share on the CentOS box i get the following error
Oh, and don't forget to check /etc/exports on the server. :)
Yep thanks for the tips all - It turned out that the mount command was to 'blame' - Using mount from the CentOS 4.1 box gave that error but copying the mount command from the previous 7.3 box and using that to mount the share worked fine.
Odd and a bit hacky but at least it works - Seems mount has changed somewhat and newer versions don't like talking to older server.
What does your fstab entry on the centos box look like? As of centos4, NFS mounts are TCP by default. So, unless you specify UDP, it'll try TCP which, obviously, the 7.3 server isn't doing. I'd bet that's your problem.
Tom Brown wrote:
On 28/09/05, Will McDonald wmcdonald@gmail.com wrote:
On 28/09/05, Tom Brown tom.brown@goodtechnology.com wrote:
Just upgrading one of my dev servers - I'm replacing a current box that runs 7.3 to one that runs CentOS 4.1
Currently the 7.3 dev box talks to a fileserver also running 7.3 over NFS and that works fine. I'm now trying to get the CentOS 4.1 box to talk NFS to the 7.3 server.
When i try and mount the NFS share on the CentOS box i get the following error
Oh, and don't forget to check /etc/exports on the server. :)
Yep thanks for the tips all - It turned out that the mount command was to 'blame' - Using mount from the CentOS 4.1 box gave that error but copying the mount command from the previous 7.3 box and using that to mount the share worked fine.
Odd and a bit hacky but at least it works - Seems mount has changed somewhat and newer versions don't like talking to older server.
Is the server exporting the mount point via NFSv3 or NFSv2?
There is an issue with more recent RedHat based mount versions (since at least FC1) not falling back to trying NFSv2 if the NFSv3 mount fails.
Can you mount using '-o nfsvers=2' (using the CentOS4 mount binary)
James Pearson
On Thu, 29 Sep 2005 at 1:59pm, James Pearson wrote
Tom Brown wrote:
Is the server exporting the mount point via NFSv3 or NFSv2?
There is an issue with more recent RedHat based mount versions (since at least FC1) not falling back to trying NFSv2 if the NFSv3 mount fails.
Can you mount using '-o nfsvers=2' (using the CentOS4 mount binary)
RH7.3 does NFSv3 by default.
Is the server exporting the mount point via NFSv3 or NFSv2?
There is an issue with more recent RedHat based mount versions (since at least FC1) not falling back to trying NFSv2 if the NFSv3 mount fails.
Can you mount using '-o nfsvers=2' (using the CentOS4 mount binary)
interesting...
# mount -o nfsvers=2 /mnt/cvs/
works fine using the mount binary from the CentOS4 box -
thanks for that tip
Tom Brown wrote:
Is the server exporting the mount point via NFSv3 or NFSv2?
There is an issue with more recent RedHat based mount versions (since at least FC1) not falling back to trying NFSv2 if the NFSv3 mount fails.
Can you mount using '-o nfsvers=2' (using the CentOS4 mount binary)
interesting...
# mount -o nfsvers=2 /mnt/cvs/
works fine using the mount binary from the CentOS4 box -
As said earlier in this thread, RH7.3 normally allows NFSv3 mounts - you probably want to check what options are used with rpc.mountd on the server - it may have '--no-nfs-version 3' - which will cause this problem.
I have a hack to mount that works round this problem if you are interested.
James Pearson
-
James Pearson -
Joshua Baker-LePain -
Tom Brown -
Will McDonald