Monitoring Splunk

Does the following notify error cause indexing issues?

cjohnson421
New Member

I have a server running Splunk Enterprise 7.2, and we've been having indexing issues the past week. I found the following error in the splunkd logs for max user watches.

0500 ERROR FilesystemChangeWatcher - Error using inotify to watch filesystem -- /proc/sys/fs/inotify/max_user_watches is probably too low.  Falling back to using timeout-based polling.

Could this error be what is causing the indexing issues?

0 Karma

MoniM
Communicator

Hii @cjohnson421,

You can follow the below answer, it might help you:-
https://answers.splunk.com/answers/147511/filesystemchangewatcher-error-getting-attributes-of-path.h...

0 Karma

vishaltaneja070
Motivator

Not sure about that. but Try to fix the error using the below link:
https://github.com/kubernetes/kubernetes/issues/46230

0 Karma
Get Updates on the Splunk Community!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...