Getting Data In

ERROR TailingProcessor - Ignoring path

remy06
Contributor

I have about 8 files of the same kind of event logs which I require Splunk to index. Splunk managed to index 6 of them while the remaining 2 got the following error:

ERROR TailingProcessor - Ignoring path due to: File will not be read, seekptr checksum did not match (file=/myfile/test.out). Last time we saw this initcrc, the filename was different.  You may wish to use a CRC salt on this source.  Consult the documentation or file a support case online at http://www.splunk.com/page/submit_issue">http://www.splunk.com/page/submit_issue for more info.
Tags (2)
1 Solution

ziegfried
Influencer

This is probably because the first 256 byte are the same on some in those files (to prevent Splunk from re-indexing a rotated file, ie same log file but different filename). To work around this, you can instruct Splunk to add the filename as a salt when computing the checksum to determine whether the content of a file has been processed. To do that you'll have to edit the inputs.conf where your file-monitor is configured and add the crcSalt = <SOURCE> option.

Example:

[monitor://some/path]
sourcetype = some_sourcetype
crcSalt = <SOURCE>

The relevant inputs.conf is probably located in $SPLUNK_HOME/etc/system/local or in one of the local folders in your apps $SPLUNK_HOME/etc/apps/someapp/local.

Links:

http://www.splunk.com/base/Documentation/4.1.5/Admin/Monitorfilesanddirectories http://www.splunk.com/base/Documentation/4.1.5/Admin/Inputsconf

View solution in original post

ziegfried
Influencer

This is probably because the first 256 byte are the same on some in those files (to prevent Splunk from re-indexing a rotated file, ie same log file but different filename). To work around this, you can instruct Splunk to add the filename as a salt when computing the checksum to determine whether the content of a file has been processed. To do that you'll have to edit the inputs.conf where your file-monitor is configured and add the crcSalt = <SOURCE> option.

Example:

[monitor://some/path]
sourcetype = some_sourcetype
crcSalt = <SOURCE>

The relevant inputs.conf is probably located in $SPLUNK_HOME/etc/system/local or in one of the local folders in your apps $SPLUNK_HOME/etc/apps/someapp/local.

Links:

http://www.splunk.com/base/Documentation/4.1.5/Admin/Monitorfilesanddirectories http://www.splunk.com/base/Documentation/4.1.5/Admin/Inputsconf

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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...