Deployment Architecture

Stale NFS File Handle

sgarvin55
Splunk Employee
Splunk Employee

While starting splunk 4.3 for the first time I received a Stale NFS File handle and Python errors. However, after another restart, the problems went away. Do I need to be concerned?

Tags (2)
1 Solution

sgarvin55
Splunk Employee
Splunk Employee

To fix this problem, the NFS file handles must be renegotiated.

The Python errors (Traceback) is because the NFS location was not available when it was trying to either read/write to that location.

When you restarted and no errors were reported indicates that you are fine. The NFS mnt point was re-established.

You can also try:

Try one of these on the client machine:

a) Unmount and remount the file system, may need to use the -O (overlay option) of mount.

From the man pages:
-O Overlay mount. Allow the file system to be
mounted over an existing mount point, making
the underlying file system inaccessible. If a
mount is attempted on a pre-existing mount point
without setting this flag, the mount will fail,
producing the error "device busy".

b) Kill or restart the process trying to use the nonexistent files.

c) Create another mount point and access the files from the new mount point.

d) Run: /etc/init.d/nfs.client stop; /etc/init.d/nfs.client start

e) Reboot the client having problems.

View solution in original post

sgarvin55
Splunk Employee
Splunk Employee

To fix this problem, the NFS file handles must be renegotiated.

The Python errors (Traceback) is because the NFS location was not available when it was trying to either read/write to that location.

When you restarted and no errors were reported indicates that you are fine. The NFS mnt point was re-established.

You can also try:

Try one of these on the client machine:

a) Unmount and remount the file system, may need to use the -O (overlay option) of mount.

From the man pages:
-O Overlay mount. Allow the file system to be
mounted over an existing mount point, making
the underlying file system inaccessible. If a
mount is attempted on a pre-existing mount point
without setting this flag, the mount will fail,
producing the error "device busy".

b) Kill or restart the process trying to use the nonexistent files.

c) Create another mount point and access the files from the new mount point.

d) Run: /etc/init.d/nfs.client stop; /etc/init.d/nfs.client start

e) Reboot the client having problems.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...