Server Unresponsiveness from High Load or Network Issues

critical

Resource ContentionUpdated Feb 23, 2026

Nomad server becomes unresponsive with CLI commands hanging, Web UI failing to load, or API requests not processing, typically due to CPU/memory exhaustion or network connectivity problems.

Sources

Nomad Nomad server not responding - Stack Diagnosis - DrDroiddrdroid.io

Technologies:

PrometheusPrometheus metrics correlate with this issue and help confirm diagnosis

GrafanaGrafana metrics correlate with this issue and help confirm diagnosis

How to detect:

Monitor for API timeouts, CLI command hangs, Web UI load failures, and API request processing delays. Track server CPU and memory usage, network latency, and packet loss.

Recommended action:

Assess server CPU and memory usage with monitoring tools. If overloaded, scale cluster by adding servers. Verify network connectivity using ping/traceroute. Check firewall rules and security groups allow traffic to/from Nomad servers. Review server logs for errors.