ssh inodes sensor getting inconsistent results or no results

Modified on 2025-06-10 22:00:08 +0200

I had a problem with the SSH inodes sensor coming back with no information after I rebooted 4 servers. The sensor was greyed out most of the time, but would also bounce into an error state some.

I tracked it down to not having one of the NFS shares mounted. It was a little used share which didn't automount on restart. When I mounted it, the sensor immediately recovered. I thought this might be useful information to have. Also, maybe this scenario could show a more meaningful error for debugging in the future.

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Hi Josiah,

Nice find, thanks for sharing! :)

Oct, 2016 - Permalink

Disclaimer:
The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.

ssh inodes sensor getting inconsistent results or no results

Article CommentsAttention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.

Search

Attention

Related Articles

Article Comments

Attention: This article is a record of a conversation with the Paessler support team. The information in this conversation is not updated to preserve the historical record. As a result, some of the information or recommendations in this conversation might be out of date.