Linux Basic Operational Commands
These are the commands engineers commonly use when diagnosing issues on servers.
AI Workforce — Data Center Operations
Linux Basic Operational Commands
These are the commands engineers commonly use when diagnosing issues on servers.
top
Definition
top is a real-time system monitoring tool that shows CPU usage, memory usage, and running processes.
What it displays
- CPU utilization
- memory usage
- running processes
- system load averages
Why it matters in a data center
It quickly reveals which processes are consuming resources and whether a server is overloaded.
What engineers look for
- a process using extremely high CPU
- system load much higher than the number of CPU cores
- runaway processes
- abnormal memory consumption
Example situation
A server becomes slow → run top → discover a misconfigured service consuming 95% CPU.
df
Definition
df stands for disk free. It shows how much disk storage is used and how much is available.
What it displays
- total disk capacity
- used disk space
- available disk space
- mount points
Why it matters
Servers often fail when disks fill up.
Examples:
- logs fill a disk
- database runs out of space
- system cannot write temporary files
What engineers look for
- partitions close to 100% full
- unexpected disk growth
- abnormal log usage
Example
A web server stops responding → df shows the root partition is full.
iostat
Definition
iostat (Input/Output Statistics) shows disk activity and performance metrics.
What it measures
- disk read/write speeds
- disk utilization
- IO wait times
- queue depth
Why it matters
Disk bottlenecks can slow entire systems.
High disk activity can indicate:
- overloaded storage
- failing disks
- database performance problems
What engineers look for
- very high disk utilization
- long IO wait times
- excessive reads or writes
Example
Application is slow → iostat shows disks at 100% utilization.
netstat
Definition
netstat shows network connections, ports, and routing information.
What it displays
- open network connections
- listening ports
- routing tables
- interface statistics
Why it matters
It helps determine whether a server is:
- receiving traffic
- sending traffic
- listening on the correct ports
What engineers look for
- unexpected connections
- ports not listening
- large numbers of connections
- connection errors
Example
A web service should run on port 443 → netstat shows nothing listening → service crashed.
journalctl
Definition
journalctl reads system logs from systemd, the logging system used in modern Linux.
What it shows
- system boot logs
- service logs
- error messages
- hardware events
Why it matters
Logs are the primary source of troubleshooting information.
They reveal:
- why services failed
- hardware errors
- authentication failures
What engineers look for
- service crash messages
- disk errors
- kernel warnings
- network errors
Example
A service fails to start → journalctl shows configuration error.
System Resource Concepts
These are the four core system metrics engineers constantly evaluate.
CPU Usage
Definition
CPU usage measures how much processing power the system is currently using.
CPU handles tasks like:
- running applications
- executing system processes
- handling network requests
Typical indicators
- percentage of CPU usage
- system load average
Why it matters
High CPU usage can mean:
- heavy workloads
- inefficient code
- runaway processes
- malicious activity
Healthy state
CPU usage fluctuates but should not stay near 100% continuously.
Disk I/O
Definition
Disk I/O (Input/Output) measures how quickly data can be read from or written to storage devices.
This includes:
- SSD access
- database reads/writes
- log file creation
Why it matters
Even if CPU is fast, slow storage can bottleneck the entire system.
Symptoms of disk IO problems:
- slow applications
- delayed responses
- database timeouts
Common causes
- heavy database activity
- large backups
- failing disks
- storage saturation
Memory Usage
Definition
Memory usage refers to how much RAM (Random Access Memory) the system is using.
RAM stores:
- active programs
- cached files
- temporary data
Why it matters
If memory runs out, the system may:
- slow dramatically
- start using swap (disk-based memory)
- crash services
Symptoms
- slow performance
- processes killed by the OS
- high swap usage
Network Connections
Definition
Network connections represent active communication sessions between systems.
Examples:
- web client connecting to a server
- database queries
- API calls
Why it matters
Network problems are common causes of outages.
Issues can include:
- dropped packets
- connection overload
- incorrect routing
- firewall blocks
Symptoms
- applications cannot connect
- high latency
- connection timeouts
The Four Core Metrics Engineers Always Check
When diagnosing server issues, engineers almost always check these four areas first:
- CPU
- Memory
- Disk IO
- Network
These metrics reveal most system problems.
Mental Model Used by Data Center Engineers
When something breaks, engineers ask:
- Is CPU overloaded?
- Is memory exhausted?
- Is storage slow?
- Is the network failing?
Most infrastructure issues fall into one of those categories.
How This Applies to the Data Center Operations Manager Role
You are not expected to debug every server personally, but you must understand these metrics so you can:
- guide troubleshooting conversations
- understand technician reports
- prioritize incident response
- make informed decisions during outages
This is what “Dive Deep” is, being able to understand technical signals without necessarily writing code.
메타데이터
- post_id
- 4604e98adf1f
- slug
- linux-basic-operational-commands-4604e98adf1f
- url
- https://medium.com/the-ai-workforce/linux-basic-operational-commands-4604e98adf1f
- canonical_url
- https://medium.com/the-ai-workforce/linux-basic-operational-commands-4604e98adf1f
- author_url
- https://medium.com/@afiero
- status
- ok
- fetched_at
- 2026-06-10 15:53:41
