<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic WatchedFile - File too small to check seekcrc, probably truncated. Will re-read entire file - Does this mean it exists? in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/WatchedFile-File-too-small-to-check-seekcrc-probably-truncated/m-p/435307#M75953</link>
    <description>&lt;P&gt;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.&lt;/P&gt;

&lt;P&gt;One of my splunkforwarder logs indicated&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;WatchedFile - File too small to check seekcrc, probably truncated. Will re-read entire file
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Does this mean it sees this file/this file existed? I want to make sure that my multicontainer are working as  -&lt;/P&gt;

&lt;P&gt;A and B - where B is the splunkforwarder&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;A is wring to the location (/app/logs) - means this file must have been created by A&lt;/LI&gt;
&lt;LI&gt;B using VolumeFrom is about to mount the volume from A&lt;/LI&gt;
&lt;LI&gt;B has access to the logs within /app/logs/&lt;/LI&gt;
&lt;/OL&gt;</description>
    <pubDate>Wed, 19 Jun 2019 21:51:27 GMT</pubDate>
    <dc:creator>exocore123</dc:creator>
    <dc:date>2019-06-19T21:51:27Z</dc:date>
    <item>
      <title>WatchedFile - File too small to check seekcrc, probably truncated. Will re-read entire file - Does this mean it exists?</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/WatchedFile-File-too-small-to-check-seekcrc-probably-truncated/m-p/435307#M75953</link>
      <description>&lt;P&gt;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.&lt;/P&gt;

&lt;P&gt;One of my splunkforwarder logs indicated&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;WatchedFile - File too small to check seekcrc, probably truncated. Will re-read entire file
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Does this mean it sees this file/this file existed? I want to make sure that my multicontainer are working as  -&lt;/P&gt;

&lt;P&gt;A and B - where B is the splunkforwarder&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;A is wring to the location (/app/logs) - means this file must have been created by A&lt;/LI&gt;
&lt;LI&gt;B using VolumeFrom is about to mount the volume from A&lt;/LI&gt;
&lt;LI&gt;B has access to the logs within /app/logs/&lt;/LI&gt;
&lt;/OL&gt;</description>
      <pubDate>Wed, 19 Jun 2019 21:51:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/WatchedFile-File-too-small-to-check-seekcrc-probably-truncated/m-p/435307#M75953</guid>
      <dc:creator>exocore123</dc:creator>
      <dc:date>2019-06-19T21:51:27Z</dc:date>
    </item>
  </channel>
</rss>

