topic Re: Splunk unix app not receiving inputs in Getting Data In

Splunk unix app not receiving inputs

remy06 — Thu, 18 Nov 2010 09:51:11 GMT

Hi,

I've enabled some of the inputs for the unix app via its configuration page.After selecting those inputs to be enabled,I've saved it but still it doesn't seem to be receiving any inputs.

I've checked again at Manager>Data inputs>Scripts and those input scripts that I've selected are marked as Enabled.

I've also tried restarting Splunk services but no input as well.

Is there something I've missed?

Fyi,splunk is installed on CentOS.

Re: Splunk unix app not receiving inputs

bwooden — Thu, 18 Nov 2010 12:01:44 GMT

By default, the Nix app will store its data in the OS index.

You may need to add "index=os" to the beginning of your search as well.

You could also add OS to the list of selected roles via the Manager -> Access controls -> Roles.

Re: Splunk unix app not receiving inputs

remy06 — Thu, 18 Nov 2010 14:22:22 GMT

When I do a search for index=os,nothing shows up.
When I'm at the Over>About Splunk for Unix page, there is still no Hosts,Sourcetypes and Sources listed.

Re: Splunk unix app not receiving inputs

remy06 — Wed, 24 Nov 2010 10:42:55 GMT

I've did a check on splunkd logs and found number of errors like this:

11-24-2010 10:33:37.162 ERROR ExecProcessor - message from "/opt/splunk/etc/apps/unix/bin/top.sh" /bin/sh: /opt/splunk/etc/apps/unix/bin/top.sh: /bin/sh^M: bad interpreter: No such file or directory

They do exist..

Re: Splunk unix app not receiving inputs

remy06 — Thu, 02 Dec 2010 10:09:30 GMT

Any idea on this??

Re: Splunk unix app not receiving inputs

mikelanghorst — Thu, 09 Dec 2010 00:48:03 GMT

From your log output, you show "/bin/sh^M". Did you copy the files from another non unix host? It looks like you may have a dos->unix file translation issue. Go to /opt/splunk/etc/apps/unix and "dos2unix top.sh" and see if that clears that error message.

Re: Splunk unix app not receiving inputs

somchatt78 — Fri, 21 Oct 2016 13:30:33 GMT

above answer did not solve problem, even after manually adding role OS, did not solve the issue