Service Down

Scope: Systemd
1
Is the execution status running?
systemctl status nginx
2
Inspect stack trace errors or termination logs
journalctl -u nginx -n 50
3
Verify network port binds and descriptor parameters
ss -tulnp | grep nginx
4
Test internal response handling via loopback
curl http://localhost:80
5
Identify local packet dropping regulations
ufw status
iptables -L -n
6
Validate configuration files sanity
nginx -t
7
Verify partition storage write availability
df -h
8
Assess kernel termination records (OOM Killer)
dmesg | grep -i "oom"
free -h
1
Check layer-3 routing availability
ping <host>
2
Audit endpoint socket listening posture
nc -zv <host> <port>
3
Execute hop-by-hop tracking trace
traceroute <host>
Where execution halts indicates where the block resides
4
Confirm daemon binding behavior on downstream node
ss -tulnp
5
Verify remote edge filtering stack rules
iptables -L
6
Inspect node forward routing table
ip route
1
Evaluate task processor scheduling loads
top
Type 'P' inside utility interface to group execution sort tasks by compute consumption
2
Identify page space layout degradation
free -h
top
Type 'M' to group execution sort tasks by volatile storage footprint
3
Isolate blocks and channel storage performance limits
iostat -x 1
iotop
4
Analyze data payload velocity constraints
iftop
nethogs
5
Correlate context load metrics with available scheduler cores
uptime
nproc
If immediate metrics exceed total cores available, tasks are bottlenecked
6
Evaluate socket pool tracking limits
ss -s
1
Test fundamental point-to-point path behavior
ping <host>
2
Verify port standard port status
nc -zv <host> 22
3
Verify execution process lifecycle metrics on endpoint host
systemctl status sshd
4
Initialize client trace mode to track handshaking
ssh -v user@host
5
Evaluate target log vectors for denial warnings
cat /var/log/auth.log | grep Failed
6
Correct local validation credential profiles
chmod 600 ~/.ssh/id_rsa
chmod 700 ~/.ssh/
7
Analyze configuration permission variables
cat /etc/ssh/sshd_config | grep -i "permitroot\|passwordauth"
1
Isolate layer-3 address routes from naming resolution issues
ping 8.8.8.8
ping google.com
If numerical tracking connects but name tracking drops, resolution stack is damaged
2
Inspect configurations matching nameserver endpoints
cat /etc/resolv.conf
3
Test records using localized options vs fallback sources
dig google.com
dig @8.8.8.8 google.com
If direct public lookup succeeds, your configured system-level local upstream targets are invalid
4
Apply an immediate operational hotfix resolution path
echo "nameserver 8.8.8.8" >> /etc/resolv.conf
5
Verify localized modern interface manager state
resolvectl status
1
Synchronize remote catalog indexes
apt update
2
Enforce correction on broken library nodes
apt install -f
3
Clear locked process tracking anomalies
rm /var/lib/dpkg/lock-frontend
dpkg --configure -a
4
Ensure repository directory path capacity is sufficient
df -h /var
apt clean
5
Verify remote configuration link strings
cat /etc/apt/sources.list
1
Verify system unit lifecycle condition
systemctl status <service>
2
Isolate recent runtime outputs and diagnostic events
journalctl -u <service> -n 50
3
Verify network listener interface bindings
ss -tulnp
4
Verify responses inside localized context boundaries
curl localhost:<port>
5
Check layer-4 firewall configurations
ufw status
6
Verify root file allocation limit boundaries
df -h
7
Evaluate system-wide memory exhaustion parameters
free -h
8
Monitor raw operational events and diagnostic outputs
tail -f /var/log/syslog
1
Verify system engine execution parameters
systemctl status mysql
systemctl status postgresql
2
Audit database error logs for corruption indicators
journalctl -u mysql -n 50
tail -f /var/log/mysql/error.log
3
Verify proper port listener states
ss -tulnp | grep 3306
4
Validate native authentication handshake functions
mysql -u root -p
psql -U postgres
Immediate termination confirms authentication mismatches or socket failure
5
Inspect current process pipelines and transactions
mysql -e "SHOW PROCESSLIST;"
psql -c "SELECT * FROM pg_stat_activity;"
Check query states for resource blocks and row locks
6
Identify if client configuration bounds are saturated
mysql -e "SHOW STATUS LIKE 'Threads_connected';"
mysql -e "SHOW VARIABLES LIKE 'max_connections';"
7
Verify layout volume file availability constraints
df -h /var/lib/mysql
8
Inspect firewall filters and listener addresses
ufw allow 3306/tcp
Review bind-address properties inside your mysqld.cnf. Elements restricted to loopback (127.0.0.1) drop remote client routes.
1
Verify database service state
systemctl status redis
2
Examine logging tracks for storage snapshot errors
journalctl -u redis -n 50
tail -f /var/log/redis/redis-server.log
3
Verify network stack listening structures
ss -tulnp | grep 6379
4
Check engine reactivity using standard test calls
redis-cli ping
Should return PONG. Any alternative execution indicates a handshake configuration error.
5
Examine volatile storage tracking maps and stats
redis-cli info memory
redis-cli info stats
Monitor current allocation against maximum thresholds. Reaching this causes cache key evictions.
6
Evaluate socket mapping totals
redis-cli info clients
redis-cli client list
7
Trace inbound execution logic strings in real-time
redis-cli monitor
Warning: High computational footprint. Use carefully inside production clusters.
8
Audit interface and credential parameters
cat /etc/redis/redis.conf | grep -E "bind|requirepass|maxmemory"
1
Verify daemon lifecycle posture
systemctl status mongod
2
Trace journal and aggregation warnings
journalctl -u mongod -n 50
tail -f /var/log/mongodb/mongod.log
3
Verify cluster interface binding configuration
ss -tulnp | grep 27017
4
Access programmatic control database shell
mongosh
mongosh --host 127.0.0.1 --port 27017
5
Extract transactional internals inside execution prompt
db.serverStatus()
db.stats()
6
Check block storage write capabilities
df -h /var/lib/mongodb
7
Examine host parsing network bounds
cat /etc/mongod.conf | grep -A3 "net:"
Binding to loopback limits traffic to local callers only. Update config to 0.0.0.0 for broader routes.
1
Verify worker control status
systemctl status nginx
systemctl status apache2
2
Test config updates BEFORE executing worker restarts
nginx -t
apache2ctl -t
Running malformed configurations causes worker execution failures and unexpected downtime.
3
Follow HTTP protocol proxy error fields
tail -f /var/log/nginx/error.log
tail -f /var/log/apache2/error.log
4
Monitor inbound routing status logs
tail -f /var/log/nginx/access.log
5
Verify network listener assignments
ss -tulnp | grep -E '80|443'
1
Verify hypervisor/daemon background task execution
systemctl status docker
2
List unready or crashing container blocks
docker ps -a
3
Extract standard runtime logs from target context
docker logs --tail 50 -f <container_id_or_name>
4
Verify environment allocation load figures
docker stats
5
Open diagnostic console within a target container
docker exec -it <container_id_or_name> /bin/sh
docker exec -it <container_id_or_name> /bin/bash
6
Analyze network configuration topology bridges
docker network ls
docker network inspect <network_name>
7
Purge unused overlay elements and cached image layers
docker system prune -a --volumes
Warning: Destructive execution. Removes stopped container caches and dangling volumes.
1
Trace upstream unit tracking settings
systemctl status <app-name>
2
Follow service logging outputs
journalctl -u <app-name> -f -n 100
3
Verify configuration matching path bindings
ss -tulnp | grep <app-port>
4
Inspect localized app configuration files
cat /etc/<app-name>/config.yaml
cat .env
5
Isolate permission issues or access restrictions
ls -la /var/www/<app-name>
chown -R www-data:www-data /var/www/<app-name>