← All courses

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.

22 tasks · 2 questions
  1. Broken symlinkeasy
  2. Cron doesn't runeasy
  3. A file owner broke accesseasy
  4. A local name won't resolveeasy
  5. SSH rejects the key: permissions too openeasy
  6. Process leakeasy
  7. A broken PATH breaks the scriptmedium
  8. The app can't see the variablemedium
  9. Environment variables and PATHinterview questionmedium
  10. Broken JSON configmedium
  11. The app reads a stale configmedium
  12. The forgotten lock fileeasy
  13. A runaway process is hogging the CPUmedium
  14. Port taken by another processmedium
  15. The service listens on the wrong addressmedium
  16. Who filled up the diskmedium
  17. The log is filling up the diskmedium
  18. An old release is hogging the diskhard
  19. File deleted, but space not freedhard
  20. Service hangs without respondingmedium
  21. The site returns 403medium
  22. nginx won't start after an editmedium
  23. The warehouse answers 502hard
  24. 4xx, 5xx, 502 and 504interview questioneasy