Web stack incident report

Issue Summary :

Well , as we don’t know when the outage actually started , we can assume that it happened just as our web debugging project started ,from the 08–04–2020 at 00 AM CT to 4 PM CT . The issue was that curling port 80 does not return a page but an error message “curl: (52) Empty reply from server” and everyone was affected by it and the main cause was that the apache2 web server was not working .

Timeline :

• The issue was detected by midnight .
• It was detected while trying to curl port 80
• The web server was inverstigated
• Checking the port errors
• Asked the help of peers
• Starting apache2 service

Root cause and resolution :

Apache is a cross platform HTTP web server that is commonly used to deploy and run web applications or websites. In our case , apache service was down so we can’t request any web page hence the curl error .

So to resolve this issue , we checked the status of the web server with the systmctl command

Then as it turns out apache2 service was stopped , we started it . and after that we managed to curl on port 80 with the expected message .

Corrective and preventative measures :

• I think that checking on the status of web servers constantly can prevent incident like these .
• I don’t think further actions must be done to adress the issue