<?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: How to Run Universal Forwarder 9.1 as Root? in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616334#M14141</link>
    <description>&lt;P&gt;But have you enabled the boot start with the root user or splunk user or what? Did you use initd or systemd? (the known issue you point to says about initd but is it really so?).&lt;/P&gt;</description>
    <pubDate>Fri, 07 Oct 2022 14:59:36 GMT</pubDate>
    <dc:creator>PickleRick</dc:creator>
    <dc:date>2022-10-07T14:59:36Z</dc:date>
    <item>
      <title>How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616305#M14132</link>
      <description>&lt;P&gt;I have changed the permissions of ownership&lt;/P&gt;
&lt;P&gt;chown -R&amp;nbsp; root:root/opt/splunkforwarder&lt;/P&gt;
&lt;P&gt;After that, I started Splunk as root user, but after that was finished, the owner:group reverted back to splunk:splunk, respectively. The same situation persists even after restarting Splunk and restarting the OS.&lt;/P&gt;
&lt;P&gt;Why its revert back to splunk:splunk&lt;/P&gt;
&lt;P&gt;Wanted to operate with root:root as the owner:group under /opt/splunkforwarder.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://docs.splunk.com/Documentation/Splunk/9.0.1/ReleaseNotes/KnownIssues#Universal_forwarder_issues" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Splunk/9.0.1/ReleaseNotes/KnownIssues#Universal_forwarder_issues&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 14:26:10 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616305#M14132</guid>
      <dc:creator>restinlinux</dc:creator>
      <dc:date>2022-10-07T14:26:10Z</dc:date>
    </item>
    <item>
      <title>Re: Want to Run Universal Forwarder 9.1 as Root</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616320#M14136</link>
      <description>&lt;P&gt;Check the initd or systemctl script to make sure it's not changing the file ownership.&amp;nbsp; If that doesn't help then contact support and ask for assistance with the documented issue.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 14:21:09 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616320#M14136</guid>
      <dc:creator>richgalloway</dc:creator>
      <dc:date>2022-10-07T14:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616330#M14139</link>
      <description>&lt;P&gt;use&amp;nbsp;splunk-launch.conf under $splunkHome/etc/&lt;BR /&gt;use below&lt;/P&gt;&lt;P&gt;SPLUNK_HOME=/opt/splunk&lt;/P&gt;&lt;P&gt;# By default, Splunk stores its indexes under SPLUNK_HOME in the&lt;BR /&gt;# var/lib/splunk subdirectory. This can be overridden&lt;BR /&gt;# here:&lt;BR /&gt;#&lt;BR /&gt;# SPLUNK_DB=/home/build/build-home/ember/var/lib/splunk&lt;/P&gt;&lt;P&gt;# Splunkd daemon name&lt;/P&gt;&lt;P&gt;# Splunkweb daemon name&lt;BR /&gt;SPLUNK_WEB_NAME=splunkweb&lt;/P&gt;&lt;P&gt;# If SPLUNK_OS_USER is set, then Splunk service will only start&lt;BR /&gt;# if the 'splunk [re]start [splunkd]' command is invoked by a user who&lt;BR /&gt;# is, or can effectively become via setuid(2), $SPLUNK_OS_USER.&lt;BR /&gt;# (This setting can be specified as username or as UID.)&lt;BR /&gt;#&lt;BR /&gt;# SPLUNK_OS_USER&lt;BR /&gt;SPLUNK_SERVER_NAME=Splunkd&lt;BR /&gt;&lt;BR /&gt;then you can use sudo systemctl start/stop/status Splunkd&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 14:46:07 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616330#M14139</guid>
      <dc:creator>bapun18</dc:creator>
      <dc:date>2022-10-07T14:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616332#M14140</link>
      <description>&lt;P&gt;post changing this you can also use sudo /splunkhome/bin/splunk start/status/stop etc&lt;BR /&gt;&amp;nbsp;helps, please accept the solution and karma would be appreciated.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 14:48:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616332#M14140</guid>
      <dc:creator>bapun18</dc:creator>
      <dc:date>2022-10-07T14:48:16Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616334#M14141</link>
      <description>&lt;P&gt;But have you enabled the boot start with the root user or splunk user or what? Did you use initd or systemd? (the known issue you point to says about initd but is it really so?).&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 14:59:36 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616334#M14141</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-10-07T14:59:36Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616338#M14143</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/231884"&gt;@PickleRick&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;&lt;P&gt;But have you enabled the boot start with the root user or splunk user or what? Did you use initd or systemd? (the known issue you point to says about initd but is it really so?).&lt;/P&gt;&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;&lt;P&gt;You can use systemd&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 15:26:20 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616338#M14143</guid>
      <dc:creator>bapun18</dc:creator>
      <dc:date>2022-10-07T15:26:20Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616348#M14144</link>
      <description>&lt;P&gt;I know you can. The question is how it was configured in this case.&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 16:40:37 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616348#M14144</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-10-07T16:40:37Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616364#M14145</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;have you try this?&amp;nbsp;&lt;A href="https://docs.splunk.com/Documentation/Forwarder/9.0.1/Forwarder/Installleastprivileged" target="_blank" rel="noopener"&gt;https://docs.splunk.com/Documentation/Forwarder/9.0.1/Forwarder/Installleastprivileged&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Why you want to run it as a root? In security point of view it’s a bad practice and there is no reason for it to get read any files.&lt;/P&gt;&lt;P&gt;r. Ismo&lt;/P&gt;</description>
      <pubDate>Fri, 07 Oct 2022 18:38:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616364#M14145</guid>
      <dc:creator>isoutamo</dc:creator>
      <dc:date>2022-10-07T18:38:28Z</dc:date>
    </item>
    <item>
      <title>Re: How to Run Universal Forwarder 9.1 as Root?</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616421#M14146</link>
      <description>&lt;P&gt;From the POLP point of view, of course the UF should run with user having finely tuned set of permissions allowing it to only access specific files and so on.&lt;/P&gt;&lt;P&gt;But let's be realistic - it's often easier to run it with just root or LOCAL_SYSTEM (that's how it installs in Windows, BTW) so you don't have to pull your hair out trying to get it to read all necessary inputs and not to break your users/groups.&lt;/P&gt;</description>
      <pubDate>Sat, 08 Oct 2022 09:10:40 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/How-to-Run-Universal-Forwarder-9-1-as-Root/m-p/616421#M14146</guid>
      <dc:creator>PickleRick</dc:creator>
      <dc:date>2022-10-08T09:10:40Z</dc:date>
    </item>
  </channel>
</rss>

