<?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: [Errno 13] Permission denied in Security</title>
    <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394181#M9624</link>
    <description>&lt;P&gt;Try using this command instead&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sudo service splunk restart
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It seems the splunk is running with different user and you're trying to restart it with user root. The above service command will ensure Splunk service will restart with the account it's setup to run with.&lt;/P&gt;</description>
    <pubDate>Thu, 21 Feb 2019 19:49:08 GMT</pubDate>
    <dc:creator>somesoni2</dc:creator>
    <dc:date>2019-02-21T19:49:08Z</dc:date>
    <item>
      <title>How to resolve [Errno 13] Permission denied?</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394180#M9623</link>
      <description>&lt;P&gt;Hello friend,&lt;/P&gt;
&lt;P&gt;I've got the next issue trying to run ./splunk start or status. How can i fix it? i think it is a user permission issue.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE&gt;[root@cerr500810 bin]# ./splunk start

Warning: cannot create "/monitoreo/splunk/var/log/splunk"

Warning: cannot create "/monitoreo/splunk/var/log/introspection"
Pid file "/monitoreo/splunk/var/run/splunk/splunkd.pid" unreadable.: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/Splunk_TA_nix/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/TA-tripwire_enterprise/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/launcher/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/lookup_editor/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/search/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/splunk_instrumentation/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/system/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/learned/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/Splunk_TA_nix/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/TA-tripwire_enterprise/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/launcher/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/lookup_editor/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/search/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/splunk_instrumentation/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/system/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/learned/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/Splunk_TA_nix/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/TA-tripwire_enterprise/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/launcher/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/lookup_editor/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/search/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/splunk_instrumentation/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/system/metadata/local.meta: Permission denied
Cannot initialize: /monitoreo/splunk/etc/apps/learned/metadata/local.meta: Permission denied
Pid file "/monitoreo/splunk/var/run/splunk/splunkd.pid" unreadable.: Permission denied
Pid file "/monitoreo/splunk/var/run/splunk/splunkd.pid" unreadable.: Permission denied
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 08 Jul 2022 14:21:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394180#M9623</guid>
      <dc:creator>julian0125</dc:creator>
      <dc:date>2022-07-08T14:21:11Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394181#M9624</link>
      <description>&lt;P&gt;Try using this command instead&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;sudo service splunk restart
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;It seems the splunk is running with different user and you're trying to restart it with user root. The above service command will ensure Splunk service will restart with the account it's setup to run with.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 19:49:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394181#M9624</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-21T19:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394182#M9625</link>
      <description>&lt;P&gt;hello @somesoni2&lt;/P&gt;

&lt;P&gt;i tried with the command "sudo service splunk restart" but it shows the next:&lt;/P&gt;

&lt;P&gt;[root@cerr500810 bin]# sudo service splunk restart&lt;BR /&gt;
Redirecting to /bin/systemctl restart splunk.service&lt;BR /&gt;
Job for splunk.service failed because the control process exited with error code. See "systemctl status splunk.service" and "journalctl -xe" for details.&lt;BR /&gt;
[root@cerr500810 bin]# sudo service splunk restart&lt;BR /&gt;
Redirecting to /bin/systemctl restart splunk.service&lt;BR /&gt;
Job for splunk.service failed because the control process exited with error code. See "systemctl status splunk.service" and "journalctl -xe" for details.&lt;BR /&gt;
[root@cerr500810 bin]# sudo service splunk start&lt;BR /&gt;
Redirecting to /bin/systemctl start splunk.service&lt;BR /&gt;
Job for splunk.service failed because the control process exited with error code. See "systemctl status splunk.service" and "journalctl -xe" for details.&lt;BR /&gt;
[root@cerr500810 bin]# sudo service splunk status&lt;BR /&gt;
Redirecting to /bin/systemctl status splunk.service&lt;BR /&gt;
● splunk.service - splunk Service , para monitoreo de Seguridad&lt;BR /&gt;
   Loaded: loaded (/etc/systemd/system/splunk.service; disabled; vendor preset: disabled)&lt;BR /&gt;
   Active: failed (Result: exit-code) since Thu 2019-02-21 20:28:16 UTC; 4s ago&lt;BR /&gt;
  Process: 24782 ExecStart=/usr/local/sbin/splunk.sh (code=exited, status=2)&lt;BR /&gt;
 Main PID: 24782 (code=exited, status=2)&lt;/P&gt;

&lt;P&gt;Feb 21 20:28:15 cerr500810 systemd[1]: Starting splunk Service , para monitoreo de Seguridad...&lt;BR /&gt;
Feb 21 20:28:16 cerr500810 systemd[1]: splunk.service: main process exited, code=exited, status=2/INVALIDARGUMENT&lt;BR /&gt;
Feb 21 20:28:16 cerr500810 systemd[1]: Failed to start splunk Service , para monitoreo de Seguridad.&lt;BR /&gt;
Feb 21 20:28:16 cerr500810 systemd[1]: Unit splunk.service entered failed state.&lt;BR /&gt;
Feb 21 20:28:16 cerr500810 systemd[1]: splunk.service failed.&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:30:08 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394182#M9625</guid>
      <dc:creator>julian0125</dc:creator>
      <dc:date>2019-02-21T20:30:08Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394183#M9626</link>
      <description>&lt;P&gt;Can you run this and see under what user Splunkd service is running?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;ps -ef  | grep splunkd | grep start | grep -v grep
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Thu, 21 Feb 2019 20:56:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394183#M9626</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2019-02-21T20:56:35Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394184#M9627</link>
      <description>&lt;P&gt;Sure! i've got this&lt;/P&gt;

&lt;P&gt;[segemer@cerr500810 system]$  ps -ef  | grep splunkd | grep start | grep -v grep&lt;BR /&gt;
root      7805     1  0 Feb13 ?        00:29:16 splunkd -p 8089 start&lt;BR /&gt;
root      7824  7805  0 Feb13 ?        00:00:00 [splunkd pid=7805] splunkd -p 8089 start [process-runner]&lt;BR /&gt;
[segemer@cerr500810 system]$&lt;/P&gt;</description>
      <pubDate>Thu, 21 Feb 2019 21:00:11 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394184#M9627</guid>
      <dc:creator>julian0125</dc:creator>
      <dc:date>2019-02-21T21:00:11Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394185#M9628</link>
      <description>&lt;P&gt;Looks like at some point of time, Splunk started with wrong user. It's currently running as root. Do you always run Splunk as root OR use a non-root splunk user account?&lt;/P&gt;

&lt;P&gt;Also, who owns Splunk file system (run ls -ltr /monitoreo/splunk)?&lt;BR /&gt;
What's content of attribute SPLUNK_OS_USER in file /monitoreo/splunk/etc/splunk-launch.conf ?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 23:19:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394185#M9628</guid>
      <dc:creator>somesoni2</dc:creator>
      <dc:date>2020-09-29T23:19:53Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394186#M9629</link>
      <description>&lt;P&gt;you might be root, but the Splunk owner is another user.&lt;BR /&gt;
1. command &lt;CODE&gt;ls -l&lt;/CODE&gt; or &lt;CODE&gt;ll&lt;/CODE&gt; to know who the owner is&lt;BR /&gt;
2. switch to Splunk user&lt;/P&gt;</description>
      <pubDate>Fri, 22 Feb 2019 10:21:12 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394186#M9629</guid>
      <dc:creator>andhika_pratama</dc:creator>
      <dc:date>2019-02-22T10:21:12Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394187#M9630</link>
      <description>&lt;P&gt;This happens when you have started splunk as user &lt;CODE&gt;root&lt;/CODE&gt; and then later try to start it as the correct non- &lt;CODE&gt;root&lt;/CODE&gt; user (usually &lt;CODE&gt;splunk&lt;/CODE&gt;).  To fix, do this:&lt;/P&gt;

&lt;P&gt;AS USER &lt;CODE&gt;root&lt;/CODE&gt;:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;/opt/splunk/bin/splunk start
chown -R splunk: $SPLUNK_HOME
service splunk start
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 04 Mar 2019 10:37:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394187#M9630</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2019-03-04T10:37:35Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394188#M9631</link>
      <description>&lt;P&gt;I see Splunk is not installed under the default directory &lt;BR /&gt;
try running this &lt;/P&gt;

&lt;P&gt;you have to make sure Splunk is running from &lt;BR /&gt;
/opt/splunk/bin/splunk start  &lt;/P&gt;

&lt;P&gt;1- change the splunk home directory to /opt/splunk&lt;BR /&gt;
2- Run (using the root user) /opt/splunk/bin/splunk stop &lt;BR /&gt;
3- chown -R splunk /opt/&lt;BR /&gt;
4- sudo su splunk &lt;BR /&gt;
5- /opt/splunk/bin/splunk start&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 11:38:55 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394188#M9631</guid>
      <dc:creator>aamer86</dc:creator>
      <dc:date>2019-12-09T11:38:55Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394189#M9632</link>
      <description>&lt;P&gt;I see that you already are root. This is bad practice. Never use root to start the service.&lt;/P&gt;

&lt;P&gt;Next, check the permissions on the file system as suggested by @woodcock &lt;/P&gt;

&lt;P&gt;If the permissions are set up correctly, check if the disk is mounted properly. I have seen instances where the disk is set to read-only mode accidentally by the linux admin. This makes startup or usage impossible since splunk will be unable to create files.&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 11:45:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394189#M9632</guid>
      <dc:creator>arjunpkishore5</dc:creator>
      <dc:date>2019-12-09T11:45:16Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394190#M9633</link>
      <description>&lt;P&gt;Hi @aamer86 &lt;/P&gt;

&lt;P&gt;This is incorrect. Default directory is just that - a default directory and not a mandatory directory. It's possible to change the base directory and have splunk running by updating the value of $SPLUNK_HOME&lt;/P&gt;</description>
      <pubDate>Mon, 09 Dec 2019 11:46:56 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/394190#M9633</guid>
      <dc:creator>arjunpkishore5</dc:creator>
      <dc:date>2019-12-09T11:46:56Z</dc:date>
    </item>
    <item>
      <title>Re: [Errno 13] Permission denied</title>
      <link>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/604936#M16215</link>
      <description>&lt;P&gt;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/1406"&gt;@woodcock&lt;/a&gt;&amp;nbsp;this was the same issue which i was facing...and now using your steps it resolved thanks a lot&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jul 2022 13:00:17 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/How-to-resolve-Errno-13-Permission-denied/m-p/604936#M16215</guid>
      <dc:creator>nnimbe1</dc:creator>
      <dc:date>2022-07-08T13:00:17Z</dc:date>
    </item>
  </channel>
</rss>

