log analyzer minio

    1

    Diagnostic tool for MinIO infrastructure logs, identifying quorum loss, drive failures, and S3 API errors.

    $1

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+22 more

    log analyzer minio

    Example session with this skill installed

    Analyze these logs
    ERROR: Drive /mnt/drive2 is not writable.
    API: PutObject(bucket=assets, object=logo.png)
    Time: 2023-10-27T10:00:05Z
    Status: 507 Insufficient Storage.
    Nodes: 4 nodes, 1 drive per node.

    • Read your context and instructions
    • Compiled the log analyzer minio

    I have analyzed the provided logs regarding the Insufficient Storage error on your 4-node cluster.

    REPORTE DE ANÁLISIS DE LOG — MINIO

    📋 RESUMEN EJECUTIVO
    TecnologíaMinIO Distributed
    EntornoNo declarado
    Componente(s)Node: /mnt/drive2
    Período log2023-10-27 10:00:05Z
    Total eventos1 crítico
    DiagnósticoEl clúster ha perdido el quorum de escritura debido a un fallo en el disco /mnt/drive2.

    🔴 HALLAZGOS CRÍTICOS

    Quorum Loss: En un clúster de 4 nodos con 1 drive por nodo (4 total), el erasure coding requiere usualmente N/2 drives para lectura y N/2+1 para escritura. Con 1 drive caído (/mnt/drive2), el clúster entra en modo read-only si no se alcanza el umbral de escritura.

    Hardware Failure: El error Drive is not writable indica un fallo físico o un problema de montaje a nivel de sistema operativo en el punto de montaje /mnt/drive2.

    🟡 ADVERTENCIAS

    Insufficient Storage: Este código 507 no significa que el disco esté lleno, sino que no hay suficientes drives "healthy" disponibles para completar el set de erasure coding.

    ❓ PREGUNTAS ABIERTAS / 🛠️ PRÓXIMOS PASOS

    1. Verifique el estado del hardware del disco en el nodo afectado usando smartctl.
    2. Ejecute mc admin heal una vez que el disco sea reemplazado o vuelto a montar.
    3. ¿Cuál es la versión exacta del servidor para confirmar el comportamiento de quorum?

    Next steps

    • Replace or re-mount the drive at /mnt/drive2.
    • Run mc admin info to verify the status of the remaining 3 drives.
    • Monitor the healing process using mc admin heal.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    Debug and resolve MinIO storage infrastructure issues by analyzing raw log data. This skill identifies root causes across standalone, distributed, and Kubernetes Operator environments. It targets specific S3 error codes, signature mismatches, and hardware-level drive failures that impact high-availability clusters.

    What it does

    • S3 Error Diagnosis identifies specific causes for AccessDenied, NoSuchBucket, and SignatureDoesNotMatch errors.
    • Cluster Health Assessment detects quorum loss, drive failures, and node connectivity issues in distributed deployments.
    • Clock Skew Detection flags RequestTimeTooSkewed errors caused by NTP desynchronization between clients and servers.
    • Healing Monitoring tracks the status of drive replacements and background healing operations to prevent premature performance alerts.
    • Sensitive Data Redaction highlights and flags exposed Access Keys, Secret Keys, and presigned URLs in log outputs.

    How it works

    1. Log Input Provide raw log snippets containing minio references, X-Amz-Request-Id headers, or mc admin command outputs.
    2. Environment Context Specify if the deployment is standalone, distributed, or a Kubernetes Tenant to determine quorum logic.
    3. Structured Analysis The agent parses the logs against known patterns like Insufficient storage or Drive not writable.
    4. Diagnostic Reporting Receive a structured executive summary including total event counts and critical findings.

    Frameworks & tools

    Works with MinIO Server (standalone/distributed), MinIO Kubernetes Operator, and MinIO Client (mc).

    Why this beats prompting it yourself

    Standard LLMs often confuse generic S3 errors with MinIO-specific quorum logic and erasure coding requirements. This skill applies precise thresholds for drive failures and networking peer connectivity that are unique to MinIO's architecture.

    Use cases

    • Troubleshoot why a distributed cluster has lost write quorum despite nodes being online.
    • Debug authentication failures caused by local clock drift or rotated credentials.
    • Verify if a drive replacement is successfully healing or if the disk is physically faulty.
    • Audit logs for leaked credentials or internal bucket structures before sharing data.

    Known limitations

    Does not perform active repairs or execute mc commands directly. Requires manual input of node and drive counts for accurate quorum analysis.

    How to use

    Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill passes our trust checks below.

    Security scanned

    Passed our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scanned

    Verified clean today

    • Passed all security checks, Safe to install

    Listedtoday

    What's inside

    Frequently Asked Questions