| Infra | redis, dind, litellm, registry-cache | | Orchestration | scheduler, task-server, task-downloader, scratch-cleaner | | Fuzzing | build-bot, fuzzer-bot, coverage-bot, tracer-bot, merger-bot | | Analysis | patcher, seed-gen, program-model, pov-reproducer | | Interface | competition-api, ui |
High restart counts don't necessarily mean an issue is ongoing -- restarts accumulate over a pod's lifetime. Always distinguish:
When many pods restart around the same time, check for a shared-dependency failure before investigating individual pods. The most common cascade: Redis goes down -> every service gets ConnectionError/ConnectionRefusedError -> mass restarts. Look for the same error across multiple --previous logs -- if they all say redis.exceptions.ConnectionError, debug Redis, not the individual services.
Depura el Buttercup CRS (Cyber Reasoning System) que se ejecuta en Kubernetes. Úselo al diagnosticar fallas de pod, bucles de reinicio, fallas de Redis, presión de recursos, saturación de disco, problemas de DinD o cualquier mal comportamiento del servicio en el espacio de nombres crs. Cubre clasificación, análisis de registros, inspección de colas y patrones de falla comunes para: redis, fuzzer-bot, cover-bot, seed-gen, patcher, build-bot, programador, servidor de tareas, descargador de tareas, modelo de programa, litellm, dind, tracer-bot, merger-bot, Competition-api, pov-reproducer, scratch-cleaner, registro-cache, image-preloader, ui. Fuente: trailofbits/skills.