Re: Cannot mount via NFS

On Fri, 25 Jun 2004 16:52:22 -0700, Jeff Krimmel wrote:

> On Fri, 25 Jun 2004 23:43:10 +0000, Bill Unruh wrote:
>
>> Jeff Krimmel <madscientist03abc@hotmail.com> writes:
>
> [...]
>
>> ]I have done some more reading, and it looks like my problem might be
>> ]related to the two network interfaces I have set up on the server. The
>> ]server is an NFS server already but only on a second network interface. I
>> ]am trying to mount an NFS partition via the server's first network
>> ]interface. Is it possible for an NFS server to be set up on only one of
>> ]the two interfaces? If so, how can I get the server to act as an NFS
>> ]server on _both_ of its network interfaces?
>>
>> nfs does not care about network interfaces-- it cares about ip addresses.
>> The routing takes care of the interface.
>>
>> Just make sure that you give permission in /etc/exports and that your
>> firewall allows it to happen.
>
> That's good to know, and it's also the frustrating part. Neither machine
> has a firewall up. The export permissions in /etc/exports are set up
> appropriately. The server I am trying to connect to is already an NFS
> server for another set of clients on its other ethernet interface. The
> client I am using is already an NFS client connecting to a different
> server (with a single ethernet interface).
>
> All of the "rpcinfo -p" and "showmount -e" commands I try on the server
> from the client return RPC errors. When I do these commands from the
> server's other clients (that are using the server's other ethernet
> interface), they all work fine. So, RPC is set up and working on both of
> these machines, it's just not working between them. I can ping one from
> the other, I can ssh from one to the other, and I can do just about
> anything else that would imply a solid connection exists between the two.
> The RPC services just aren't jiving between the two for whatever reason.
> I think it has to do with portmapper on the server only paying attention
> to it's private ethernet interface and not looking at the ethernet
> interface I'm trying to connect to. But, absolutely any other ideas would
> be of help; I'm pretty lost.

I guess I should add that the only way I know that a firewall is not
running on either machine is a "/sbin/ipchains -L" on the server (since
it's RedHat 7.3), and a "/sbin/iptables -L" on the client (since it's
RedHat 9.0). All of chains have a default policy of ACCEPT with no rules.
Regardless, as I described above, each machine is successfully operating
in its desired role for _other_ NFS connections, just not the one I want
to establish.

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

In comp.os.linux.networking Jeff Krimmel <madscientist03abc@hotmail.com> wrote:
>>
>> Output of "ifconfig -a" and "netstat -rn" might be helpfull as well.
>
> I don't know what an ACL entry is, but ...

"ACL" stands for "access control list".

> ... I don't see anything using
> "ifconfig -a" or "netstat -rn" that would lead me to believe anything is
> blocking connections between the two.

Would you mind if we'd take a look too?

--
andrei

On Sat, 26 Jun 2004 00:36:11 +0000, Andrei Ivanov wrote:

> In comp.os.linux.networking Jeff Krimmel <madscientist03abc@hotmail.com> wrote:
>>>
>>> Output of "ifconfig -a" and "netstat -rn" might be helpfull as well.
>>
>> I don't know what an ACL entry is, but ...
>
> "ACL" stands for "access control list".
>
>> ... I don't see anything using
>> "ifconfig -a" or "netstat -rn" that would lead me to believe anything is
>> blocking connections between the two.
>
> Would you mind if we'd take a look too?

I'm a bit out of touch here... but I'm wondering if there might not be
some way to simplify the situation and remove some of the unknowns? The OP
talks about two (redundant?) network interfaces. I don't know the topology
and whether they go to/thru the same hubs/routers, but maybe it doesn't
matter. How about removing or disconnecting one of the NICs, say keep the
one that is known to work to/from the other NFS servers/clients. Force all
the traffic to go in/out one network interface. Debug that, and make all
the services work. Then try the redundancy/performance improvement (?) of
adding in the 2nd network interface? or is this server spanning networks?

Divide and conquer?

--
Juhan Leemet
Logicognosis, Inc.

On Sat, 26 Jun 2004 00:36:11 +0000, Andrei Ivanov wrote:

> In comp.os.linux.networking Jeff Krimmel <madscientist03abc@hotmail.com>
> wrote:
>>>
>>> Output of "ifconfig -a" and "netstat -rn" might be helpfull as well.
>>
>> I don't know what an ACL entry is, but ...
>
> "ACL" stands for "access control list".
>
>> ... I don't see anything using
>> "ifconfig -a" or "netstat -rn" that would lead me to believe anything
>> is blocking connections between the two.
>
> Would you mind if we'd take a look too?

For the purposes of reproducing the network output, let's say the server's
IP address is 11.22.67.89, and let's say the client's IP address is
11.22.34.5. (They do, in fact, share the first pair of IP specifiers.)

Here are the results of "ifconfig -a" on the client:

================================================== ========================
eth0 Link encap:Ethernet HWaddr 00:04:75:C4:B6:12
inet addr:11.22.34.5 Bcast:11.22.34.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2690781 errors:0 dropped:0 overruns:207 frame:0
TX packets:1329688 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:843110875 (804.0 Mb) TX bytes:646381397 (616.4 Mb)
Interrupt:12 Base address:0xc000

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:228258 errors:0 dropped:0 overruns:0 frame:0
TX packets:228258 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:523101141 (498.8 Mb) TX bytes:523101141 (498.8 Mb)
================================================== =======================

Here are the result of "netstat -rn" on the client:

================================================== ========================
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
11.22.34.0 11.22.34.5 255.255.255.0 UG 0 0 0 eth0
11.22.34.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 11.22.34.254 0.0.0.0 UG 0 0 0 eth0
================================================== ========================

Here are the results of "ifconfig -a" on the server:

================================================== ========================
eth0 Link encap:Ethernet HWaddr 00:E0:81:23:26:70
inet addr:11.22.67.89 Bcast:11.22.67.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:51913044 errors:0 dropped:0 overruns:1205 frame:0
TX packets:40378426 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:1162649411 (1108.7 Mb) TX bytes:3919979337 (3738.3 Mb)
Interrupt:10 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 00:04:76:F4:FC:56
inet addr:192.168.0.254 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX
packets:859509816 errors:0 dropped:0 overruns:0 frame:0 TX
packets:782850169 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2816956802 (2686.4 Mb) TX bytes:170441727 (162.5 Mb)
Interrupt:5 Memory:e8000000-e8010000

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:49176045 errors:0 dropped:0 overruns:0 frame:0
TX packets:49176045 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4076987982 (3888.1 Mb) TX bytes:4076987982 (3888.1 Mb)
================================================== =======================

Here are the results of "netstat -rn" on the server:

================================================== =======================
Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 40 0 0 eth1
11.22.67.0 0.0.0.0 255.255.255.0 U 40 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 40 0 0 lo
0.0.0.0 11.22.67.254 0.0.0.0 UG 40 0 0 eth0
================================================== =======================

Hope that helps,

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

On Sat, 26 Jun 2004 01:48:51 -0200, Juhan Leemet wrote:

[...]

> I'm a bit out of touch here... but I'm wondering if there might not be
> some way to simplify the situation and remove some of the unknowns? The OP
> talks about two (redundant?) network interfaces.

The server has a total of three network interfaces, two of which are
ethernet interfaces and one of which is the loopback interface. One
ethernet interface is for communications with the outside world; the other
ethernet interface is for a private LAN.

> I don't know the topology
> and whether they go to/thru the same hubs/routers, but maybe it doesn't
> matter.

I'm not exactly sure how the topology is laid out either. They share the first
two groups in the IP address (i.e., they are both 11.22.xx.xx, where the
x's are different for each) if that helps you out. I know quite little
about all of this, really. I'm trying to learn as I go. :)

> How about removing or disconnecting one of the NICs, say keep the
> one that is known to work to/from the other NFS servers/clients. Force all
> the traffic to go in/out one network interface. Debug that, and make all
> the services work. Then try the redundancy/performance improvement (?) of
> adding in the 2nd network interface? or is this server spanning networks?
>
> Divide and conquer?

I have two responses. First, each ethernet interface works just fine,
because I can ping and ssh to and from the server from and to the client.
The client in this case is _not_ part of the server's private LAN, so it
must be using the outside ethernet interface. The server is also an NFS
server for its inside ethernet interface (the one conducting traffic to
and from the private LAN), and that NFS system works beautifully. Second,
I would like to keep the server up and running as much as possible. It's
the master node on a cluster that is currently under heavy load, and I
would like to avoid downtime if at all possible.

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.

Jeff Krimmel <madscientistabc03@hotmail.com> writes:

[...]

>For the purposes of reproducing the network output, let's say the server's
>IP address is 11.22.67.89, and let's say the client's IP address is
>11.22.34.5. (They do, in fact, share the first pair of IP specifiers.)

*sigh*
I'll never understand why people will go into great details trying
to obfuscate the IP addresses involved, while asking for networking
help.

>Here are the results of "ifconfig -a" on the client:

>================================================= =========================
>eth0 Link encap:Ethernet HWaddr 00:04:75:C4:B6:12
> inet addr:11.22.34.5 Bcast:11.22.34.255 Mask:255.255.255.0

[...]

OK.


>Here are the results of "ifconfig -a" on the server:

>================================================= =========================
>eth0 Link encap:Ethernet HWaddr 00:E0:81:23:26:70
> inet addr:11.22.67.89 Bcast:11.22.67.255 Mask:255.255.255.0

[...]

You _do_ realise that these machines are not on the same network?


Michael

On Sun, 27 Jun 2004 09:56:15 +0000, Michael Buchenrieder wrote:

> Jeff Krimmel <madscientistabc03@hotmail.com> writes:
>
> [...]
>
>>For the purposes of reproducing the network output, let's say the server's
>>IP address is 11.22.67.89, and let's say the client's IP address is
>>11.22.34.5. (They do, in fact, share the first pair of IP specifiers.)
>
> *sigh*
> I'll never understand why people will go into great details trying
> to obfuscate the IP addresses involved, while asking for networking
> help.

:) I know so little about this stuff that since I have seen others do it
in the archives, I decided it couldn't hurt.

>>Here are the results of "ifconfig -a" on the client:
>
>>================================================ ==========================
>>eth0 Link encap:Ethernet HWaddr 00:04:75:C4:B6:12
>> inet addr:11.22.34.5 Bcast:11.22.34.255 Mask:255.255.255.0
>
> [...]
>
> OK.
>
>
>>Here are the results of "ifconfig -a" on the server:
>
>>================================================ ==========================
>>eth0 Link encap:Ethernet HWaddr 00:E0:81:23:26:70
>> inet addr:11.22.67.89 Bcast:11.22.67.255 Mask:255.255.255.0
>
> [...]
>
> You _do_ realise that these machines are not on the same network?

They are on the same network but not on the same subnet.

Jeff

--
Add an underscore between 'd' and 's' and remove the first three
letters of the alphabet for email.