<?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 Re: Splunk UF after Sleep/Hibernate in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707818#M117005</link>
    <description>So UF recognize the change of time when it writes this message into log, but its scheduler didn’t understand it correctly to run next round at correct time. Definitely time to create splunk support case.</description>
    <pubDate>Tue, 31 Dec 2024 17:01:20 GMT</pubDate>
    <dc:creator>isoutamo</dc:creator>
    <dc:date>2024-12-31T17:01:20Z</dc:date>
    <item>
      <title>Splunk</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707642#M116980</link>
      <description>&lt;P&gt;n/a&lt;/P&gt;</description>
      <pubDate>Wed, 29 Jan 2025 22:50:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707642#M116980</guid>
      <dc:creator>Priya70</dc:creator>
      <dc:date>2025-01-29T22:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707725#M116987</link>
      <description>&lt;P&gt;Can you paste your inputs.conf here between editor's script block &amp;lt;/&amp;gt; ?&lt;/P&gt;&lt;P&gt;When you are saying "&lt;SPAN&gt;cheduled runs are sometimes missed, or scripts execute at unexpected times." is the only fix for this to restart splunkd service on UF?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Are those UFs in domain or just individual nodes which manages time sync with ntpd instead of Windows domain&amp;nbsp;&lt;/SPAN&gt;service?&lt;/P&gt;</description>
      <pubDate>Mon, 30 Dec 2024 14:00:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707725#M116987</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-12-30T14:00:38Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707751#M116989</link>
      <description>&lt;P&gt;N.A&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2025 16:19:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707751#M116989</guid>
      <dc:creator>Priya70</dc:creator>
      <dc:date>2025-01-02T16:19:23Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707769#M116992</link>
      <description>This should works correctly.&lt;BR /&gt;When you are saying “restart UF”, are you meaning splunk UF process or whole windows node?&lt;BR /&gt;Any reason why you are using separate ntpd instead of domain time? Have you checked how big time difference is after hibernation? You are aware that there are limits how big time difference ntpd can manage by itself without additional synchronization?</description>
      <pubDate>Tue, 31 Dec 2024 07:13:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707769#M116992</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-12-31T07:13:54Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707810#M117001</link>
      <description>&lt;P&gt;N.A&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2025 16:20:06 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707810#M117001</guid>
      <dc:creator>Priya70</dc:creator>
      <dc:date>2025-01-02T16:20:06Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707814#M117002</link>
      <description>How quickly that sw update node’s time to correct after hibernation? Basically after that UF’s cron schedule should work as expected. If not then I propose that you should create a support case to Splunk.</description>
      <pubDate>Tue, 31 Dec 2024 15:33:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707814#M117002</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-12-31T15:33:51Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707817#M117004</link>
      <description>&lt;P&gt;N.A&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2025 16:20:42 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707817#M117004</guid>
      <dc:creator>Priya70</dc:creator>
      <dc:date>2025-01-02T16:20:42Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707818#M117005</link>
      <description>So UF recognize the change of time when it writes this message into log, but its scheduler didn’t understand it correctly to run next round at correct time. Definitely time to create splunk support case.</description>
      <pubDate>Tue, 31 Dec 2024 17:01:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707818#M117005</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2024-12-31T17:01:20Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk UF after Sleep/Hibernate</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707820#M117006</link>
      <description>&lt;P&gt;N/A&lt;/P&gt;</description>
      <pubDate>Thu, 02 Jan 2025 16:21:04 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/Splunk/m-p/707820#M117006</guid>
      <dc:creator>Priya70</dc:creator>
      <dc:date>2025-01-02T16:21:04Z</dc:date>
    </item>
  </channel>
</rss>

