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
Get Updates on the Splunk Community!

CX Day is Coming!

Customer Experience (CX) Day is on October 7th!! We're so excited to bring back another day full of wonderful ...

Strengthen Your Future: A Look Back at Splunk 10 Innovations and .conf25 Highlights!

The Big One: Splunk 10 is Here!  The moment many of you have been waiting for has arrived! We are thrilled to ...

Now Offering the AI Assistant Usage Dashboard in Cloud Monitoring Console

Today, we’re excited to announce the release of a brand new AI assistant usage dashboard in Cloud Monitoring ...