Thanks to visit codestin.com
Credit goes to www.scribd.com

Scribd
Upload
25 views2 pages

Linux Troubleshooting Guide

The document outlines various troubleshooting scenarios related to SSH connections, IP routing, file permissions, disk space issues, service failures, kernel panics, crontab problems, network configuration, disk failures in RAID arrays, and user account lockouts. Each scenario includes a question and a concise answer detailing possible causes and solutions. It serves as a quick reference guide for system administrators facing common technical issues.

Uploaded by

sondos.alsafy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
25 views2 pages

Linux Troubleshooting Guide

The document outlines various troubleshooting scenarios related to SSH connections, IP routing, file permissions, disk space issues, service failures, kernel panics, crontab problems, network configuration, disk failures in RAID arrays, and user account lockouts. Each scenario includes a question and a concise answer detailing possible causes and solutions. It serves as a quick reference guide for system administrators facing common technical issues.

Uploaded by

sondos.alsafy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

1.

Scenario: SSH Connection Issue

o Question: A user is unable to SSH to a remote server. What could be the possible cause?

o Answer: Several possibilities:

 Host is not allowed to SSH to the server.

 Direct root login may not be allowed.

 AllowUsers or AllowGroup restrictions in the SSH configuration.

2. Scenario: IP Routing Issue

o Question: You can SSH from one Linux box (IP: 192.168.10.12) to another (IP:
192.168.10.11), but not from a Windows box (IP: 192.169.10.29). What’s the problem?

o Answer: Likely an IP routing issue. Check the gateway settings on 192.168.10.12 and
ensure proper connectivity.

3. Scenario: File Permissions

o Question: User root created a file named “secret” with permissions -rwx------. Only root
and another user named “deepak” should access it. How can this be achieved?

o Answer: Set the correct permissions:

o chmod 700 secret

o chown root:deepak secret

4. Scenario: Disk Space Full

o Question: The root partition is full. How would you identify large files and free up space?

o Answer: Use commands like du, df, and find to identify large files and delete
unnecessary ones.

5. Scenario: Service Not Starting

o Question: A critical service (e.g., Apache) is not starting. How would you troubleshoot?

o Answer: Check service logs (/var/log) for errors. Verify configuration files and
dependencies.

6. Scenario: Kernel Panic

o Question: The server experienced a kernel panic. What steps would you take to
diagnose and resolve it?

o Answer: Analyze kernel logs (dmesg), check hardware, and apply relevant patches.

7. Scenario: Crontab Issue

o Question: A scheduled cron job is not running. How would you troubleshoot?
o Answer: Verify the cron syntax, check user permissions, and review system logs.

8. Scenario: Network Configuration

o Question: A server lost network connectivity. How would you troubleshoot?

o Answer: Check network interfaces (ifconfig), routing (ip route), and DNS settings.

9. Scenario: Disk Failure

o Question: A disk failed in a RAID array. How would you replace it without data loss?

o Answer: Identify the failed disk, replace it, and rebuild the RAID using tools like mdadm.

10. Scenario: User Account Lockout

o Question: A user account is locked out due to too many failed login attempts. How
would you unlock it?

o Answer: Use pam_tally2 or faillock to reset the failed login count.

You might also like