Getting Data In

Splunk not indexing the entire file.

khhenderson
Path Finder

I have a new 5.0 splunk server that is the indexer and search head.
I have one forwarder sending logs.
All is working well but!
One directory of log files. Splunk is only reading the first line of the files in this directory.
The splunkd.log

11-09-2012 08:33:43.250 -0600 INFO WatchedFile - Checksum for seekptr didn't match, will re-read entire file='/opt/jrun4/logs/server-2-event.log'.

11-09-2012 08:33:43.250 -0600 INFO WatchedFile - Will begin reading at offset=0 for file='/opt/jrun4/logs/server-2-event.log'.

Here is what is in my inputs.conf

[monitor:///opt/jrun4/logs]

crcSalt = <SOURCE>

disabled = false

I just recently add the crcSalt = <SOURCE> and restarted the forwarder. I'm still not getting the entire file indexed.

NOTE: I do have the word "SOURCE" between the greater than and less than symbols. It just didn't show up when typeing this question.

Please help.

0 Karma

Lucas_K
Motivator

Double check and see that your events are not being timestamped incorrectly and they are not appearing elsewhere in your index.

Does it still show only one event if you directly reference the source file over all time? ie. index=blah source=/opt/jrun4/logs/server-2-event.log

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!

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 ...

Think Like an Architect: Introducing the Splunk Certified Cybersecurity Defense ...

In cybersecurity, defenders respond to threats. Architects design the systems that stop them.    As ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...