<?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 Splunk stop sending data after log rotation in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687823#M114574</link>
    <description>&lt;P&gt;We have an app input config monitor containing wildcards with whitelist configured to pick up only .log and .out. There are about 120 log files matching the whitelist regex.&amp;nbsp;All the logfiles are ingesting fine except for 1 specific logfile that seems unable to continue the ingestion after log rotation.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;crcSalt and initCrcLength already defined as below -&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;initCrcLength = 1048576&lt;BR /&gt;crcSalt = &amp;lt;SOURCE&amp;gt;&lt;BR /&gt;&lt;BR /&gt;On splunkd.log, the below event can be found&amp;nbsp; -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;05&lt;/SPAN&gt;-15-2024&lt;/SPAN&gt; &lt;SPAN class=""&gt;00:32:57.332&lt;/SPAN&gt; &lt;SPAN class=""&gt;-0400&lt;/SPAN&gt; &lt;SPAN class=""&gt;INFO&lt;/SPAN&gt; &lt;SPAN class=""&gt;WatchedFile&lt;/SPAN&gt;&lt;SPAN&gt; [&lt;/SPAN&gt;&lt;SPAN class=""&gt;16425&lt;/SPAN&gt; &lt;SPAN class=""&gt;tailreader0&lt;/SPAN&gt;&lt;SPAN&gt;] &lt;/SPAN&gt;&lt;SPAN class=""&gt;-&lt;/SPAN&gt; &lt;SPAN class=""&gt;Logfile&lt;/SPAN&gt; &lt;SPAN class=""&gt;truncated&lt;/SPAN&gt; &lt;SPAN class=""&gt;while&lt;/SPAN&gt; &lt;SPAN class=""&gt;open&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN class=""&gt;original&lt;/SPAN&gt; &lt;SPAN class=""&gt;pathname&lt;/SPAN&gt; &lt;SPAN class=""&gt;file=&lt;/SPAN&gt;&lt;SPAN&gt;'/xxx&lt;/SPAN&gt;&lt;SPAN class=""&gt;/catalina-.out&lt;/SPAN&gt;&lt;SPAN&gt;', &lt;/SPAN&gt;&lt;SPAN class=""&gt;will&lt;/SPAN&gt; &lt;SPAN class=""&gt;begin&lt;/SPAN&gt; &lt;SPAN class=""&gt;reading&lt;/SPAN&gt; &lt;SPAN class=""&gt;from&lt;/SPAN&gt; &lt;SPAN class=""&gt;start.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Is 120 logs on 1 input too many for Splunk to handle? How can we resolve this issue?&lt;/P&gt;</description>
    <pubDate>Fri, 17 May 2024 06:04:50 GMT</pubDate>
    <dc:creator>splunkjpm</dc:creator>
    <dc:date>2024-05-17T06:04:50Z</dc:date>
    <item>
      <title>Splunk stop sending data after log rotation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687823#M114574</link>
      <description>&lt;P&gt;We have an app input config monitor containing wildcards with whitelist configured to pick up only .log and .out. There are about 120 log files matching the whitelist regex.&amp;nbsp;All the logfiles are ingesting fine except for 1 specific logfile that seems unable to continue the ingestion after log rotation.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;crcSalt and initCrcLength already defined as below -&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;initCrcLength = 1048576&lt;BR /&gt;crcSalt = &amp;lt;SOURCE&amp;gt;&lt;BR /&gt;&lt;BR /&gt;On splunkd.log, the below event can be found&amp;nbsp; -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN class=""&gt;&lt;SPAN class=""&gt;05&lt;/SPAN&gt;-15-2024&lt;/SPAN&gt; &lt;SPAN class=""&gt;00:32:57.332&lt;/SPAN&gt; &lt;SPAN class=""&gt;-0400&lt;/SPAN&gt; &lt;SPAN class=""&gt;INFO&lt;/SPAN&gt; &lt;SPAN class=""&gt;WatchedFile&lt;/SPAN&gt;&lt;SPAN&gt; [&lt;/SPAN&gt;&lt;SPAN class=""&gt;16425&lt;/SPAN&gt; &lt;SPAN class=""&gt;tailreader0&lt;/SPAN&gt;&lt;SPAN&gt;] &lt;/SPAN&gt;&lt;SPAN class=""&gt;-&lt;/SPAN&gt; &lt;SPAN class=""&gt;Logfile&lt;/SPAN&gt; &lt;SPAN class=""&gt;truncated&lt;/SPAN&gt; &lt;SPAN class=""&gt;while&lt;/SPAN&gt; &lt;SPAN class=""&gt;open&lt;/SPAN&gt;&lt;SPAN&gt;, &lt;/SPAN&gt;&lt;SPAN class=""&gt;original&lt;/SPAN&gt; &lt;SPAN class=""&gt;pathname&lt;/SPAN&gt; &lt;SPAN class=""&gt;file=&lt;/SPAN&gt;&lt;SPAN&gt;'/xxx&lt;/SPAN&gt;&lt;SPAN class=""&gt;/catalina-.out&lt;/SPAN&gt;&lt;SPAN&gt;', &lt;/SPAN&gt;&lt;SPAN class=""&gt;will&lt;/SPAN&gt; &lt;SPAN class=""&gt;begin&lt;/SPAN&gt; &lt;SPAN class=""&gt;reading&lt;/SPAN&gt; &lt;SPAN class=""&gt;from&lt;/SPAN&gt; &lt;SPAN class=""&gt;start.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;Is 120 logs on 1 input too many for Splunk to handle? How can we resolve this issue?&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 06:04:50 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687823#M114574</guid>
      <dc:creator>splunkjpm</dc:creator>
      <dc:date>2024-05-17T06:04:50Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk stop sending data after log rotation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687888#M114581</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;it shouldn't bee to much.&lt;/P&gt;&lt;P&gt;Could you show your inputs.conf inside &amp;lt;/&amp;gt; block?&lt;/P&gt;&lt;P&gt;Also which UF version and OS you have?&lt;/P&gt;&lt;P&gt;Have you also check that your UF user have access to this new (?) or truncated file?&lt;/P&gt;&lt;P&gt;What&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;splunk list inputstatus
splunk list monitor&lt;/LI-CODE&gt;&lt;P&gt;commands outputs are? Can you find this individual file from those and what status it has?&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 14:31:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687888#M114581</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-05-17T14:31:49Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk stop sending data after log rotation</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687931#M114585</link>
      <description>&lt;P&gt;Ugh. As I remember from quite a few years back, tomcat logs are awful to deal with.&lt;/P&gt;&lt;P&gt;How are you rotating them? I suppose you're trying logrotate with copytruncate option (because that was the only way that even remotely resembled a "working" solution for rotating this).&lt;/P&gt;&lt;P&gt;The problem I remember from my previous job was that in this case java wouldn't "rewind" the file position pointer and would continue to append to the old file position even though the file got truncated which would mean that you ended up with a sparse file filled with "virtual zeros" up to the previous logfile's end.&lt;/P&gt;&lt;P&gt;catalina.out is a very ugly thing to deal with. As far as I remember, it didn't rotate on its own and if you wanted to "normally" rotate it you'd have to restart your tomcat completely which is a huge PITA.&lt;/P&gt;</description>
      <pubDate>Fri, 17 May 2024 21:13:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk-stop-sending-data-after-log-rotation/m-p/687931#M114585</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2024-05-17T21:13:37Z</dc:date>
    </item>
  </channel>
</rss>

