Day-21:Apache Troubleshooting | KodeKloud Engineer:Linux Level-2 скачать в хорошем качестве

Day-21:Apache Troubleshooting | KodeKloud Engineer:Linux Level-2

In this video, I walk you through a real-world Linux sysadmin task: troubleshooting and fixing Apache (httpd) across multiple application servers in a datacenter environment. From hunting down syntax errors in the config files to fixing incorrect ports and paths, I'll show you the exact process I use to get services back online fast. We’ll be diving into the terminal to use powerful tools like systemctl for service management, journalctl for debugging logs, and vi for configuration edits. What You’ll Learn: How to identify why a service is failing to start. Troubleshooting configuration errors in httpd.conf. Correcting DocumentRoot and Listen port settings. Verifying service connectivity using curl. The Troubleshooting Workflow: 1. App Server 1 (Tony): * Issue: Syntax error in config file. Fix: Analyzed logs with journalctl -xeu httpd.service and corrected the error in /etc/httpd/conf/httpd.conf. 2. App Server 2 (Steve): Issue: Multiple configuration errors. Fix: Updated the listener to port 6200 and corrected the DocumentRoot path to /var/www/html. 3. App Server 3 (Banner): Issue: Service was stopped but config was fine. Fix: simply enabled and started the service with systemctl enable --now httpd. Commands Used in This Video: SSH into server: ssh user@server Switch to root: sudo -i Check status: systemctl status httpd Start/Enable service: systemctl enable --now httpd View error logs: journalctl -xeu httpd.service Verify service: curl http://[IP_ADDRESS]:6200 If you found this helpful, hit that LIKE button and SUBSCRIBE for more hands-on DevOps and Linux tutorials! 🔔 #Linux #DevOps #Apache #SysAdmin #Troubleshooting #TechTutorial #Nautilus