Apache was not responding on Opal4

Fixed - The root cause appears to have been a misconfigured customer application. We’ve corrected the configuration and have updated our monitoring system to alert us when Apache approaches its configured limits. (17:22 UTC — Apr 28)

The Apache service on Opal4 was not responding for approximately 1 hour today beginning 18:23 UTC.

The problem was that the Apache service had hit its configured ServerLimit which meant that no further Apache processes could spawn to handle requests. That has been corrected and the service is online now.

We’re now investigating the root cause and also looking into why our own monitoring systems did not alert us to this condition. (18:23 UTC — Apr 24)