Splunk Enterprise

Python upgrade

gcusello
SplunkTrust
SplunkTrust

Hi at all,
probably it's an already asked question but I cannot find the correct one:
I upgraded Splunk to 8.0.2 on my test site before to execute in production systems.
I setted (as documented) in $SPLUNK_HOME/etc/system/local/server.conf [general] the python.version = python3 and (after restart) this setting is confirmed by btool.
But checking the Python version (with splunk cmd python -V) I still have Python 2.7.17.

Where could be the error? I missed some step?
in documentation there's only to add the python.version = python3 row in server.conf and restart Splunk but I still have the old.

Now I'm checking on a Windows system but production systems are Red Hat.

Thank you.
Ciao.
Giuseppe

0 Karma
1 Solution

gcusello
SplunkTrust
SplunkTrust
0 Karma

btshivanand
Path Finder

Adding python.version = python3 is not required as i think.Since i see that python 3 is already running. Is it correct?

/splunk cmd python3 --version
Python 3.7.4

 

Regards,Shivanand

 

 

 

 

0 Karma

gcusello
SplunkTrust
SplunkTrust

Ciao,
I found the solution in this answer.
https://answers.splunk.com/answers/795318/switching-to-python3-in-splunk-8.html

Ciao.
Giuseppe

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Fuel Your Journey: What’s Waiting for You at the .conf26 Acceleration Station

Navigating the show floor at .conf26 isn't just about keynotes and technical breakout sessions; it's also ...

Join the Final Session of the Data Management & Federation Bootcamp Series

Over the past three sessions of the Data Management & Federation Bootcamp Series, we've explored how to build ...

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...