topic Re: Filter out the Phython version check in integrity check in Splunk Enterprise

Filter out the Phython version check in integrity check

sramamurthy2 — Fri, 24 Jan 2025 13:54:28 GMT

Hi,

We recently upgraded the Splunk environment to 9.2.4, and we have some of the apps that are using the Python 2.7 version we are in the process of upgrading those apps in the next 3 months. I noticed that there are errors related to " splunk/bin/jp.py present_but_shouldnt_be, /splunk/bin/python2.7 present_but_shouldnt_be"

Since we also use python 2.7, we do not want to delete these files in the bin. I want to understand there is any way that we can suppress these messages during the integrity check.

Re: Filter out the Phython version check in integrity check

sramamurthy2 — Fri, 24 Jan 2025 13:56:52 GMT

@dural_yyz, @amahoski , @gcusello

Re: Filter out the Phython version check in integrity check

sramamurthy2 — Fri, 24 Jan 2025 14:39:17 GMT

@kiran_panchavat , @PickleRick , @ITWhisperer , @isoutamo , @bowesmana

Re: Filter out the Phython version check in integrity check

richgalloway — Fri, 24 Jan 2025 14:41:34 GMT

Please don't tag uninvolved users. If someone has an answer, they'll respond.

Re: Filter out the Phython version check in integrity check

dural_yyz — Tue, 28 Jan 2025 15:36:28 GMT

Well I suppose you could add these to the manifest file but I can't stress how much I wouldn't do that.

That said I was under the impression that at some point in Splunk 8.x and forward they stopped allowing Splunk processes to reference or pull any Python 2.x capabilities and libraries. Now I'm not strictly very experienced in that area so I could easily be wrong.

Morrel of the story:

Get off python 2.x reliance ASAP.

Re: Filter out the Phython version check in integrity check

sramamurthy2 — Mon, 17 Feb 2025 15:20:57 GMT

Thanks @dural_yyz, you were right. I tried to copy the files from the Splunk manifest under the $plunk_Home and use the same in the latest version manifest file in the Splunk 9.x and after that I restarted the services and I dont see the error again. Looks like When the splunk starts it reads the manifest file and triggers the error that are not in the manifiest file.

Cheers !!!!