Getting Data In

504 Gateway Time-out

Mohanad
Observer

We are hosting Splunk enterprise on AWS EC2 instances, the flow goes as follows:

ALB>Apache Reverse proxies>ALB>SHC<>Indexers.

after a period of times (days mostly) we start to experience 504 gateway time-out which disappears when we restart our proxies, and we go for another round and so on.
Any clues for how to troubleshoot this,
we adjusted the timeouts parameters on the application, and the application loadbalancers but the problem is still persisting.

Mohanad_0-1730201872578.png

 

0 Karma

dural_yyz
Motivator

Take a look at any TLS certificates that get issued between ALB and Proxy.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...