Getting Data In

Splunk "destroying" a TCP connection

TheJagoff
Communicator

Hello. I noticed on a U/F, "Splunk destroying TcpOutputClient during shutdown/reload" as a level INFO and happens 4 or 5 times a minute for each of the 3 indexers.
The U/F has been running for quite some time and is not in a shutdown/reload situation and I am receiving events both _internal and OS data from the TA_Splunk_nix  from it.
Is destroying a connection a normal message and what would cause that? I can't seem to find anything online about this message.

Labels (2)
0 Karma
1 Solution

kiran_panchavat
SplunkTrust
SplunkTrust

@TheJagoff 

Please take a look. Is it related to the same?

Fixed issues - Splunk Documentation

Slow indexer/receiver detection capability - Splunk Community

Splunk crash during tcpout (outputs.conf) reload - Splunk Community

 

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

View solution in original post

kiran_panchavat
SplunkTrust
SplunkTrust

@TheJagoff 

Please take a look. Is it related to the same?

Fixed issues - Splunk Documentation

Slow indexer/receiver detection capability - Splunk Community

Splunk crash during tcpout (outputs.conf) reload - Splunk Community

 

Did this help? If yes, please consider giving kudos, marking it as the solution, or commenting for clarification — your feedback keeps the community going!

TheJagoff
Communicator

Looking through the 2nd article that you suggested, it was noticed that the outputs.conf had 
autoLBFrequency = 15
forceTimebasedAutoLB = true

Removed forceTimebasedAutoLB = true and the message stopped after the U/F restarted. It appears that the 2 entries were conflicting with each other.

Thank you for the guidance!

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