Deployment Architecture

ERROR TcpChannel - Error trying to begin socket accept: An invalid argument was supplied.

alane
Engager

Upgraded Deployment Server / License Server to Version 6. Runs OK for 15 minutes then maxes out CPU and starts to fail with
ERROR TcpChannel - Error trying to begin socket accept: An invalid argument was supplied.
showing in SplunkD log.

Voltaire
Communicator

Are you using IPV6?
I had a similar issue with Splunk 6.0 build 182037. "ERROR TcpChannel - Error trying to begin socket accept: An invalid argument was supplied."
I pinged the Splunk Indexer and found that it was using IPV6 to resolve the hostname. I disabled IPV6, then added the hostname IPV4 address in the localhosts file. Restarted Splunk and it is working fine now.

0 Karma

dstaulcu
Builder

I'm experiencing this problem too.. happening among all of my indexers and all of my heavy forwarders. Clients of each type are getting "WARN TcpOutputProc - Cooked connection to ip=x.x.x.x:9997 timed out". Problem continues even after upgrading from 6.0 and 6.0.3

0 Karma
Get Updates on the Splunk Community!

NEW! Log Views in Splunk Observability Dashboards Gives Context From a Single Page

Today, Splunk Observability releases log views, a new feature for users to add their logs data from Splunk Log ...

Last Chance to Submit Your Paper For BSides Splunk - Deadline is August 12th!

Hello everyone! Don't wait to submit - The deadline is August 12th! We have truly missed the community so ...

Ready, Set, SOAR: How Utility Apps Can Up Level Your Playbooks!

 WATCH NOW Powering your capabilities has never been so easy with ready-made Splunk® SOAR Utility Apps. Parse ...