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!

Accelerating Observability as Code with the Splunk AI Assistant

We’ve seen in previous posts what Observability as Code (OaC) is and how it’s now essential for managing ...

Integrating Splunk Search API and Quarto to Create Reproducible Investigation ...

 Splunk is More Than Just the Web Console For Digital Forensics and Incident Response (DFIR) practitioners, ...

Congratulations to the 2025-2026 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...