httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 48388] mod proxy disabling workers after a single error
Date Mon, 29 Mar 2010 18:35:46 GMT

Daniel Ruggeri <> changed:

           What    |Removed                     |Added
             Status|NEW                         |NEEDINFO

--- Comment #1 from Daniel Ruggeri <> 2010-03-29 18:35:45 UTC ---
   Have you had the opportunity to set LogLevel to debug for additional
information and confirmed that all logging is making it to the error_log in
question? Given your configuration, I think the error is happening as a request
is being processed. Do you have any way to duplicate this problem or perhaps
confirm that the backend is not having any sort of problems?

The relevant code in question is in modules/proxy/proxy_util.c
     * Put the entire worker to error state if
     * the PROXY_WORKER_IGNORE_ERRORS flag is not set.
     * Altrough some connections may be alive
     * no further connections to the worker could be made
    if (!connected && PROXY_WORKER_IS_USABLE(worker) &&
        !(worker->s->status & PROXY_WORKER_IGNORE_ERRORS)) {
        worker->s->status |= PROXY_WORKER_IN_ERROR;
        worker->s->error_time = apr_time_now();
        ap_log_error(APLOG_MARK, APLOG_ERR, 0, s,
            "ap_proxy_connect_backend disabling worker for (%s)",

This is after a loop that will iterate through each backend address returned by
DNS and attempt connection. I ask if this is all of the log because there
should be at least one more error message that accompanies this one.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message