Getting Data In

TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":

aagehh
New Member

Hi

I get al lot of the following messages on my IX:
TcpInputProc - Encountered S2S Exception=Invalid _meta atom: for key="Caption":
Can anyone explain what this error messages indicate?

0 Karma

isoutamo
SplunkTrust
SplunkTrust

The reason for this was that there was one wrongly named sourcetype (unsupported character) on props.conf.

Before upgrade to 7.x.x it was worked without any errors, but after update it start to write this message to internal log. It also gives error "WARN TcpOutputProc - Possible duplication of events with channel=source::tcp:10514". That also vanished after fixing sourcetype name.

--
Ismo

0 Karma

isoutamo
SplunkTrust
SplunkTrust

We have the same issue after updated from 6.6.5 to 7.3.2.

Also our HF -> IDX (cluster) traffic has stalled after that. HF said that IDX stops receiving events and on IDX side the haven't found any (real) reason for that yet. All resources seems to be ok even indexers didn't take events in.

r. Ismo

0 Karma

skalliger
Motivator

I'd probably do the upgrade again, on both sides (IDX and HF). Are HF and IDX on the same version or did only the IDX got upgraded?

Skalli

0 Karma

isoutamo
SplunkTrust
SplunkTrust

All nodes has the same splunk version.

Ismo

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Thanks for the Memories! Splunk University, .conf25, and our Community

Thank you to everyone in the Splunk Community who joined us for .conf25, which kicked off with our iconic ...

Data Persistence in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. What happens if the OpenTelemetry collector ...

Introducing Splunk 10.0: Smarter, Faster, and More Powerful Than Ever

Now On Demand Whether you're managing complex deployments or looking to future-proof your data ...