adminLinux Process and Service Model Checklist
Linux system administration becomes much easier when you understand processes and services. A website, database, Docker container or automation worker is not magic. It is a running process controlled by the operating system.
Core principle
A process is a running program. A service is a managed process that can start, stop, restart and run in the background. When something breaks, you need to know whether the process exists, whether the service manager sees it and whether logs explain the failure.
Checklist
- Identify which service should be running.
- Check service status with systemctl.
- Check whether the process exists.
- Check which user owns the process.
- Check CPU and memory usage of the process.
- Read recent service logs.
- Restart only the affected service if needed.
- Confirm the service starts after reboot if required.
- Document service name and purpose.
- Connect the service to the website or application it supports.
Reusable lesson
This applies to Nginx, PHP-FPM, MySQL, Docker, n8n, API workers, queue workers and monitoring agents.
When to Use This Checklist
Use this checklist when learning how Linux runs websites, databases, Docker services, automation workers and background processes.
Required Tools
SSH access, Ubuntu VPS, systemctl, ps, top, journalctl, service name
Before You Start
Do not restart random services. First identify which service supports the broken website, workflow or application.
Structured Checklist Steps
- Identify target service.
- Check systemctl status.
- Check running process.
- Check process owner.
- Check CPU and memory.
- Read journal logs.
- Restart only if needed.
- Check enable status.
- Document service purpose.
- Map service to application.
Verification Steps
- Service status is known.
- Process exists or failure is confirmed.
- Logs explain recent failure.
- Resource usage is understood.
- Service can restart cleanly.
Rollback Plan
If a restart makes the situation worse, stop changing services and inspect logs or restore the previous config before restarting again.
Common Mistakes
- Restarting all services blindly.
- Not knowing the real service name.
- Ignoring journal logs.
- Confusing a stopped process with a broken application config.
- Not checking whether the service is enabled on boot.
Related Commands
sudo systemctl status nginx
sudo systemctl status php8.2-fpm
ps aux | head
top
journalctl -u nginx --since "30 minutes ago"
sudo systemctl restart nginx
sudo systemctl enable nginx