[splunk@server splunkforwarder]$ ls
bin etc ftr lib license-eula.txt openssl README-splunk.txt share splunkforwarder-4.3-115073-Linux-x86_64-manifest
[splunk@server splunkforwarder]$ cd etc/apps
[splunk@server apps]$ ls
learned search SplunkUniversalForwarder
[splunk@server etc]$ cd ../bin
[splunk@server bin]$ ./splunk cmd python
couldn't run "/home/splunk/splunkforwarder/bin/python": No such file or directory
http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Introducingtheuniversalforwarder
Unlike full Splunk, the universal forwarder does not include a bundled version of Python.
OK, so just to recap:
universalforwarder (splunkforwarder) does not include python.
Splunk (full version) with LWF or HF enabled does include python.
Ayn, I removed some lines to cover my internal information but just trust that part of it is working correctly.
How did you end up in /home/splunk/splunkforwarder/bin
by doing cd ..
from etc/apps
? 😉
http://docs.splunk.com/Documentation/Splunk/latest/Deploy/Introducingtheuniversalforwarder
Unlike full Splunk, the universal forwarder does not include a bundled version of Python.
Nope. This was a design decision for the 'universal forwarder' to not include python.
LWF HF and indexer do include python.
Not the UF.