Troubleshooting and recovering a Linux server
Find out why a server broke and fix it — from a broken symlink to a 502 behind a proxy.
- Broken symlinkeasy
- Cron doesn't runeasy
- A file owner broke accesseasy
- A local name won't resolveeasy
- SSH rejects the key: permissions too openeasy
- Process leakeasy
- A broken PATH breaks the scriptmedium
- The app can't see the variablemedium
- Environment variables and PATHinterview questionmedium
- Broken JSON configmedium
- The app reads a stale configmedium
- The forgotten lock fileeasy
- A runaway process is hogging the CPUmedium
- Port taken by another processmedium
- The service listens on the wrong addressmedium
- Who filled up the diskmedium
- The log is filling up the diskmedium
- An old release is hogging the diskhard
- File deleted, but space not freedhard
- Service hangs without respondingmedium
- The site returns 403medium
- nginx won't start after an editmedium
- The warehouse answers 502hard
- 4xx, 5xx, 502 and 504interview questioneasy