Splunk SOAR

SOAR 6.3.1 Supervisord Fails to Start on Warmstandby

mpc7zh
Explorer

This is the error I get when trying to start SOAR on the Warmstandby:

Splunk SOAR is in standby. Starting all services except automation daemons
Starting Database server (PostgreSQL): [ OK ]
Starting Connection pooler (PgBouncer): [ OK ]
Checking database connectivity: [ OK ]
Checking component versions: [ OK ]
Starting Supervisord: [ OK ]
Starting Splunk SOAR daemons: [ OK ]
Checking Supervisord processes: [FAILED]
add_to_es_index failed to start. Check /opt/soar/var/log/phantom/add-es-index-stderr.log for more info.
Splunk SOAR startup failed.
 

I saw there is a known issue for this: https://docs.splunk.com/Documentation/SOARonprem/6.3.1/ReleaseNotes/KnownIssues

2024-12-03PSAAS-20901supervisord failing to start on warm standby instance

 

Does anyone have a workaround or fix for this issue?

Labels (1)
0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Community Content Calendar, September edition

Welcome to another insightful post from our Community Content Calendar! We're thrilled to continue bringing ...

Splunkbase Unveils New App Listing Management Public Preview

Splunkbase Unveils New App Listing Management Public PreviewWe're thrilled to announce the public preview of ...

Leveraging Automated Threat Analysis Across the Splunk Ecosystem

Are you leveraging automation to its fullest potential in your threat detection strategy?Our upcoming Security ...