Administrator Guide

NFS Insecure Access to Secure Export
Description A client tries to access a secure export from an insecure port.
Cause The secure NFS export requirement means that the accessing clients must use a well-known port (below
1024), which usually means that they must be root (uid=0) on the client.
Workaround Identify the relevant NFS export and verify that it is set as secure (requires secure client port).
• If the NFS export must remain secure, see the NFS client documentation in order to issue the mount
request from a well-known port (below 1024).
• If a secure NFS export is not required (for example, the network is not public), ensure that the export
is insecure and retry accessing it.
NFS Mount Fails Due to Export Options
Description This event is issued when an NFS mount fails due to export options.
Cause The export list lters client access by IP address, network, or netgroup, and screens the accessing client.
Workaround
1. Verify the relevant NFS export details. Write down all existing options so that you are able to revert
to them.
2. Remove IP address/client restrictions on the NFS export and retry the mount. If the mount
succeeds, verify that the IP address or domain is explicitly specied, or that it is part of the dened
network or netgroups. Once the mount succeeds, adjust the original options accordingly.
Pay attention to pitfall scenarios, where the network netmask is not intuitive, for example,
192.175.255.254 is part of 192.168.0.0/12 but not of 192.168.0.0/16.
NFS Mount Fails Due to Netgroup Failure
Description
This event is issued when a client fails to mount an NFS export because the required netgroup
information cannot be attained.
Cause This error is usually the outcome of a communication error between the FluidFS cluster and the NIS/
LDAP server. It can be a result of a network issue, directory server overload, or a software malfunction.
Workaround Repeat the below process for each congured NIS/LDAP server, each time leaving just a single NIS/
LDAP used, starting with the problematic server.
1. Inspect the NIS/LDAP server logs and see whether the reason for the error is reported in the logs.
2. Network tests: Try pinging the FluidFS cluster from a client located in the same subnet as the NIS/
LDAP server. Try pinging the NIS/LDAP server from a client located in the same subnet as the
FluidFS cluster.
If packet loss is evident on one of the above network tests, resolve the network issues in the
environment.
3. Using a Linux client located in the same subnet as the FluidFS cluster and congured to use the
same directory server, query the netgroup details from the NIS/LDAP server using the relevant
commands. Ensure that the reply is received in a timely manner (up to 3 seconds).
You can temporarily work around the problem by removing the netgroup restriction on the NFS export
and/or by dening an alternative directory server. Identify the relevant NFS export and the options
dened for it, while focusing on the netgroup denition. Document the used netgroup in order to restore
it once the issue is solved and remove the netgroup limitation.
NFS Mount Path Does Not Exist
Description
A client tries to mount a mount path that does not exists on a NAS volume.
Cause This error usually occurs in one of the following scenarios:
• The FluidFS cluster is restored from a backup or remote replication. During restore time, the directory
structure is not complete and a few directories might not exist.
492
FluidFS Troubleshooting