Getting Data In

Why has source stopped indexing?

heloma
Engager

hi,

I have 2 source A and B (routers), they are sending the data over udp port 514.

all of the sudden, the source B is not indexed anymore.

I have captured the traffic (tcpdump), I can see clearly that the traffic is reaching the Splunk server.

My Splunk deployment is a free license all-in-one server.

any thoughts ?

 

thanks.

 

heloma

Labels (2)
0 Karma

PickleRick
SplunkTrust
SplunkTrust

Do you have more than one interface in the server? If you didn't add any restrictions on firewall or in input configuration (did you check your config with btool?), maybe it's an issue with rpfilter (I assume you're running your system on linux)

0 Karma

VatsalJagani
SplunkTrust
SplunkTrust
  • Please check if your input is still there.
  • Make sure tcpdump shows data for source B.
  • Check for any new configuration added/updated after which data stopped indexing.
  • Check splunkd logs for errors and warnings.
    • index=_internal sourcetype=splunkd CASE(ERROR) OR CASE(WARN*)

I hope this helps!!!

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