Getting Data In
Provide Splunk Cloud feedback in this confidential UX survey by June 17
for a chance to win a $200 Amazon gift card!

Universal Forwarder - Repeating message TcpOutputProc - Found currently active indexer...

dlpco
Path Finder

I am getting the following messages on my forwarder running on Windows 10:

04-06-2020 18:05:52.171 -0700 INFO TcpOutputProc - Found currently active indexer. Connected to idx=192.168.218.6:9997, reuse=1.
04-06-2020 18:06:22.093 -0700 INFO TcpOutputProc - Found currently active indexer. Connected to idx=192.168.218.6:9997, reuse=1.
04-06-2020 18:06:51.934 -0700 INFO TcpOutputProc - Found currently active indexer. Connected to idx=192.168.218.6:9997, reuse=1.
04-06-2020 18:07:21.808 -0700 INFO TcpOutputProc - Found currently active indexer. Connected to idx=192.168.218.6:9997, reuse=1.
04-06-2020 18:07:51.660 -0700 INFO TcpOutputProc - Found currently active indexer. Connected to idx=192.168.218.6:9997, reuse=1.

I just updated the forwarder to 8.0.3 and these messages just keep coming. There are no disconnect messages, just these found messages.

HELP...

0 Karma

kaurinko
Path Finder

@dlpco  Try downgrading the UF to version 8.0.1. It solved my problems. I also noticed, that all the logs were not transported to the indexer during the error messages. With UF v. 8.0.1 normal operation was resumed.

Br, Petri

0 Karma

kaurinko
Path Finder

Hi,

I noticed by accident I also had this problem, and it all started when I upgraded the Universal Forwaders to version 8.1.0. Now I downgraded all UFs back to version 8.0.1 and the problems disappeared. The Indexer version was originally when the problems started to appear 8.1.0, and right now it is 8.1.0.1.

For me this was not only an annoyance. I first found the problem, when I realized some logs were not transferred to the indexer. Some trouble shooting took me to the UF version issue. In my opinion this is clearly a bug, and it should be fixed.

Best regards,

Petri

Tags (2)
0 Karma

codebuilder
Motivator

Those entries are normal and indicate successful connection between forwarder and indexer. Nothing to be concerned about, the opposite actually.

0 Karma

daniellange
New Member

Hi, 

I also get these messages, 410.000 times in 4 hours and splunkd is the most indexed data type when I look in the monitoring console.

Is this normal? (I have around 800 forwarders in total) 

 

/Daniel 

0 Karma
Take the 2021 Splunk Career Survey

Help us learn about how Splunk has
impacted your career by taking the 2021 Splunk Career Survey.

Earn $50 in Amazon cash!