Troubleshoot Uwsgi

When to use this skill

• Worker exhaustion: All workers busy, requests queue in the kernel backlog, then
• Harakiri storm: Workers are killed and respawned faster than they can serve
• Memory creep: Workers grow over time until OOM-killed or recycled by
• Stuck workers: Workers hang on blocking I/O (database lock, slow external call)
• Reload failure: SIGHUP reload with broken application code leaves zero
• Any time the user reports a Uwsgi service behaving outside its expected envelope (elevated errors, latency, saturation, resource exhaustion, or unexpected restarts).
• An on-call engineer is paging on a Netdata alert tied to a Uwsgi instance and wants a structured triage path.

Key facts