Knowledge Management

Persistent queue problems

hrawat_splunk
Splunk Employee
Splunk Employee

If you are using persistent queue, you are likely to see following errors in splunkd.log 

 

 

ERROR TcpInputProc - Encountered Streaming S2S error

1. "Cannot register new_channel"

2. "Invalid payload_size"

3. "Too many bytes_used"

4. "Message rejected. Received unexpected message of size"

5. "not a valid combined field name/value type for data received"

 

 

Many other streaming S2S streaming errors.
 
If your deployment is impacted, you should upgrade your HF/IHF/IUF/IDX instance that is using persistent queue to following patches.
9.3.2/9.2.4/9.1.7

This patch also fixes all the PQ related crashes and other PQ issues. 
With 9.3.2/9.2.4/9.1.7 there are no known PQ issues.

Labels (1)
Tags (1)
Get Updates on the Splunk Community!

Introduction to Splunk Observability Cloud - Building a Resilient Hybrid Cloud

Introduction to Splunk Observability Cloud - Building a Resilient Hybrid Cloud  In today’s fast-paced digital ...

Observability protocols to know about

Observability protocols define the specifications or formats for collecting, encoding, transporting, and ...

Take Your Breath Away with Splunk Risk-Based Alerting (RBA)

WATCH NOW!The Splunk Guide to Risk-Based Alerting is here to empower your SOC like never before. Join Haylee ...