This routine provides a fast, repeatable sanity check of core system resources on a DirectAdmin-managed VPS. It is designed to confirm that disk usage, memory availability, and system load are within expected bounds before or after routine maintenance, updates, or when performance concerns arise.
Scope and intent
- Detect resource exhaustion early
- Confirm the server is operating within normal parameters
- Provide a baseline check usable in many operational contexts
- Support decision-making before deeper investigation
When to run this routine
- After server, web server, or DirectAdmin updates
- After a reboot
- When performance degradation is reported or suspected
- As part of regular operational review
Prerequisites
- Root or administrative shell access
- Familiarity with expected baseline resource usage for this VPS
1. Disk usage check
- Review total disk usage and available space on all mounted filesystems
- Confirm no filesystem is unexpectedly near capacity
- Pay special attention to system partitions and mail or backup storage locations
- Note any sudden growth since the last known-good state
2. Inode availability check
- Confirm inode usage is within safe limits
- Identify filesystems with high inode consumption even if disk space appears sufficient
- Flag abnormal inode usage for follow-up investigation
3. Memory utilization check
- Review total memory, used memory, and available memory
- Confirm swap usage is not increasing unexpectedly
- Ensure memory pressure is not sustained under idle or light load
4. Load average review
- Check short-, mid-, and longer-term load averages
- Compare load values to CPU core count
- Confirm load trends align with expected activity
5. Process-level sanity check
- Identify top resource-consuming processes
- Confirm no runaway or orphaned processes are present
- Verify expected services account for predictable resource usage
6. Quick correlation check
- Correlate disk, memory, and load observations
- Watch for combined signals (e.g., high load with low memory)
- Avoid making changes during this step; observe and record only
7. Record observations
- Document the date and reason this check was performed
- Record any values that differ from normal baselines
- Note whether follow-up investigation is required
Completion criteria
- Disk space and inode usage are within safe operating limits
- Memory and swap usage are stable and expected
- System load aligns with known activity
Next step — based on your current state:
- If abnormal values were observed, proceed to Log Review Routine.
- If this check followed updates, consider After Server Update Verification Checklist.
- If the system is healthy, return to normal operations or continue scheduled maintenance.