{
  "is": "issue",
  "title": "Apache was not responding on Opal4",
  "body": "\u003cp\u003e\u003cem\u003eFixed\u003c/em\u003e - The root cause appears to have been a misconfigured customer application. We\u0026rsquo;ve corrected the configuration and have updated our monitoring system to alert us when Apache approaches its configured limits. \n  \u003cspan class=\"faded\"\u003e(17:22 UTC — Apr 28)\u003c/span\u003e\n\n\u003c/p\u003e\n\u003cp\u003eThe Apache service on Opal4 was not responding for approximately 1 hour today beginning 18:23 UTC.\u003c/p\u003e\n\u003cp\u003eThe problem was that the Apache service had hit its configured \u003ccode\u003eServerLimit\u003c/code\u003e which meant that no further Apache processes could spawn to handle requests. That has been corrected and the service is online now.\u003c/p\u003e\n\u003cp\u003eWe\u0026rsquo;re now investigating the root cause and also looking into why our own monitoring systems did not alert us to this condition. \n  \u003cspan class=\"faded\"\u003e(18:23 UTC — Apr 24)\u003c/span\u003e\n\n\u003c/p\u003e\n",
  "createdAt": "2020-04-24 18:23:00 +0000 UTC",
  "lastMod": "2020-04-24 18:23:00 +0000 UTC",
  "permalink": "https://opalstackstatus.com/issues/2020-04-24-apache-was-not-responding-on-opal4/",
  "severity": "down",
  "resolved": true,
  "informational": false,
  "resolvedAt": "2020-04-28 17:22:38",
  "affected": ["Shared: Dallas (USA)"],
  "filename": "2020-04-24-apache-was-not-responding-on-opal4.md"
}