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.

View solution in original post

Did you miss .conf21 Virtual?

Good news! The event's keynotes and many of its breakout sessions are now available online, and still totally FREE!