Getting Data In

Splunk 4.1.6 - skipped indexing of internal audit event will keep dropping events until indexer congestion is remedied. Check disk space and other issues that may cause indexer to block

inquen
Engager

How would I resolve an issue like this? There appears to be ample disk space on the server hosting the Splunk installation.

1 Solution

jbsplunk
Splunk Employee
Splunk Employee

It probably means something is going on with the queues sending data through Splunk. I would check metrics.log for messages that show 'blocked=true'. Disk space could be part of the reason you'd run into this issue, but its sort of a generic 'things aren't healthy' message.

View solution in original post

k_harini
Communicator

How was this resolved? Please help

0 Karma

rachelneal
Path Finder

I am having the exact same problem and have ample disk space as well. I do find a lot of "blocked=true" in the metrics log but not sure how to remedy. what ended up working?

0 Karma

chicodeme
Communicator

What did it end up being?

0 Karma

jbsplunk
Splunk Employee
Splunk Employee

It probably means something is going on with the queues sending data through Splunk. I would check metrics.log for messages that show 'blocked=true'. Disk space could be part of the reason you'd run into this issue, but its sort of a generic 'things aren't healthy' message.

Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...