All Apps and Add-ons

NMON Performance Monitor for Unix and Linux Systems: Manually running nmon_helper.sh fails with message "terminated"

jmantor
Path Finder

Per the troubleshooting guide we tried this :

[splunk@blahblahblah]$ /opt/splunkforwarder/bin/splunk cmd /opt/splunkforwarder/etc/apps/TA-nmon/bin/nmon_helper.sh
Terminated

It didn't start the nmon process and doesn't seem to give an indication of why ?

0 Karma

guilmxm
Influencer

Hi!

This looks to me very strange, in the worst case and if things went bad you have much more output than that.

Question:

  • Have you extracted the TA content in a Windows workstation ? I would be tended to think that the content of scripts has been trans-coded during the transfer step (it is probably currently in Windows format instead of Unix, it should be UTF8)

To say this differently you probably have ^M symbols in the file.

  • Check the permission (is the file executable ?, by default it is maybe you lost this because of the way you extracted or transfered it to your deployment server)

I would strongly recommend transferring the tgz archive and then extract it on the deployment server if you are using one, or on the UF if you are not using deployment server

Guilhem,

0 Karma

jmantor
Path Finder

What should we look at to troubleshoot further?

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Casting Call: Compete in Cyber Games

Lights, Camera, SecOps: Apply to Compete in Cyber Games     Think you have what it takes to beat the clock? ...

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

How Edge Processor's Durable Queue Works

Edge Processor sits in one of the most consequential places in any Splunk pipeline: between your data sources ...