Erro do Apache httpd “proxy: ap_get_scoreboard_lb” com ProxyPass

Question

Eu configurei o apache como proxy para o tomcat, mas estou recebendo o seguinte erro ao segmentar a página. Eu às vezes recebo uma página em branco ou um 503:

[Erro]

[Mon Dec 03 04:58:16 2012] [error] proxy: ap_get_scoreboard_lb(2) failed in child 29611 for worker proxy:reverse
[Mon Dec 03 04:58:16 2012] [error] proxy: ap_get_scoreboard_lb(1) failed in child 29611 for worker https://localhost:8443/
[Mon Dec 03 04:58:16 2012] [error] proxy: ap_get_scoreboard_lb(0) failed in child 29611 for worker http://localhost:8080/

Eu tenho dois vhosts configurados na vm da seguinte forma:

[host http]

<VirtualHost *:80>
  ServerName www.mysite.net
  ServerAlias mysite.net

  ProxyRequests Off
  ProxyPreserveHost On

  <Proxy *>
    Order deny,allow
    Allow from all
  </Proxy>

  ProxyPass / http://localhost:8080/ retry=0
  ProxyPassReverse / http://localhost:8080/ retry=0
</VirtualHost>

[ssl vhost]

<VirtualHost *:443>
        ServerName www.mysite.net
        ServerAlias mysite.net

        ErrorLog /var/log/apache2/error.log

        LogLevel warn

        CustomLog /var/log/apache2/access.log combined
        ServerSignature On

        SSLEngine on
        SSLProxyEngine on
        SSLCertificateFile /etc/apache2/ssl/server.crt
        SSLCertificateKeyFile /etc/apache2/ssl/server.key

        ProxyRequests Off
        ProxyPreserveHost On
        ProxyPass / https://localhost:8443/ retry=0
        ProxyPassReverse / https://localhost:8443/ retry=0

</VirtualHost>

Os detalhes do meu sistema são: Apache / 2.2.22 (Ubuntu) mod_jk / 1.2.32 mod_ssl / 2.2.22 OpenSSL / 1.0.1 mod proxy_http também está ativado.

    

Answer 1

Parece haver uma diferença entre parar e iniciar o apache e fazer um apachectl graceful restarting (ou seja, parar e iniciar ao invés de apachectl restart ) como encontrado em este site :

This is a bit of a guess, and probably wrong, but does stopping and 
starting the server rather than restarting (they're different, 
restarting (including gracefully) doesn't kill the master process) 
help? As I understand it, there are issues in mod_proxy regarding the 
scoreboard size when changes to the config are made between restarts.