Troubleshooting

Troubleshooting guides help you diagnose and resolve common problems with your Quake AI workloads. Each guide follows a symptom-first structure: start with what you observe, narrow down the cause, and apply a targeted fix.

When something goes wrong, follow this general diagnostic pattern:

1. Identify the symptom: what exactly is failing? An SSH connection timeout, an API error code, an instance stuck in a build state?
2. Check recent changes: did you modify a security group, rotate credentials, resize an instance, or update a configuration?
3. Isolate the layer: is the problem at the network level (security groups, floating IPs), the instance level (OS, application), or the platform level (API errors, quota limits)?
4. Gather evidence: collect logs, error messages, and resource status before making changes. Use openstack server show, openstack console log show, and instance system logs.
5. Apply and verify: make one change at a time and verify whether it resolves the issue before proceeding.

Common symptoms quick reference#

See also#

• Error response format: JSON and XML error structure, fault objects, request correlation, parsing examples
• Retry and resilience patterns: exponential backoff, jitter, idempotency, and which errors are retryable
• API rate limits: quotas vs. rate limits, 429 handling
• Operate overview
• Runbooks
• Monitoring