When I am trying to access Drupal and the database is down, it will return a 500 error. However, when I try to access Drupal when Redis is down, it says:

Additional uncaught exception thrown while handling exception.

Predis\Connection\ConnectionException: Connection refused [tcp://drupal-redis-2:6379] in Predis\Connection\AbstractConnection->onConnectionError() (line 146 of /var/www/corp/sites/all/libraries/predis/src/Connection/AbstractConnection.php).

Predis\Connection\ConnectionException: Connection refused [tcp://drupal-redis-2:6379] in Predis\Connection\AbstractConnection->onConnectionError() (line 146 of /var/www/corp/sites/all/libraries/predis/src/Connection/AbstractConnection.php).

The HTTP code returned, however, is 200. This makes it difficult to detect if a server is down for load balancing purposes.

This question is similar to Site is down due to MySQL error but it returns 200/OK but it remains unanswered and is a little different.

  • check this stackoverflow.com/questions/9866541/… Feb 21, 2019 at 22:19
  • Thanks but I don't need to know if redis is running; I need Drupal to return a 5xx error code if it has an exception (such as redis not running). Feb 21, 2019 at 22:38
  • Does the website still work if Redis is down? If so, it isn't a fatal error. I'd say this is by design but you might have more luck talking to the Predis developers.
    – imclean
    Feb 21, 2019 at 23:18
  • The website does not work when redis is down. Feb 22, 2019 at 19:12

1 Answer 1


This is a known issue, whose fix didn't make it into the Drupal 7 core so far. The culprit can be found within the _drupal_exception_handler(). If another error occurs while handling an exception, it just returns the messages stated in your question without setting HTTP status codes (possibly to avoid further exceptions).

Compare https://www.drupal.org/project/drupal/issues/2666908

The above issue already has a small RTBC patch that solves the problem by adding a 500 status code to the handling of the second exception:

function _drupal_exception_handler($exception) {
  require_once DRUPAL_ROOT . '/includes/errors.inc';

  try {
    // Log the message to the watchdog and return an error page to the user.
    _drupal_log_error(_drupal_decode_exception($exception), TRUE);
  catch (Exception $exception2) {
    // Add a 500 status code in case an exception was thrown before the 500
    // status could be set (e.g. while loading a maintenance theme from cache).
    drupal_add_http_header('Status', '500 Internal Server Error');

    // Another uncaught exception was thrown while handling the first one.
    // If we are displaying errors, then do so with no possibility of a further uncaught exception being thrown.
    if (error_displayable()) {
      print '<h1>Additional uncaught exception thrown while handling exception.</h1>';
      print '<h2>Original</h2><p>' . _drupal_render_exception_safe($exception) . '</p>';
      print '<h2>Additional</h2><p>' . _drupal_render_exception_safe($exception2) . '</p><hr />';

Given the age of that patch, the line numbering differs a little from the current version of bootstrap.inc. But it still applies cleanly and works as expected.

After you patched your Drupal, you should be able to receive the 500 error code at your load balancer, if Redis is down or the error page can't be created for another reason.

Please note, if your Drupal already sent headers/output to the browser before the error handler kicks in, above patch may have unintended side-effects. You may have to test yourself, whether your webserver still generates 500 server errors for these edge cases.

  • Consider leaving your feedback in the issue queue. Drupal 7 will be out of support by November 2021, but it's never too late to get improvements committed to core. Feb 26, 2019 at 0:40

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.