Troubleshoot a Linux service that fails to start
Collect unit state and logs before retrying a failed service; isolate configuration, permissions, dependencies, and port conflicts.
Read guide →TROUBLESHOOTING · FIELD GUIDES
Evidence-led runbooks for common Linux, networking, CI/CD, Docker, Terraform, Kubernetes, firewall, and TLS problems.
Collect unit state and logs before retrying a failed service; isolate configuration, permissions, dependencies, and port conflicts.
Read guide →Determine whether bytes or inodes are exhausted, locate the affected mount, and reclaim data through its owning application.
Read guide →Trace hostname, route, destination port, listener, and firewall path to find where an SSH connection is rejected.
Read guide →Compare system lookups with direct resolver answers to isolate local configuration, upstream reachability, and record problems.
Read guide →Capture container exit state and previous logs, then inspect launch command, environment names, mounts, and resource limits.
Read guide →Compare dependency and lockfile changes, runner versions, the first failed test, and upstream package availability.
Read guide →Read the plan’s replacement markers and compare configuration, state, provider version, workspace, and immutable attributes.
Read guide →Collect events, restart count, last termination reason, previous logs, probes, and resource limits to diagnose CrashLoopBackOff.
Read guide →Check the exact image reference, registry response, pull credentials, namespace, node network, and platform compatibility.
Read guide →Inspect validity dates, hostname, chain, and clock at the endpoint that actually terminates TLS.
Read guide →Confirm the service listener, active firewall manager, source path, and effective policy before a narrow rules change.
Read guide →Collect time-stamped capacity and pressure data before restarting services or resizing a host.
Read guide →