Cannot access Confluence after installation

Hello everybody,

I've installed Confluence on our Unix environment and I have various issues while bringing this instance to work.

Right after the installation I cannot access Confluence direclty via browser and IP -> The page stays blank.

While using an SSH tunnel over my own IP I could access through localhost:8090 and did the first configuration (set database, etc.). Because I couldn't get access directly I tried various things: Setting an Apache (httpd) before Confluence, shut down firewall and so on. Now I cannot open Confluence in any possible way although it seems that Confluence starts regulary.

So currently, the firewall and the httpd daemon are off. The localhost log of the Confluence' Tomcat is empty and the catalina.out looks following:

Nov 25, 2014 6:01:46 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not fin                                                                                                                                                             d a matching property.
Nov 25, 2014 6:01:46 PM org.apache.catalina.startup.SetAllPropertiesRule begin
WARNING: [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debu                                                                                                                                                             g' to '0' did not find a matching property.
Nov 25, 2014 6:01:46 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to                                                                                                                                                              '0' did not find a matching property.
Nov 25, 2014 6:01:46 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'debug                                                                                                                                                             ' to '0' did not find a matching property.
Nov 25, 2014 6:01:46 PM org.apache.tomcat.util.digester.SetPropertiesRule begin
WARNING: [SetPropertiesRule]{Server/Service/Engine/Host/Context} Setting propert                                                                                                                                                             y 'debug' to '0' did not find a matching property.
Nov 25, 2014 6:01:47 PM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8090"]
Nov 25, 2014 6:01:47 PM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 642 ms
Nov 25, 2014 6:01:47 PM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Tomcat-Standalone
Nov 25, 2014 6:01:47 PM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.52
2014-11-25 18:01:57,533 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 5.6.4 [build 5637 based on commit hash e1ef10868e8fe2f234a1a0b171b01cde1d9717c4]
Nov 25, 2014 6:04:14 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error filterStart
Nov 25, 2014 6:04:14 PM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [] startup failed due to previous errors
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [com.mysql.fabric.jdbc.FabricMySQLDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [org.hsqldb.jdbc.JDBCDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [org.postgresql.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesJdbc
SEVERE: The web application [] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-1] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-2] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-3] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-4] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-5] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-6] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-7] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-8] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-9] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [scheduler_Worker-10] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.catalina.loader.WebappClassLoader clearReferencesThreads
SEVERE: The web application [] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak.
Nov 25, 2014 6:04:14 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8090"]
Nov 25, 2014 6:04:14 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 147831 ms

I'm totally confused by the various and severe errors.

We use a mysql database. The connector is in the WEB-INF/lib, so I don't understand some jdbc errors.

The user "confluence " has all right on conf/, logs/, temp/ and work/

Maybe the server.xml is also interesting for you

<Server port="8000" shutdown="SHUTDOWN" debug="0">
    <Service name="Tomcat-Standalone">
        <Connector port="8090" connectionTimeout="20000"
         maxThreads="200" redirectPort="8443" minSpareThreads="10"
         disableUploadTimeout="true"
         enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8" />
        <Engine name="Standalone" defaultHost="localhost" debug="0">
            <Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="false">
                <Context path="" docBase="../confluence" debug="0" reloadable="false" useHttpOnly="true">
                    <!-- Logger is deprecated in Tomcat 5.5. Logging configuration for Confluence is specified in confluence/WEB-INF/classes/log4j.properties -->
                    <Manager pathname="" />
                </Context>
            </Host>
        </Engine>
        <!--
            To run Confluence via HTTPS:
             * Uncomment the Connector below
             * Execute:
                 %JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
                 $JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA  (Unix)
               with a password value of "changeit" for both the certificate and the keystore itself.
             * Restart and visit https://localhost:8443/
             For more info, see http://confluence.atlassian.com/display/DOC/Adding+SSL+for+Secure+Logins+and+Page+Security
        -->
<!--
        <Connector port="8443" maxHttpHeaderSize="8192"
                   maxThreads="150" minSpareThreads="25"
                   enableLookups="false" disableUploadTimeout="true"
                   acceptCount="100" scheme="https" secure="true"
                   clientAuth="false" sslProtocol="TLS" SSLEnabled="true"
                   URIEncoding="UTF-8" keystorePass="<MY_CERTIFICATE_PASSWORD>"/>
-->
    </Service>
</Server>

I hope I've provided you the required information, which can help.

Thank you very much in advance.

Best regards, Dominic

4 answers

1 accepted

Hi Dominc,

You might want to check the atlassian-confluence.log that is located in the <home-folder>/logs. Just because the logs that you've mentioned didn't bring good information to us to work on.
Cheers,

WZ

Dominic,

I don't see any data sources configured in your server.xml. I suspect that may well be it. Tomcat starts but no declared access to a database which is where, I think, we find the root of all the OTHER errors following that. I am using postgresql and have (among other datasources I've configured to my Tomcat instance) the following lines:

<Resource name="jdbc/confluence" auth="Container" type="javax.sql.DataSource"
username="<your_db_username>"
password="<your_db_password>"
driverClassName="org.postgresql.Driver"
url="jdbc:postgresql://127.0.0.1:5432/confluence"
maxActive="20"
maxIdle="10"
validationQuery="select 1" />

Since I don't see those, I suspect it is the root of all your evils.

For full info, start here https://confluence.atlassian.com/display/DOC/Database+Setup+For+MySQL and look also here https://confluence.atlassian.com/display/DOC/Configuring+a+MySQL+Datasource+in+Apache+Tomcat for the full cookbook.

Good luck

Hi Mike,

Thank you for you answer.

We are currently using the JDBC connection which is defined in /var/atlassian/application-data/confluence/confluence.cfg.xml. As I mentioned I was able to do the initial configuration of Confluence (creating database, adding admin user, put in example space,...).

I am not sure if this will help but may I switch from jdbc to a datasource connection...

Hi William,

I wanted to provide you this log file. And now it works smile

Why did this happen? I changed and the log4j log level to debug. So this log file was really huge. I wanted to provide you a reduced version and turned the log level to warn again. Deleted the log file and restarted Confluence again. Surprisingly I was finally able to log in to Confluence.

So I tested again and changed the log level and Confluence start took very long. Maybe some components are hanging because of this. Maybe also the database was not started after restarting the machine idk

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Oct 24, 2018 in Confluence

Atlassian Research opportunity with Confluence templates

Do you use templates with Confluence? Take part in a remote 1-hr workshop. You'll receive USD $100 for your time!   We're looking for people to participate in a   remote 1-hr workshop...

1,100 views 17 14
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you