Getting Data In

ERROR TailingProcessor - Ignoring path due to: This key could not be found : _MetaData:Index

FRoth
Contributor

I checked out the new Universal Forwarder and ran into some problems that I dont understand.
First I configured the forwarder by creating a "output.conf" and "input.conf" in /opt/splunkforwarder/etc/system/local.

The content of output.conf:

[tcpout:indexerNeo]

server=mapache.server.org:55515

The content of input.conf:

[monitor:///var/log/apache2/modsec_audit.log]

sourcetype=modsec

I got some errors in the splunkd.log that I dont understand:

05-03-2011 15:35:14.993 +0000 WARN TcpOutputProc - Pipeline data does not have indexKey. [_path] = /var/log/apache2/modsec_audit.log

[_startOffset] = 38875

[_fnameCrc] = 9536363811639999154

[_seekCrc] = 8646198035968417993

[_fishKey] = 15451249598830936081

[_modTime] = 1304436775

[_raw] =

[MetaData:Source] = source::/var/log/apache2/modsec_audit.log

[MetaData:Host] = host::s152188.onlinehome-server.info

[MetaData:Sourcetype] = sourcetype::modsec

[_done] = _done

[_hpn] = _hpn

[_conf] = source::/var/log/apache2/modsec_audit.log|host::s152188.onlinehome-server.info|modsec|

05-03-2011 15:35:16.714 +0000 ERROR TailingProcessor - Ignoring path due to: This key could not be   found : _MetaData:Index

Is there anybody who can help me?

0 Karma
1 Solution

FRoth
Contributor

Ok, I did it. I had to set an index to write the input to.

I added and index and then the line in "input.conf" file:

[monitor:///var/log/apache2/modsec_audit.log]

sourcetype=modsec

index=modsec

View solution in original post

FRoth
Contributor

Ok, I did it. I had to set an index to write the input to.

I added and index and then the line in "input.conf" file:

[monitor:///var/log/apache2/modsec_audit.log]

sourcetype=modsec

index=modsec

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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...