Getting Data In

splunk universal forwarder

kowsikreddy
Loves-to-Learn

Hi

Actually we are forwarding  data from 2 forwarders servers to the indexer server, from one  forwarder server we are receiving the data in indexer server and in search head also we can see data but we are not receiving the data in indexer server from other forwarder server.

Even in the forwarder server logs we can see it is connected to indexer but logs are not getting forward to the indexer server.

 

We can see below logs in splunkd  as below

 

12-07-2020 12:38:07.059 +0100 INFO  TcpOutputProc - Connected to idx=xx.xx.xx.xx:9998, pset=0, reuse=0.

12-07-2020 12:38:07.091 +0100 INFO  WatchedFile - Will begin reading at offset=20396720 for file='E:\Apps\SplunkUniversalForwarder\var\log\splunk\metrics.log'.

12-07-2020 12:38:07.106 +0100 INFO  WatchedFile - File too small to check seekcrc, probably truncated.  Will re-read entire file='E:\Apps\SplunkUniversalForwarder\var\log\splunk\license_usage.log'.

12-07-2020 12:38:07.153 +0100 INFO  WatchedFile - File too small to check seekcrc, probably truncated.  Will re-read entire file='E:\Apps\SplunkUniversalForwarder\var\log\splunk\remote_searches.log'.

 

Below log  can see in helat.log

TCPOutAutoLB-0 - More than 70% of forwarding destinations have failed

 

Outputs.conf file

[tcpout]

defaultGroup = lb

[tcpout:lb]

server =xxx.xxx.com:9998

autoLB = true

Labels (2)
0 Karma

kowsikreddy
Loves-to-Learn

Thanks @96nick 

 

Actaully we are using outputs.conf in other folder also (E:\APPS\SplunkUniversalForwarder\etc\system\local) apart from E:\APPS\SplunkUniversalForwarder\etc\apps\SplunkUniversalForwarder\local due to that it is processing data to old indexer server

0 Karma

96nick
Communicator

A few things I'd look at first:

  1. Do a diff on each of the files in your config that have to do with forwarding to see if there are any differences
  2. Check the _internal logs on your server
  3. Check the networking

You didn't mention if the two forwarders were on the same or different networks, but if they are there could be a firewall blocking the events from arriving to your indexer. Run a search on your indexer like  "index=_internal source=*splunkd.log host={your-host-that-doesn't-work}" and see what shows up.

Run a search for that specific host on your indexer with 'All Time'. Sounds crazy, but the timestamps might be wack. Also make sure you can view the index you are sending your data (especially if you recently created your user account). I know I've made that mistake before :). 

Official docs regarding your issue:

https://docs.splunk.com/Documentation/Splunk/latest/Troubleshooting/Cantfinddata#Are_you_using_forwa...

 

Hope that helped!

 

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!

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...

SplunkTrust Application Period is Officially OPEN!

It's that time, folks! The application/nomination period for the 2026-2027 SplunkTrust is officially open. If ...