Common Linux Errors and Their Solutions

In Linux system administration, encountering various errors is a norm. These errors may arise from permission issues, configuration errors, resource shortages, or hardware failures. Timely diagnosis and resolution of these errors can help administrators maintain system stability and performance.

1. Introduction

As an open-source operating system, Linux is widely used in servers, cloud environments, and embedded systems. However, in daily use, users often encounter various errors, such as “Permission denied,” “No space left on device,” or “Kernel panic.” If these errors are not addressed promptly, they may lead to system crashes or data loss.

2. File and Permission Related Errors

File operations are the most common scenarios in Linux, and permission-related errors occur frequently. Below are common types.

2.1 Permission Denied

Description: The error “Permission denied” occurs when trying to access a file or directory, such as failing to run a command or read a file.

Common Causes:

• Insufficient user permissions (not root or file owner).
• Incorrect file or directory permission settings (e.g., 600 instead of 644).
• SELinux or AppArmor enforced access control denial.
• File system mount options (e.g., noexec) restrict execution.

Solutions:

1. Check permissions:

   ls -l /path/to/file
   

2. Modify permissions:

   sudo chmod 644 /path/to/file
   sudo chown user:group /path/to/file
   

3. Check SELinux:

   sudo getenforce
   sudo ausearch -m avc -ts recent
   sudo setsebool -P httpd_can_network_connect on
   

4. Use sudo or switch users:

   sudo command
   su - user
   

Preventive Measures:

• Follow the principle of least privilege.

• Regularly audit permissions:

  find / -perm -4000 -o -perm -2000 2>/dev/null
  

• Enable SELinux and configure policies correctly.

Case: Nginx cannot read the configuration file.

• Cause: Permission is set to 600, not accessible by the nginx user.
• Solution: sudo chown nginx:nginx /etc/nginx/nginx.conf.

2.2 No Such File or Directory

Description: Commands like ls or cd report “No such file or directory.”

Common Causes:

• Incorrect file path or spelling error.
• File has been deleted or moved.
• Symbolic link is broken.
• Mount point is not mounted.

Solutions:

1. Check the path:

   ls /path/to/file
   

2. Find the file:

   find / -name "file" 2>/dev/null
   

3. Check symbolic links:

   readlink -f /path/to/symlink
   

4. Mount the device:

   sudo mount /dev/sda1 /mnt
   

Preventive Measures:

• Use absolute paths or environment variables (e.g., $PATH).
• Regularly back up files.
• Use rsync to synchronize files.

Case: Script execution fails due to missing dependency files.

• Solution: sudo apt install missing_package.

2.3 Too Many Open Files

Description: The number of files opened by a process exceeds the limit, resulting in “Too many open files.”

Common Causes:

• High concurrency applications (e.g., web servers) opening too many connections.
• System file descriptor limit is too low.
• Memory leaks causing file handles not to be released.

Solutions:

1. Check the limit:

   ulimit -n
   

2. Temporarily increase the limit:

   ulimit -n 65535
   

3. Permanent configuration:

   sudo nano /etc/security/limits.conf
   

   Add:

   * soft nofile 65535
   * hard nofile 65535
   root soft nofile 65535
   root hard nofile 65535
   

4. Check the files opened by the process:

   lsof -p <pid> | wc -l
   

Preventive Measures:

• Optimize application code to close file handles promptly.
• Use connection pools to reduce the number of open connections.
• Monitor file descriptor usage.

Case: Nginx reports “Too many open files.”

• Solution: Adjust /etc/security/limits.conf and restart the service.

3. Network Related Errors

Network errors are common in connection failures or configuration issues.

3.1 Connection Refused

Description: The error “Connection refused” occurs when trying to connect to a remote server.

Common Causes:

• Service not started or not listening on the port.
• Firewall blocking the connection.
• Port not open.
• Network issues (e.g., routing errors).

Solutions:

1. Check service status:

   sudo systemctl status nginx
   

2. Check port listening:

   ss -tuln | grep :80
   

3. Check firewall:

   sudo firewall-cmd --list-all
   sudo firewall-cmd --permanent --add-port=80/tcp
   sudo firewall-cmd --reload
   

4. Test the port:

   telnet server_ip 80
   

Preventive Measures:

• Use ufw or firewalld to manage the firewall.
• Regularly check service ports.

Case: SSH connection refused.

• Solution: sudo systemctl start sshd.

3.2 No Route to Host

Description: The error “No route to host” occurs when pinging or connecting.

Common Causes:

• Incorrect routing table.
• Firewall blocking ICMP.
• Network interface not configured.

Solutions:

1. Check routing:

ip route show

1. Add route:

sudo ip route add default via 192.168.1.1

1. Check firewall:

sudo iptables -L

Preventive Measures:

• Configure static routes or use DHCP.
• Test network connectivity.

Case: Unable to access external websites.

• Solution: Add a default gateway.

3.3 Connection Timed Out

Description: Connection attempts time out.

Common Causes:

• Target server not responding.
• Firewall blocking.
• High network latency.

Solutions:

1. Check target port:

nc -zv server_ip 80

1. Check network latency:

ping server_ip

1. Adjust timeout:

sudo nano /etc/ssh/sshd_config

Add:

ClientAliveInterval 60
ClientAliveCountMax 3
sudo systemctl restart sshd

Preventive Measures:

• Optimize network configuration.
• Use load balancing.

Case: Remote SSH times out.

• Solution: Configure keepalive.

4. Disk Space and Storage Related Errors

Storage errors are common due to insufficient space or permission issues.

4.1 No Space Left on Device

Description: The error “No space left on device” occurs when writing files.

Common Causes:

• Disk is full.
• Inode exhaustion.
• Quota limits.

Solutions:

1. Check space:

df -h
du -sh /*

1. Clean temporary files:

sudo rm -rf /tmp/*
sudo apt clean

1. Check inode:

df -i

1. Delete large files:

sudo find / -size +100M -exec ls -lh {} \;

Preventive Measures:

• Configure quotas:

  sudo setquota -u user 10G 12G 0 0 /home
  

• Monitor space.

Case: /var/log is full.

• Solution: sudo find /var/log -type f -mtime +7 -delete.

4.2 Read-Only File System

Description: Write operations fail because the file system is read-only.

Common Causes:

• Disk errors.
• Mounted as read-only.
• File system corruption.

Solutions:

1. Check mount:

mount | grep ro

1. Remount as read-write:

sudo mount -o remount,rw /data

1. Check errors:

dmesg | grep error
sudo fsck /dev/sda1

Preventive Measures:

• Regularly perform fsck checks.
• Use RAID redundancy.

Case: Root partition is read-only.

• Solution: Restart in rescue mode and run fsck.

4.3 Disk Quota Exceeded

Description: The error “Disk quota exceeded” occurs when a user writes files.

Common Causes: User exceeds quota limits.

Solutions:

1. Check quota:

quota -u user

1. Adjust quota:

sudo setquota -u user 20G 22G 0 0 /home

Preventive Measures: Enable quota monitoring.

Case: User’s /home is at quota limit.

• Solution: Clean files or increase quota.

5. Memory and Process Related Errors

Memory errors are common due to resource exhaustion.

5.1 Out of Memory (OOM) Killed

Description: The process is killed by the OOM killer.

Common Causes:

• Insufficient memory.
• Process memory leaks.

Solutions:

1. Check logs:

dmesg | grep -i oom

1. Increase memory or swap:

sudo fallocate -l 4G /swapfile
sudo mkswap /swapfile
sudo swapon /swapfile

1. Adjust OOM behavior:

sudo nano /etc/sysctl.conf

Add:

vm.overcommit_memory=2
sudo sysctl -p

Preventive Measures:

• Use cgroups to limit process memory.
• Monitor memory usage.

Case: MySQL OOM killed.

• Solution: Increase innodb_buffer_pool_size.

5.2 Too Many Open Files

Description: The process opens too many files.

Common Causes: High concurrent connections.

Solutions:

1. Check limits:

ulimit -n

1. Increase limits:

sudo nano /etc/security/limits.conf

Add:

* soft nofile 65535
* hard nofile 65535

Preventive Measures: Optimize application connection pools.

Case: Nginx error.

• Solution: Increase worker_connections.

5.3 Killed (Signal 9)

Description: The process is killed by SIGKILL.

Common Causes: OOM or manual kill -9.

Solutions:

1. Check logs:

dmesg | grep killed

1. Increase resources or optimize the process.

Preventive Measures: Avoid kill -9, use kill -15 instead.

Case: Script was killed.

• Solution: Check resource usage.

6. Kernel and Boot Related Errors

Kernel errors are serious and may lead to crashes.

6.1 Kernel Panic

Description: Kernel crashes, and the system halts.

Common Causes:

• Hardware failure.
• Driver issues.
• Memory errors.

Solutions:

1. Check logs:

dmesg | grep panic

1. Configure kdump:

sudo nano /etc/kdump.conf

Add:

path /var/crash
core_collector makedumpfile -c --message-level 1 -d 31
sudo systemctl enable kdump
sudo systemctl start kdump

1. Analyze dump:

sudo crash /var/crash/vmcore

Preventive Measures:

• Update the kernel.
• Check hardware.

Case: Kernel panic.

• Solution: Update drivers.

6.2 GRUB Boot Error

Description: Boot failure.

Common Causes: GRUB configuration errors.

Solutions:

1. Enter rescue mode.
2. Repair GRUB:

sudo grub-install /dev/sda
sudo update-grub

Preventive Measures: Backup /boot.

Case: Boot failure.

• Solution: Reinstall GRUB.

7. Package Management and Software Installation Errors

Package management errors are common during software installation.

7.1 Package Not Found

Description: Package not found.

Common Causes: Repository not updated or package name error.

Solutions:

1. Update repository:

sudo apt update

1. Search for the package:

apt search nginx

Preventive Measures: Enable official repositories.

Case: Installation failed.

• Solution: Update repository.

7.2 Dependency Error

Description: Dependency issues.

Common Causes: Version conflicts.

Solutions:

1. Install dependencies:

sudo apt install -f

Preventive Measures: Use apt install to automatically resolve dependencies.

Case: Missing software dependencies.

• Solution: apt install -f.

7.3 Broken Packages

Description: Package is broken.

Solutions:

1. Repair:

sudo apt --fix-broken install

Preventive Measures: Avoid interrupting installations.

Case: Upgrade failed.

• Solution: Repair broken packages.

8. Other Common Errors

8.1 Command Not Found

Description: Command not found.

Cause: Not in PATH.

Solutions:

1. Check PATH:

echo $PATH

1. Add to PATH:

export PATH=$PATH:/usr/local/bin

Prevention: Install to /usr/bin.

8.2 Segmentation Fault

Description: Segmentation fault.

Cause: Memory access violation.

Solutions:

1. Debug:

gdb ./program

1. Check code.

Prevention: Use valgrind to check memory.

8.3 Kernel Module Load Error

Description: Module load failed.

Cause: Incompatible or missing.

Solutions:

1. Check module:

modprobe module_name

Prevention: Update the kernel.

9. Conclusion

Handling Linux errors is a core skill in operations and maintenance. By summarizing common errors and their solutions, one can systematically diagnose and fix issues. Remember, prevention is better than cure; regular system maintenance can reduce the occurrence of errors.