Installation

Permission Error [Errno 13] after upgrading Splunk

marxsabandana
Path Finder

We encountered an error after we upgraded to a new version of Splunk. This Splunk instance is under a distributed environment and this is one of the indexers within a cluster. Please see the logs below after we run ./splunk status :

 

 

 

Exception: <class 'PermissionError'>, Value: [Errno 13] Permission denied: '/opt/splunk/etc/system/local                                                                                                                             /migration.conf'Traceback (most recent call last):
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/cli.py", line 1359, in <module>
    sys.exit(main(sys.argv))
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/cli.py", line 1212, in main
    parseAndRun(argsList)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/cli.py", line 1067, in parseAndRun
    retVal = cList.getCmd(command, subCmd).call(argList, fromCLI = True)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/cli.py", line 293, in call
    return self.func(args, fromCLI)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/control_api.py", line 35, in wrapperFunc
    return func(dictCopy, fromCLI)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/_internal.py", line 189, in firstTimeRun
    migration.autoMigrate(args[ARG_LOGFILE], isDryRun)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/migration.py", line 3166, in autoMigrate
    checkTimezones(CONF_PROPS, dryRun)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/migration.py", line 411, in checkTimezones
    migSettings = comm.readConfFile(PATH_MIGRATION_CONF)
  File "/opt/splunk/lib/python3.7/site-packages/splunk/clilib/cli_common.py", line 172, in readConfFile
    f = open(path, 'rb')
PermissionError: [Errno 13] Permission denied: '/opt/splunk/etc/system/local/migration.conf'Please file a case online at http://www.splunk.com/page/submit_issue

 

 

 

We also tried the "chown" command but still no luck.

 

 

Labels (2)
0 Karma

pkumar9610
Explorer

try to change ownership to entire Splunk directory, not only to specific folder and then try to restart Splunk and verify. Make sure you change ownership to right user, I just gave <user> as example below 

Eg: If splunk is installed in location - /opt/splunk

- Go to /opt directory

- run command -->  sudo chown -R user:user splunk

- Restart splunk 

 

Hope this helps !!! Good luck 

 

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

What Is Splunk? Here’s What You Can Do with Splunk

Hey Splunk Community, we know you know Splunk. You likely leverage its unparalleled ability to ingest, index, ...

Level Up Your .conf25: Splunk Arcade Comes to Boston

With .conf25 right around the corner in Boston, there’s a lot to look forward to — inspiring keynotes, ...

Manual Instrumentation with Splunk Observability Cloud: How to Instrument Frontend ...

Although it might seem daunting, as we’ve seen in this series, manual instrumentation can be straightforward ...