Source: medium.com
WordPress LAMP service outage incident report — Postmortem practiceCategory: puppet
this article was written for learning purposes) From 6:19 PM to 8:02 PM UTC-0, all requests to WordPress server resulted in 500 error response messages.
The root case of this outage was an invalid extension in a configuration file.
Root Cause, At 6:12 PM UTC-0, a configuration change was released to production environment without first being released to the testing enviroment.
After the misconfigured file was identified at 7:20 PM UTC-0, a puppet manifest script was written (see image 5) at 7:30 PM and applied to the server to fix the error and bring the service back up at 8:02 PM UTC-0.
The root case of this outage was an invalid extension in a configuration file.
Root Cause, At 6:12 PM UTC-0, a configuration change was released to production environment without first being released to the testing enviroment.
After the misconfigured file was identified at 7:20 PM UTC-0, a puppet manifest script was written (see image 5) at 7:30 PM and applied to the server to fix the error and bring the service back up at 8:02 PM UTC-0.
Related Articles
Community Partners
DevOps Careers