Hi there,
I'm getting errors while trying to run NMON 1.8.1 on Splunk 6.5.1. This is on a Debian 8 box on x86_64:
root@monitor:/opt/splunk/etc/apps# uname -a
Linux monitor 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt25-1 (2016-03-06) x86_64 GNU/Linux
root@monitor:/opt/splunk/etc/apps# cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
NAME="Debian GNU/Linux"
VERSION_ID="8"
VERSION="8 (jessie)"
ID=debian
HOME_URL="http://www.debian.org/"
SUPPORT_URL="http://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@monitor:/opt/splunk/etc/apps#
I've only got a single Splunk instance; no forwarders, no remote machines, just the one box that eats local files like syslog and sim-trap data.
It seems that the nmon_helper.sh script that runs doesn't think that the OS is suitable for the nmon app, but I can run the app manually, and it seems fine:
ERROR, could not find an nmon binary suitable for this system, please install nmon manually and set it available in the user PATH
Also, I'm unsure what this particular error means, or if it's there because of the nmon binary issue error above.
ERROR ExecProcessor - message from "/opt/splunk/etc/apps/TA-nmon/bin/nmon_cleaner.sh --cleancsv" The Nmon repository location /opt/splunk/var/log/nmon/var/nmon_repository could not be found, We tried: /opt/splunk/var/log/nmon/var/nmon_repository
I just deleted the NMON Performance Monitor for Unix and Linux Systems, TA-nmon - Technical Addon for Nmon Performance Monitor, and TA_nmon_selfmode from $SPLUNK_HOME/etc/apps, re-started, re-installed nmon from SB, and extracted TA-nmon*.tgz from apps/nmon/resources, restarted again, deleted and re-created the nmon index, and still I'm seeing the same issues.
My google-fu seems to be failing me; I can't find any pointers on where to look to try and resolve the error, and if the above error about installing nmon manually is accurate, I can't find any documentation on how to do that.
Any ideas?
Thanks in advance!
In addition, please do not deploy in the same time the TA-nmon and the TA-nmon_selfmode.
Only one TA-nmon must be deployed in the same time
Thanks. I was following the documentation:
http://nmon-for-splunk.readthedocs.io/en/latest/installation_standalone.html
It made reference to this command: tar -xvf /opt/splunk/etc/apps/nmon/resources/TA-nmon*.tgz
And in the resources directory in the core app file, it had nmon and nmon_selfmode.
Right I see.
That's true, it was written before I provided the TA-nmon_selfmode, I have added a caution message on the doc.
Was this the root cause of your issue?
I have verified on my side, Debian 8 works perfectly fine, so I couldn't reproduce (but I haven't tested having both TA deployed)
I don't know if that was the root cause. I installed nmon manually and deleted selfmode, so I'm not sure which actually fixed it 🙂
Ok thank you 😉
I see, I just tested in a virtual machine, Debian 8 all fresh, Splunk and both TA-nmon causes even no trouble.
And the nmon binary starts with no trouble either.
If you have time for this, and want to help understanding the issue, you could:
Then, edit the "nmon_helper.sh", comment out "set -x" at the very beginning of the script.
And run:
/opt/splunk/bin/splunk cmd /opt/splunk/etc/apps/TA-nmon/bin/nmon_helper.sh
And send me by mail the output (you can contact me by Spunk base app home page) or pastbin, or whatever you like.
Thank you
And just rever the mv when you are done.
Hi !
Ok, I will check this, not sure why because the binary for Debian 8 is included in nmon binaries.
You can solve this very easily, if the nmon_helper.sh cannot find a suitable binary, it will try to run the one available in your path.
So, just:
sudo apt-get install nmon
And you will be good