Confluence proxied by httpd - start failures

[Jiri Pik]

I am using virtually identical httpd configuration for JIRA and Confluence - the standard Atlassian recommended config.

JIRA has no problem with rebooting of the AWS EC2 machine.

Confluence, however, very often fails to start on reboot and the only way to get it work is to wait and after 10 minutes reboot again and then the instance starts properly.

During the 10 minute waiting, the httpd logs show

There is nothing odd in the Confluence logs during this time. However, the apache's returned code is 503 - Service unavailable whereas after then 10 minutes with successful reboot, the page keeps loading.

What could be the cause? Is it some delay needed for Apache httpd proxy to start working? How to fix?

[Gonchik Tsymzhitov]

Hi Jiri, 

Could you provide httpd virtual host conf, and connector config in confluence server.xml?

Cheers,

Gonchik Tsymzhitov

[Jiri Pik]

HI: 

THANK YOU.

My hypothesis is that the whenever there is some longer change of config / initialization to take place, the first reboot fails. For example, when I upgraded the MySQL jar file (removed the old one and put in the new one) it failed on reboot. 

The relevant httpd config is

<Directory />
 AllowOverride none
 Require all denied
</Directory> 

<Proxy *>
 Require all granted
</Proxy>

SSLProxyEngine On
ProxyRequests Off

ProxyPass /synchrony http://localhost:8091/synchrony
 
<Location /synchrony>
 Require all granted
 RewriteEngine on
 RewriteCond %{HTTP:UPGRADE} ^WebSocket$ [NC]
 RewriteCond %{HTTP:CONNECTION} Upgrade$ [NC]
 RewriteRule .* ws://localhost:8091%{REQUEST_URI} [P]
</Location>

ProxyPass / http://localhost:8090/
ProxyPassReverse / http://localhost:8090/

<Location />
 Require all granted
</Location>

The connector is 

        <Connector port="8090" connectionTimeout="20000" redirectPort="8443" maxThreads="48" minSpareThreads="10" enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8" protocol="org.apache.coyote.http11.Http11NioProtocol" proxyName="confluence.myfirm.com" proxyPort="443" scheme="https"/> 

What could be the cause?