A useful Linux health review should answer four questions: is the server available, does it have enough capacity, is it controlled securely, and can it be recovered? The checklist below gives infrastructure teams a practical starting point without assuming a specific Linux distribution.

1. Availability and service state

  • Confirm current uptime and recent reboots
  • Review failed system services and repeated restart patterns
  • Check scheduled jobs and batch workloads for failures
  • Verify time synchronisation and DNS resolution

2. Capacity and performance

  • Review CPU saturation rather than a single CPU snapshot
  • Check memory pressure, swap activity and out-of-memory events
  • Inspect filesystem usage, inode use and growth trends
  • Identify I/O latency and processes causing sustained load

3. Security and change control

  • Review pending security updates and patch history
  • Audit privileged accounts, sudo access and inactive users
  • Confirm firewall rules match the intended service exposure
  • Review authentication failures and unexpected listening services

4. Recovery readiness

  • Confirm backup jobs completed successfully
  • Verify restoration steps are documented and periodically tested
  • Record dependencies, service owners and escalation contacts
  • Document the next maintenance actions with clear priority