Python 2.7 present and shouldn't be

[cmuesing]

I am getting an integrity check error on /opt/splunk/bin/python2.7 that says present_but_shouldnt_be. I can find the write protected file python2.7 in that path. Is this just as simple as deleting it? Is there some uninstall I need to run? 

[sadiq_aziz]

same having this issue when we upgraded to 9.2.3

looks like Splunk installation files installed python 2.7 by default

[dural_yyz · Accepted solution]

Extracting Splunk 9.3.0 on a linux build I see a file in the /opt/splunk/ called splunk-9.3.0-<buildhash>-linux-2.6-x86_64-manifest.  That file lists every directory and file along with permission codes that should exist for your install.  The integrity checks are based upon that manifest file.  If you have a 2.7 folder still inside your install you should be safe to delete it, especially if the folder has zero hidden or displayed files/folders.

[cmuesing]

Thank you. I deleted the file and it worked great. 

[computermathguy]

We just upgraded from 9.2.2 to 9.2.3 and started getting the python integrity warnings.

 

File path                              Check result                                File path                                         Check result

/opt/splunk/bin/jp.py

present_but_shouldnt_be

/opt/splunk/bin/python2.7

present_but_shouldnt_be

[sampath_v]

We are facing the same challenge. Did you get a solution to this issue? I have upgraded to 9.2.3 recently.

[pmerlin1]

Hi , same issue for me, I deleted these files : 
/opt/splunk/bin/python2.7
/opt/splunk/bin/jp.py
and i restarted Splunk
Then the messages disappeared

[cmuesing]

We deleted Python 2.7.

[dural_yyz]

No matter which version you upgrade to you can always reference the manifest file.  If the manifest does not list the file in the warning then it can be deleted.