Getting Data In

Ignored unique path file with crcSalt =

chca
Path Finder

Having trouble with CRC, I set my inputs to use crcSalt = , which I understood would use the full path of the input, and not the first few lines of the file.

However, I still get this error: ignored file (crc conflict, needs crcSalt) for this file:
E:\Log Files\com.chexweb.library_logs_2010\ex100110.log

If the path is unique, why is there a crc conflict? Here's a copy of my inputs.conf:

[monitor://E:\Log Files\com.chexweb.w3_logs_2010]
followTail = 0
crcSalt =
index=iis_com-chexweb-www

[monitor://E:\Log Files\com.chexweb.library_logs_2010]
followTail = 0
crcSalt =
index=iis_com-chexweb-library

[monitor://E:\Log Files\com.chexweb.courses_logs_2010]
followTail = 0
crcSalt =
index=iis_com-chexweb-courses

Tags (2)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

Did you use

crcSalt = <SOURCE>

or

crcSalt = <source>

? The former, with capitals, is required

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

Did you use

crcSalt = <SOURCE>

or

crcSalt = <source>

? The former, with capitals, is required

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!

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...

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

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...