Troubleshooting

Start troubleshooting with system, service, and capacity facts.

Inspect an inactive service without restarting it.

Search multiple logs for related clues.

Compare configs before guessing at a routing issue.

Use disk and log size commands in triage.

Inspect identity and file metadata before changing modes.

Compare sockets, firewall, and config.

Use package logs to explain recent changes.

Write a rollback note from evidence.

Complete a focused triage loop.

Triage a simulated website outage from service, config, and logs.

Use disk and log evidence for storage triage.

Compare configs and hash scripts during deploy triage.

Map a listener to process and firewall evidence.

Inspect identity and modes before changing permissions.

Search auth evidence and SSH policy together.

Review package upgrade evidence during triage.

Connect cron schedule, service, and logs.

Triage inactive backup state and manifest context.

Compare active config and expected config examples.

Build a resource snapshot before blaming a process.

Capture rollback evidence before writing a note.

Collect service, log, and network evidence in one drill.

Complete a full triage loop with evidence and a final marker.

Separate local name-resolution evidence from web-service health.

Establish identity and metadata before applying a narrow repair.