As the splunk forwarder is missing python and relies on the OS python, could we not create an app "python2.7" on the deployment server and push this out to each host we manage, then use this version of python for running other splunk applications?
We need to get Python 2.7 out to the forwarders but the OS has version 2.6 and we do not want to replace this. The hosts also do not have access to the internet to download version 2.7. Thus build Python 2.7 on the deployment server and then push it out.
Found this link as well, with an answer
http://answers.splunk.com/answers/203218/errors-on-jmx-ta-using-splunk-universal-forwarders.html
Found this link as well, with an answer
http://answers.splunk.com/answers/203218/errors-on-jmx-ta-using-splunk-universal-forwarders.html
yes you can do this but not recommended, you can use any other tool like puppet etc for this...
The Splunk forwarder cannot "push out" any binary! Forwarders take in data and send it to indexers. That's it.
Even the deployment server can't manage binaries.
Sorry.
I have been able to push out some libraries and binaries from the deployment server to the forwarder by just creating and app and adding the files to this. So this looks like it should be possible. Just need to work out what is needed to get the local Python2.7 working