<?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: savedsearch will not run via cron schedule but can be ran manually in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658322#M227403</link>
    <description>&lt;P&gt;IMO, user Nobody should not be used.&amp;nbsp; All scheduled searches should be owned by a real user, even if it's a service account.&amp;nbsp; That means the user running the search would have a role that specifies what accesses and resources the search has. When a search runs manually, it takes on the role of the person running it (unless set to "run as owner").&lt;/P&gt;&lt;P&gt;Make sure the search in question has read access to all of the knowledge objects it needs.&amp;nbsp; IOW, each KO should be set to "Everyone" in the Read column (if using Nobody, that is; otherwise, set the permissions for the roles that need access).&lt;/P&gt;</description>
    <pubDate>Thu, 21 Sep 2023 18:27:23 GMT</pubDate>
    <dc:creator>richgalloway</dc:creator>
    <dc:date>2023-09-21T18:27:23Z</dc:date>
    <item>
      <title>savedsearch will not run via cron schedule but can be ran manually</title>
      <link>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658301#M227397</link>
      <description>&lt;DIV&gt;I am fighting with what I think is a knowledge object permission at the moment, but not 100% sure of this.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;U&gt;&lt;STRONG&gt;Context&lt;/STRONG&gt;&lt;/U&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV&gt;I have 2 apps&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;1) mainapp with savedsearches, macros, dashboards, etc.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;2) mainapp_TA, containing most of the *.config files (props, transforms, etc.)&lt;BR /&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;Based on the GUI Settings &amp;gt; pages, all ...&lt;BR /&gt;* savedsearches are all set to owner=nobody&lt;/DIV&gt;&lt;DIV&gt;* macros are set to owner= No Owner&lt;/DIV&gt;&lt;DIV&gt;* Sharing is set to App for everything&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;U&gt;&lt;STRONG&gt;Issue&lt;/STRONG&gt;&lt;/U&gt;&lt;/DIV&gt;&lt;UL&gt;&lt;LI&gt;One of my 7 savedsearches will NOT run using a CRON schedule when the owner=nobody. The other savedsearches run just fine.&lt;/LI&gt;&lt;LI&gt;However, once I set owner=greg in /metadata/local.meta, the CRON schedule runs just fine.&lt;UL&gt;&lt;LI&gt;Note: I tried setting owner to another user in our environment, and the the CRON would NOT run. So, somehow this savedsearch is tied to me and I am not sure how to "untie" it.&lt;/LI&gt;&lt;/UL&gt;&lt;/LI&gt;&lt;LI&gt;When the owner=nobody on this savedsearch, I can manually hit "run" from the Settings &amp;gt;&amp;nbsp;Searches, Reports, and Alerts page and it works every time.&lt;/LI&gt;&lt;/UL&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;I cannot figure out WHY this savedsearch is special and requires me to be the owner.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;&lt;DIV class=""&gt;&lt;DIV&gt;&lt;DIV&gt;I have to be missing something but not sure where to look now.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Any help is greatly appreciated.&lt;BR /&gt;&lt;BR /&gt;Regards, Greg&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;&lt;/DIV&gt;</description>
      <pubDate>Thu, 21 Sep 2023 14:20:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658301#M227397</guid>
      <dc:creator>GregSmith</dc:creator>
      <dc:date>2023-09-21T14:20:14Z</dc:date>
    </item>
    <item>
      <title>Re: savedsearch will not run via cron schedule but can be ran manually</title>
      <link>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658322#M227403</link>
      <description>&lt;P&gt;IMO, user Nobody should not be used.&amp;nbsp; All scheduled searches should be owned by a real user, even if it's a service account.&amp;nbsp; That means the user running the search would have a role that specifies what accesses and resources the search has. When a search runs manually, it takes on the role of the person running it (unless set to "run as owner").&lt;/P&gt;&lt;P&gt;Make sure the search in question has read access to all of the knowledge objects it needs.&amp;nbsp; IOW, each KO should be set to "Everyone" in the Read column (if using Nobody, that is; otherwise, set the permissions for the roles that need access).&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 18:27:23 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658322#M227403</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2023-09-21T18:27:23Z</dc:date>
    </item>
    <item>
      <title>Re: savedsearch will not run via cron schedule but can be ran manually</title>
      <link>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658323#M227404</link>
      <description>&lt;P&gt;Thank you. Will give it a try and let the forum know.&lt;BR /&gt;&lt;BR /&gt;Greatly appreciate the response and path forward.&lt;/P&gt;&lt;P&gt;Regards, Greg&lt;/P&gt;</description>
      <pubDate>Thu, 21 Sep 2023 17:27:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/savedsearch-will-not-run-via-cron-schedule-but-can-be-ran/m-p/658323#M227404</guid>
      <dc:creator>GregSmith</dc:creator>
      <dc:date>2023-09-21T17:27:17Z</dc:date>
    </item>
  </channel>
</rss>

