<?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: forwarder fails to start with permission errors in Getting Data In</title>
    <link>https://community.splunk.com/t5/Getting-Data-In/forwarder-fails-to-start-with-permission-errors/m-p/196841#M39134</link>
    <description>&lt;P&gt;For starters, being on CentOS why you chose not to install the x86_64 RPM version.  The install script will create the right user/and group for you.  Installing with the tarball needs manual intervention to get things right, I fail to see any benefit from side-stepping, and you may your problem rooted in this very fact.  As a permissions issue this looks more like an underlying system/file-system-level problem.&lt;/P&gt;

&lt;P&gt;First of all, your one example prompt says "root&amp;gt;", but does than mean you genuinely are running su?  Or is it just a static prompt?  Second, what is the state of the files?  You say you changed permissions to 777, but that's a really awful thing to do.  Show us the result of&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;id
ls -ld /opt/splunkforwarder/etc/users/users.ini
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Can you&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;cat /opt/splunkforwarder/etc/users/users.ini
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Are you running SELinux enabled?  Is it enforcing?  If so (and I suspect this is probably your problem) your security context is going to be out of whack.  It may be that that is disallowing the file open.&lt;/P&gt;</description>
    <pubDate>Thu, 12 Jun 2014 19:42:52 GMT</pubDate>
    <dc:creator>grijhwani</dc:creator>
    <dc:date>2014-06-12T19:42:52Z</dc:date>
    <item>
      <title>forwarder fails to start with permission errors</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/forwarder-fails-to-start-with-permission-errors/m-p/196840#M39133</link>
      <description>&lt;P&gt;Brand new system, new colo. &lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
cat /etc/redhat-release &lt;BR /&gt;
CentOS release 6.5 (Final)&lt;BR /&gt;
arch&lt;BR /&gt;
x86_64&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;Installing this:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
splunkforwarder-6.1.1-207789-Linux-x86_64.tgz&lt;/PRE&gt;&lt;/P&gt;

&lt;P&gt;After the unzip, attempting to start the forwarder:&lt;BR /&gt;
&lt;PRE&gt;&lt;BR /&gt;
root&amp;gt; /opt/splunkforwarder/bin/splunk start --accept-license --answer-yes --auto-ports --no-prompt&lt;BR /&gt;
&lt;/PRE&gt;&lt;BR /&gt;
Gives all these "Permission Denied" errors.&lt;BR /&gt;
Even when changing the file:&lt;BR /&gt;
/opt/splunkforwarder/etc/users/users.ini&lt;BR /&gt;
to 777 it still gives this error.&lt;/P&gt;

&lt;P&gt;Help!&lt;/P&gt;

&lt;PRE&gt;
./splunk start

Splunk&amp;gt; Winning the War on Error

Checking prerequisites...
    Checking mgmt port [8089]: open
Cannot create username mapping file: /opt/splunkforwarder/etc/users/users.ini: Permission denied
Cannot open file=/opt/splunkforwarder/etc/users/users.ini for parsing: Permission denied
Error opening username mapping file: /opt/splunkforwarder/etc/users/users.ini
New certs have been generated in '/opt/splunkforwarder/etc/auth'.
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
ERROR - Error opening "/opt/splunkforwarder/var/log/splunk/splunkd-utility.log": Permission denied
    Checking conf files for problems...
ERROR UsernameMapper - Cannot create username mapping file: /opt/splunkforwarder/etc/users/users.ini: Permission denied
ERROR IniFile - Cannot open file=/opt/splunkforwarder/etc/users/users.ini for parsing: Permission denied
ERROR UsernameMapper - Error opening username mapping file: /opt/splunkforwarder/etc/users/users.ini
ERROR UsernameMapper - Cannot create username mapping file: /opt/splunkforwarder/etc/users/users.ini: Permission denied
ERROR IniFile - Cannot open file=/opt/splunkforwarder/etc/users/users.ini for parsing: Permission denied
ERROR UsernameMapper - Error opening username mapping file: /opt/splunkforwarder/etc/users/users.ini
Cannot open file to check: /opt/splunkforwarder/etc/system/local/inputs.conf
        Your indexes and inputs configurations are not internally consistent. For more information, run 'splunk btool check --debug'
ERROR UsernameMapper - Cannot create username mapping file: /opt/splunkforwarder/etc/users/users.ini: Permission denied
ERROR IniFile - Cannot open file=/opt/splunkforwarder/etc/users/users.ini for parsing: Permission denied
ERROR UsernameMapper - Error opening username mapping file: /opt/splunkforwarder/etc/users/users.ini
ERROR UsernameMapper - Cannot create username mapping file: /opt/splunkforwarder/etc/users/users.ini: Permission denied
ERROR IniFile - Cannot open file=/opt/splunkforwarder/etc/users/users.ini for parsing: Permission denied
ERROR UsernameMapper - Error opening username mapping file: /opt/splunkforwarder/etc/users/users.ini
&lt;/PRE&gt;

&lt;P&gt;FYI: &lt;/P&gt;

&lt;PRE&gt;
./bin/splunk btool check --debug
Checking: /opt/splunkforwarder/etc/apps/search/local/inputs.conf
No spec file for: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/app.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/default-mode.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/inputs.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/limits.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/outputs.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/props.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/server.conf
Checking: /opt/splunkforwarder/etc/apps/SplunkUniversalForwarder/default/web.conf
No spec file for: /opt/splunkforwarder/etc/apps/introspection_generator_addon/default/app.conf
Checking: /opt/splunkforwarder/etc/apps/introspection_generator_addon/default/inputs.conf
Checking: /opt/splunkforwarder/etc/apps/introspection_generator_addon/default/server.conf
No spec file for: /opt/splunkforwarder/etc/apps/search/default/app.conf
Checking: /opt/splunkforwarder/etc/apps/search/default/props.conf
Checking: /opt/splunkforwarder/etc/apps/search/default/restmap.conf
Checking: /opt/splunkforwarder/etc/system/default/alert_actions.conf
No spec file for: /opt/splunkforwarder/etc/system/default/app.conf
Checking: /opt/splunkforwarder/etc/system/default/audit.conf
Checking: /opt/splunkforwarder/etc/system/default/authentication.conf
Checking: /opt/splunkforwarder/etc/system/default/authorize.conf
No spec file for: /opt/splunkforwarder/etc/system/default/conf.conf
Checking: /opt/splunkforwarder/etc/system/default/default-mode.conf
Checking: /opt/splunkforwarder/etc/system/default/inputs.conf
Checking: /opt/splunkforwarder/etc/system/default/limits.conf
Checking: /opt/splunkforwarder/etc/system/default/outputs.conf
Checking: /opt/splunkforwarder/etc/system/default/procmon-filters.conf
Checking: /opt/splunkforwarder/etc/system/default/props.conf
Checking: /opt/splunkforwarder/etc/system/default/restmap.conf
Checking: /opt/splunkforwarder/etc/system/default/server.conf
Checking: /opt/splunkforwarder/etc/system/default/source-classifier.conf
Checking: /opt/splunkforwarder/etc/system/default/web.conf
Checking: /opt/splunkforwarder/etc/system/local/inputs.conf
Checking: /opt/splunkforwarder/etc/system/local/server.conf
&lt;/PRE&gt;</description>
      <pubDate>Thu, 12 Jun 2014 03:34:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/forwarder-fails-to-start-with-permission-errors/m-p/196840#M39133</guid>
      <dc:creator>swissarmychains</dc:creator>
      <dc:date>2014-06-12T03:34:08Z</dc:date>
    </item>
    <item>
      <title>Re: forwarder fails to start with permission errors</title>
      <link>https://community.splunk.com/t5/Getting-Data-In/forwarder-fails-to-start-with-permission-errors/m-p/196841#M39134</link>
      <description>&lt;P&gt;For starters, being on CentOS why you chose not to install the x86_64 RPM version.  The install script will create the right user/and group for you.  Installing with the tarball needs manual intervention to get things right, I fail to see any benefit from side-stepping, and you may your problem rooted in this very fact.  As a permissions issue this looks more like an underlying system/file-system-level problem.&lt;/P&gt;

&lt;P&gt;First of all, your one example prompt says "root&amp;gt;", but does than mean you genuinely are running su?  Or is it just a static prompt?  Second, what is the state of the files?  You say you changed permissions to 777, but that's a really awful thing to do.  Show us the result of&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;id
ls -ld /opt/splunkforwarder/etc/users/users.ini
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Can you&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;cat /opt/splunkforwarder/etc/users/users.ini
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Are you running SELinux enabled?  Is it enforcing?  If so (and I suspect this is probably your problem) your security context is going to be out of whack.  It may be that that is disallowing the file open.&lt;/P&gt;</description>
      <pubDate>Thu, 12 Jun 2014 19:42:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Getting-Data-In/forwarder-fails-to-start-with-permission-errors/m-p/196841#M39134</guid>
      <dc:creator>grijhwani</dc:creator>
      <dc:date>2014-06-12T19:42:52Z</dc:date>
    </item>
  </channel>
</rss>

