Getting Data In

WatchedFile - File too small to check seekcrc, probably truncated. Will re-read entire file - Does this mean it exists?

exocore123
Path Finder

I am writing a splunk forwarder to our own splunk instance. For some reason, my logs are not shipping and its frustrating. The docker instance we have is fargate so I can not ssh into the instance and debug whether the logs exist.

One of my splunkforwarder logs indicated

WatchedFile - File too small to check seekcrc, probably truncated. Will re-read entire file

Does this mean it sees this file/this file existed? I want to make sure that my multicontainer are working as -

A and B - where B is the splunkforwarder

  1. A is wring to the location (/app/logs) - means this file must have been created by A
  2. B using VolumeFrom is about to mount the volume from A
  3. B has access to the logs within /app/logs/
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!

Make Your Machine Data AI-Ready in Splunk

Every team is getting ready for AI agents.   Thursday, November 12, 2026  |  11AM  PST / 2PM EST   ...

Splunk Asynchronous Forwarding Explained

Splunk asynchronous forwarding is often misunderstood as simply setting autoLBVolume. That is not quite right. ...

How to Monitor AI Agents with Splunk Agent Observability

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...