topic Re: Universal Forwarder - Repeating message TcpOutputProc - Found currently active indexer... in Getting Data In

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

dlpco — Tue, 07 Apr 2020 01:20:03 GMT

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

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

codebuilder — Fri, 17 Apr 2020 16:20:16 GMT

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

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

daniellange — Tue, 24 Nov 2020 05:46:50 GMT

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

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

kaurinko — Wed, 25 Nov 2020 14:07:25 GMT

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

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

kaurinko — Mon, 30 Nov 2020 09:50:49 GMT

@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

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

Navaneedhan — Thu, 14 Mar 2024 22:30:28 GMT

@codebuilder

i got the same message, but in the splunk i don't find any logs.
What is the problem ?