linux troubleshooting guide
Beginner Linux Certification Command Practice
Build command confidence with realistic tasks: inspect first, predict output, run read-only checks, then compare results before changing systems.
Problem
Beginner command practice often becomes memorization. Real Linux work requires reading output, choosing safe inspection commands, and understanding when not to run a command.
First rule
Practice with read-only commands first, and treat every command as a question you are asking the system.
Audience
beginners studying Linux fundamentals, LPIC-1, LFCS, Linux+, or job-focused command-line troubleshooting
Cert context
This guide is cert-adjacent but unofficial. It maps common command habits to study practice without using exam dumps, real exam questions, or provider-owned material.
quick start
Safe first commands
df -hdu -xhd1 /var 2>/dev/null | sort -htail -n 80 /var/log/nginx/error.lognamei -l /var/www/example/index.htmlsudo ss -tulpnrsync -avhn --delete ./source/ ./backup/
Practice storage triage
Learn to prove what is full before deleting anything. Storage tasks combine `df`, `du`, `find`, sorting, and careful interpretation.
df -hdf -idu -xhd1 /var 2>/dev/null | sort -h
Practice log reading
Logs teach pipes, grep patterns, time windows, and service context. Start with recent output, then search and inspect surrounding lines.
journalctl -u nginx --since '30 minutes ago' --no-pagergrep -inE 'error|failed|denied|timeout' /var/log/nginx/error.log
Practice permissions carefully
Permissions practice should be precise. Inspect owner, group, mode, and parent directories before changing anything.
namei -l /var/www/example/index.htmlstat -c '%A %U:%G %n' /var/www/example/index.html
Practice services and networking
Service checks become more useful when connected to ports and logs. A service can be active but not listening, or listening locally while remote users still fail.
systemctl --failed --no-pagersudo ss -tulpncurl -I https://example.com/
Practice dangerous commands with dry runs
Backup and synchronization commands are valuable, but they can destroy data when pointed the wrong way. Learn dry-run habits early.
rsync -avhn --delete ./source/ ./backup/rsync -ani --delete ./source/ ./backup/
triage logic
How to read the result
a command returns no output
No output can mean success, no matches, wrong file, wrong service name, or insufficient permission.
Next: Check the command's target and try a narrower known-good input.
a command needs sudo
You may be crossing from inspection into privileged administration.
Next: Understand the command and expected output before rerunning with privileges.
a practice task includes a destructive flag
The safe skill is previewing and explaining the impact before execution.
Next: Use dry-run mode and inspect output before removing the guard.
safety notes
Slow down here
- Use disposable labs, test directories, or read-only commands while learning.
- Certification study should build habits, not memorized incantations.
- This site is independent and unofficial; verify exam objectives with the certification provider.
Independent study support
These guides are cert-adjacent practice material, not official training, endorsement, exam dumps, or real exam questions.
related lessons
Command cards
- Check Filesystem Space with df
- Check Inodes When Disk Space Looks Fine
- Read Current-Boot Logs for One Service
- Find Listening Ports with ss
- Find Which Folder Is Filling the Disk
- Find the Files Eating Your Disk
- Watch Logs Without Opening the Whole File
- Find Errors Before Reading Every Log Line
- Inspect Permissions Before Changing Them
- Check What Is Actually Listening
- Run Rsync Without Deleting Your Backup