Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights) when replace the IP address to * then service nfs start work, but no one can use the exports. What goes wrong??
Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights) when replace the IP address to * then service nfs start work, but no one can use the exports. What goes wrong??
You might want to make sure that the portmap daemon is running.
/etc/init.d/portmap status
will tell you if it is runnning. If it is not..fire it up.
Mike
mike.redan@bell.ca schrieb:
Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights) when replace the IP address to * then service nfs start work, but no one can use the exports. What goes wrong??
You might want to make sure that the portmap daemon is running.
/etc/init.d/portmap status
will tell you if it is runnning. If it is not..fire it up.
Mike _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes portmap is running and an restart of portmap will not help.:(
Frank Büttner wrote:
mike.redan@bell.ca schrieb:
Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights) when replace the IP address to * then service nfs start work, but no one can use the exports. What goes wrong??
You might want to make sure that the portmap daemon is running.
/etc/init.d/portmap status
will tell you if it is runnning. If it is not..fire it up.
Not sure if it's just a notation issue, it may be that nfs will interpret 3 quads as a class c address. I always use a.b.c.d/n
When you specify an IP/net in exports, what does showmount -e show?
You know that you have to restart nfs when you make changes to exports right?
Milton Calnek schrieb:
Frank Büttner wrote:
mike.redan@bell.ca schrieb:
Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights) when replace the IP address to * then service nfs start work, but no one can use the exports. What goes wrong??
You might want to make sure that the portmap daemon is running.
/etc/init.d/portmap status
will tell you if it is runnning. If it is not..fire it up.
Not sure if it's just a notation issue, it may be that nfs will interpret 3 quads as a class c address. I always use a.b.c.d/n
When you specify an IP/net in exports, what does showmount -e show?
You know that you have to restart nfs when you make changes to exports right?
Yes I know. using a.b.c.d/n will let nfs start, but showmount -e will hang:( And no client can mount the export:(
Frank Büttner schrieb:
Milton Calnek schrieb:
Frank Büttner wrote:
mike.redan@bell.ca schrieb:
Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights) when replace the IP address to * then service nfs start work, but no one can use the exports. What goes wrong??
You might want to make sure that the portmap daemon is running.
/etc/init.d/portmap status
will tell you if it is runnning. If it is not..fire it up.
Not sure if it's just a notation issue, it may be that nfs will interpret 3 quads as a class c address. I always use a.b.c.d/n
When you specify an IP/net in exports, what does showmount -e show?
You know that you have to restart nfs when you make changes to exports right?
Yes I know. using a.b.c.d/n will let nfs start, but showmount -e will hang:( And no client can mount the export:(
After long waiting I get an RPC timeout error
On Fri, 2008-01-11 at 20:12 +0100, Frank Büttner wrote:
Frank Büttner schrieb:
Milton Calnek schrieb:
Frank Büttner wrote:
mike.redan@bell.ca schrieb:
Hello when I try to start nfs the command hangs. I have found out, that the problem is, that I set an IP address at /etc/exports sample: /var/foo XXX.XXX.XXX(some rights)
<snip>
You might want to make sure that the portmap daemon is running.
/etc/init.d/portmap status
will tell you if it is runnning. If it is not..fire it up.
<snip>
After long waiting I get an RPC timeout error
What's in your /etc/hosts.{allow | deny}? Even if portmap is running, these files need to have the correct contents.
E.g. mine have
# hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # ALL: 192.168.2. 127.0.0.
# hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In # particular you should know that NFS uses portmap! ALL: ALL
<snip sig stuff>
HTH
William L. Maltby schrieb: snip
these files need to have the correct contents.
E.g. mine have
# hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # ALL: 192.168.2. 127.0.0. # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In # particular you should know that NFS uses portmap! ALL: ALL<snip sig stuff>
HTH
This both files are empty.
After long try I found the problem.:) I was an dead name server entry at /etc/resolv.conf. After remove it, nfs works how it shut do.
Thanks for all help.
On Sat, 2008-01-12 at 16:07 +0100, Frank Büttner wrote:
William L. Maltby schrieb: snip
these files need to have the correct contents.
E.g. mine have
# hosts.allow This file describes the names of the hosts which are # allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # ALL: 192.168.2. 127.0.0. # hosts.deny This file describes the names of the hosts which are # *not* allowed to use the local INET services, as decided # by the '/usr/sbin/tcpd' server. # # The portmap line is redundant, but it is left to remind you that # the new secure portmap uses hosts.deny and hosts.allow. In # particular you should know that NFS uses portmap! ALL: ALL<snip sig stuff>
HTH
This both files are empty.
After long try I found the problem.:) I was an dead name server entry at /etc/resolv.conf. After remove it, nfs works how it shut do.
That is good to hear. If you have any exposure to the 'Net or some untrusted users on you local net, it would be good to have some rules in the /etc/hosts.{allow | deny}.
<snip sig stuff>
William L. Maltby schrieb:
That is good to hear. If you have any exposure to the 'Net or some untrusted users on you local net, it would be good to have some rules in the /etc/hosts.{allow | deny}.
<snip sig stuff>
This was done by iptables:) Only allowed host can connect to the system, packages form other host are simply dropt.
-
Frank Büttner -
mike.redan＠bell.ca -
Milton Calnek -
William L. Maltby