It seems that about 1 in every 1000 installations of the app result in the classpath being improperly constructed by the Python script that starts Flume.
You can resolve this issue by editing the following lines in /%SPLUNK_HOME%/etc/apps/compuwareapm/bin/runFlume.py:
c1 = os.path.join(appdir, "bin", "apache-flume-1.3.1-bin", "lib", "*")
c2 = os.path.join(appdir, "bin", "apache-flume-1.3.1-bin", "lib", "flume-ng-node-1.3.1.jar")
c3 = os.path.join(appdir, "bin", "dtFlume.jar")
remove the leading "bin" so that the lines read:
c1 = os.path.join(appdir, "apache-flume-1.3.1-bin", "lib", "*")
c2 = os.path.join(appdir, "apache-flume-1.3.1-bin", "lib", "flume-ng-node-1.3.1.jar")
c3 = os.path.join(appdir, "dtFlume.jar")
I have been unsuccesfully trying to nail down the source of this issue for quite some time, It appears that on some Splunk environments appdir = os.path.dirname(os.path.dirname(__file__)) will result in /%SPLUNK_HOME%/etc/apps/compuwareapm and in other environments it will result in /%SPLUNK_HOME%/etc/apps/compuwareapm/bin.
... View more