crashloop
Skill0 starsChanged 31 days agoMITView on GitHub
Investigar pods em CrashLoopBackOff ou com restarts repetidos.
In this repository4 other files it gives its agents.
- cpu-throttlingSkill
- latency-spikeSkill
- oom-killedSkill
- report-formatSkill
The file
Files
CrashLoopBackOff
Investigar, nesta ordem
- Logs do container anterior (
previous) — a causa costuma estar no final. exitCode: 1/2 erro de aplicação; 137 OOM/kill; 139 segfault; 143 SIGTERM.- Probes (liveness/readiness) com timeout ou caminho inválido.
- ConfigMap/Secret/variável de ambiente ausente ou inválida.
- Dependência indisponível (DB, serviço) no start.
- Mudança recente de imagem/config.
Ação sugerida
Apontar a evidência exata (linha de log ou evento) e a correção correspondente.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.