Getting Data In

Splunk monitor mode query

Mansi24
Path Finder

i have indexed data from a directory in monitor mode ,and while checking the status of files being indexed i found an error " ignored file (crc conflict, needs crcSalt)" in the filestatus.
what does this error signifies and how to rectify it?

Tags (2)
0 Karma
1 Solution

somesoni2
Revered Legend

For every file, splunk creates a CRC (cyclic redundancy check) handler, which is based on first few line of the file. This helps prevent re-indexing of same file (even though its renamed, especially in case of files which are getting rolled over). It seems that the files being ignored by Splunk, in your case ,have similar first few lines (characters) causing Splunk to ignore them.

To make Splunk read all the files in a directory regardless of similar files, you need to add "crcSalt = " in your input.conf stanza for the directory being monitored.

[monitor://C:\MyDirectory\*.log]
disabled = false
followTail = 0
sourcetype = myindex
crcSalt = <SOURCE>

Beware that, with this setting Splunk will index all the files, even though they have been renamed, rolled over.

View solution in original post

somesoni2
Revered Legend

For every file, splunk creates a CRC (cyclic redundancy check) handler, which is based on first few line of the file. This helps prevent re-indexing of same file (even though its renamed, especially in case of files which are getting rolled over). It seems that the files being ignored by Splunk, in your case ,have similar first few lines (characters) causing Splunk to ignore them.

To make Splunk read all the files in a directory regardless of similar files, you need to add "crcSalt = " in your input.conf stanza for the directory being monitored.

[monitor://C:\MyDirectory\*.log]
disabled = false
followTail = 0
sourcetype = myindex
crcSalt = <SOURCE>

Beware that, with this setting Splunk will index all the files, even though they have been renamed, rolled over.

somesoni2
Revered Legend

It has to be written as it is (string literal). And don't forget to either restart splunk instance or refresh configuration using "http://splunk-server:port/en-US/debug/refresh"

0 Karma

Mansi24
Path Finder

thanks somesoni2,

just to confirm that the written should be as it is or so we have to give the actual source from where the data is accessed for ex. if data source is my own system than i have to give my as .

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

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...