Deployment Architecture

Search Head Cluster Error - acceptPush: non-200 status_code=400

abalogh_splunk
Splunk Employee
Splunk Employee

Hello,

Are these error messages something to care about in a SHC on Splunk Enterprise 6.5.2? What do they mean?

Error pushing configurations to captain=h__x://SPLUNKSH:8089, consecutiveErrors=1 msg="Error in acceptPush: Non-200 status_code=400: ConfReplicationException: Cannot accept push with outdated_baseline_op_id=9d7db54d68936bf9017025f82645dec4ae96d16c; current_baseline_op_id=d0b8691592a4a2276b160e9680133672b2af1425"
0 Karma
1 Solution

abalogh_splunk
Splunk Employee
Splunk Employee

Answering my own question just to get this documented.

It can take a while for all the configurations to merge in a Search Head Cluster. If "consecutiveErrors=1" never exceeds the value of 1 it is spurious and can effectively be ignored. These messages pop up while the members of a search head cluster fight it out until they reach a common configuration baseline.

View solution in original post

abalogh_splunk
Splunk Employee
Splunk Employee

Answering my own question just to get this documented.

It can take a while for all the configurations to merge in a Search Head Cluster. If "consecutiveErrors=1" never exceeds the value of 1 it is spurious and can effectively be ignored. These messages pop up while the members of a search head cluster fight it out until they reach a common configuration baseline.

Get Updates on the Splunk Community!

Index This | Why did the turkey cross the road?

November 2025 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Enter the Agentic Era with Splunk AI Assistant for SPL 1.4

  🚀 Your data just got a serious AI upgrade — are you ready? Say hello to the Agentic Era with the ...

Feel the Splunk Love: Real Stories from Real Customers

Hello Splunk Community,    What’s the best part of hearing how our customers use Splunk? Easy: the positive ...