Table of contents
- Issue 1: Unable to connect to a website or an application
- Issue 2: Unable to get IP Address
- Issue 3: Server is not reachable or unable to connect
- Issue 4: Unable to ssh as root or any other user
- Issue 5: Disk Space is full issue or add/extend disk space
- Issue 6: SSL/TLS Certificate Expiry
- Issue 7: Database Connection Issue
- Issue 8: Web Application 404 Error
- Issue 9: Slow Application Response Time
- Issue 10: High CPU Usage
Issue 1: Unable to connect to a website or an application
๐ ๏ธ Approach / Solution:
โโโ Ping the server by Hostname and IP Address
โ โโโ False: Above Troubleshooting Diagram "Server is not reachable or cannot connect"
โ โโโ True: Check the service availability by using telnet command with port
โ โ โโโ True: Service is running
โ โ โโโ False: Service is not reachable or running
โ โ โ โโโ ๐ Check the service status using systemctl or other command
โ โ โ โโโ ๐ Check the firewall/selinux
โ โ โ โโโ ๐ Check the service logs
โ โ โ โโโ ๐ Check the service configuration
โโโ ...
Issue 2: Unable to get IP Address
๐ ๏ธ Approach / Solution:
โโโ IP Assignment Methods
โ โโโ DHCP
โ โ โโโ Fixed Allocation
โ โ โโโ Dynamic Allocation
โ โโโ Static
โโโ Troubleshooting
โ โโโ check network setting from virtualization environment like VMware, VirtualBox, or etc
โ โโโ check the IP address is assigned or not
โ โโโ check the NIC status from the host side using #lspci, #nmcli, etc
โ โโโ restart network service
โโโ ...
Issue 3: Server is not reachable or unable to connect
๐ ๏ธ Approach / Solution:
โโโ Ping the server by Hostname and IP Address
โ โโโ Hostname/IP Address is pingable
โ โ โโโ Issue might be on the client side as server is reachable
โ โโโ Hostname is not pingable but IP Address is pingable
โ โ โโโ Could be the DNS issue
โ โ โ โโโ ๐ check /etc/hosts
โ โ โ โโโ ๐ check /etc/resolv.conf
โ โ โ โโโ ๐ check /etc/nsswitch.conf
โ โ โ โโโ (Optional) DNS can also be defined in the /etc/sysconfig/network-scripts/ifcfg-<interface>
โ โโโ Hostname/IP Address both are not pingable
โ โ โโโ Check the other server on its same network to see if there is a Network side access issue or overall something bad
โ โ โ โโโ False: Issue is not overall network side but it's with that host/server
โ โ โ โโโ True: Might be an overall network side issue
โ โ โโโ Logged into the server by Virtual Console, if the server is Powered ON. Check the uptime
โ โ โโโ Check if the server has the IP and has UP status of Network interface
โ โ โ โโโ (Optional) Also check IP-related information from /etc/sysconfig/network-scripts/ifcfg-<interface>
โ โ โโโ Ping the gateway, also check routes
โ โ โโโ Check Selinux, Firewall rules
โ โ โโโ Check physical cable connection
Issue 4: Unable to ssh as root or any other user
๐ ๏ธ Approach / Solution:
โโโ Ping the server by Hostname and IP Address
โ โโโ False: Above Troubleshooting Diagram "Server is not reachable or cannot connect"
โ โโโ True: Check the service availability by using telnet command with port
โ โ โโโ True: Service is running
โ โ โ โโโ Issue might be on the client side
โ โ โ โโโ User might be disabled, nologin shell, disabled root login, and other configurations
โ โ โโโ False: Service is not reachable or running
โ โ โ โโโ ๐ Check the service status using systemctl or other command
โ โ โ โโโ ๐ Check the firewall/selinux
โ โ โ โโโ ๐ Check the service logs
โ โ โ โโโ ๐ Check the service configuration
โโโ ...
Issue 5: Disk Space is full issue or add/extend disk space
๐ ๏ธ Approach / Solution:
โโโ System Performance degradation detection
โ โโโ Application getting slow/unresponsive
โ โโโ Commands are not running (For Example: / disk space is full)
โ โโโ Cannot do logging and other etc
โโโ Analyse the issue
โ โโโ df command to find the problematic filesystem space issue
โโโ Action
โ โโโ After finding the specific filesystem, use du command in that filesystem to get which files/directories are large
โ โโโ Compress/remove big files
โ โโโ Move the items to another partition/server
โ โโโ Check the health status of the disks using badblocks command (For Example: #badblocks -v /dev/sda)
โ โโโ Check which process is IO Bound (using iostat)
โ โโโ Create a link to file/dir
โโโ New disk addition
โ โโโ Simple partition
โ โ โโโ Add disk to VM
โ โ โโโ Check the new disk with df/lsblk command
โ โ โโโ fdisk to create partition. Better to have LVM partition
โ โ โโโ Create filesystem and mount it
โ โ โโโ fstab entry for persistence
โ โโโ LVM Partition
โ โ โโโ Add disk to VM
โ โ โโโ Check the new disk with df/lsblk command
โ โ โโโ fdisk to create LVM partition
โ โ โโโ PV, VG, LV
โ โ โโโ Create filesystem and mount it
โ โ โโโ fstab entry for persistence
โ โโโ Extend LVM partition
โ โ โโโ Add disk, and create LVM partition
โ โ โโโ Add LVM partition (PV) in the existing VG
โ โ โโโ Extend LV and resize filesystem
โโโ ...
Issue 6: SSL/TLS Certificate Expiry
๐ ๏ธ Approach / Solution:
โโโ Check SSL/TLS certificate expiration date
โโโ Confirm the correct certificate is being used
โโโ Renew the SSL/TLS certificate before expiry
โโโ Verify that the server's system time is accurate
โโโ Restart the web server after certificate renewal
โโโ Ensure the renewed certificate is properly configured
โโโ Check for any errors in the web server logs
โโโ Consider automating certificate renewal tasks
โโโ Monitor SSL/TLS certificate expiry using alerts
โโโ ...
Issue 7: Database Connection Issue
๐ ๏ธ Approach / Solution:
โโโ Check if the database service is running
โโโ Verify database connection parameters (username, password)
โโโ Test database connectivity using command-line tools
โโโ Inspect database logs for connection errors
โโโ Review firewall rules for database port access
โโโ Confirm network accessibility between application and database servers
โโโ Check for any recent changes in the database configuration
โโโ Monitor database resource usage and performance
โโโ Investigate potential database server load issues
โโโ ...
Issue 8: Web Application 404 Error
๐ ๏ธ Approach / Solution:
โโโ Verify that the requested URL is correct
โโโ Check web server logs for 404 error details
โโโ Confirm that the file or resource exists on the server
โโโ Review web server configuration for correct document root
โโโ Inspect file and directory permissions
โโโ Clear web browser cache and retry
โโโ Consider URL rewriting rules if applicable
โโโ Test with different browsers or devices
โโโ Investigate if there are any recent website changes
โโโ ...
Issue 9: Slow Application Response Time
๐ ๏ธ Approach / Solution:
โโโ Identify bottlenecks using 'top' or 'htop'
โโโ Monitor application-specific logs for errors or warnings
โโโ Check for database connection and query performance
โโโ Review application code for inefficient algorithms
โโโ Optimize database queries and indexing
โโโ Investigate potential issues with external API calls
โโโ Monitor network latency between application components
โโโ Consider implementing caching mechanisms
โโโ Optimize server and network configurations
โโโ ...
Issue 10: High CPU Usage
๐ ๏ธ Approach / Solution:
โโโ Identify the process causing high CPU usage using top or htop
โโโ Check if the issue is intermittent or continuous
โโโ Review logs for any error messages or known issues
โโโ Inspect running processes and their resource consumption
โโโ Investigate potential malware or unauthorized processes
โโโ Consider optimizing or scaling the application
โโโ Monitor system metrics over time to identify patterns
โโโ Apply performance tuning based on the specific application
โโโ ...
ย