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!

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 ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...