Getting Data In

received event and Failed to parse timestamp

yoann
New Member

Hi,

I didn't found the answer. I got splunk 5.0.1 and it worked good!
Since I've installed four apps :
-TA-cisco_asa
-Splunk_for_CiscoASA
-maps
-sideview_utils

I restart splunk , I added data syslog with UDP port 514 and I see a yellow bar with :
"received event for unconfigured/disabled/deleted index='firewall' with source='source::udp:514' host='host::192.X.X.X' sourcetype='sourcetype::cisco:asa' (1 missing total)"

And in my splunkd.log we can see :
"DateParserVerbose - Failed to parse timestamp. Defaulting to timestamp of previous event (Wed Jan 23 11:29:58 2013). Context: source::514|host::192.X.X.X|syslog|"

Would I have missed a conf ?

Thanks to help me !

Tags (1)
0 Karma

yoann
New Member

Nobody know ?

0 Karma

yoann
New Member

yeah , that's why i don't understand in /usr/local/splunk/etc/system/local/ I can see : inputs.conf README server.conf tenants.conf that's all ...

0 Karma

yoann
New Member

I proceeded otherwise, I used splunkforward and there is no message now

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

As Ayn said, there potentially are a million places that may contain configuration. To make sure you need to check each and every one.

0 Karma

yoann
New Member

I have to search indexes.conf ?

0 Karma

Ayn
Legend

system/local is one of many many places configuration files can reside in. It's not enough to check just that one.

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

The bar suggests you're trying to write events into an index 'firewall' that doesn't exist.

Compare your inputs on all forwarders with the indexes on your indexers, they likely don't fit together.

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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...