Confluence not accessible through browser

[Oliver Dalton]

Hi, we are running opensuse Confluence in-house on Postgres DB using the default out of the box config (8090).  The service has been running great but today the server wasn't responding so I did a restart of the service. "/etc/init.d/confluence restart" and now we cant hit the IP:PORT - I think the issue is something to do with the Tomcat server but im unsure how to debug this.  Not sure what the scheduler_Worker- thread means in the catalina dump. Any help would be very appreciated.  Thanks  

Restart console output

confluence:/opt/atlassian/confluence/bin # /etc/init.d/confluence restart
executing using dedicated user
If you encounter issues starting up Confluence, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide

Server startup logs are located in /opt/atlassian/confluence/logs/catalina.out
---------------------------------------------------------------------------
Using Java: /opt/atlassian/confluence/jre//bin/java
2018-06-06 13:54:50,760 INFO [main] [atlassian.confluence.bootstrap.SynchronyProxyWatchdog] A Context element for ${confluence.context.path}/synchrony-proxy is found in /opt/atlassian/confluence/conf/server.xml. No further action is required
---------------------------------------------------------------------------
Using CATALINA_BASE: /opt/atlassian/confluence
Using CATALINA_HOME: /opt/atlassian/confluence
Using CATALINA_TMPDIR: /opt/atlassian/confluence/temp
Using JRE_HOME: /opt/atlassian/confluence/jre/
Using CLASSPATH: /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/confluence/work/catalina.pid
Tomcat stopped.

To run Confluence in the foreground, start the server with start-confluence.sh -fg
executing using dedicated user: confluence
If you encounter issues starting up Confluence, please see the Installation guide at http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide

Server startup logs are located in /opt/atlassian/confluence/logs/catalina.out
---------------------------------------------------------------------------
Using Java: /opt/atlassian/confluence/jre//bin/java
2018-06-06 13:54:52,306 INFO [main] [atlassian.confluence.bootstrap.SynchronyProxyWatchdog] A Context element for ${confluence.context.path}/synchrony-proxy is found in /opt/atlassian/confluence/conf/server.xml. No further action is required
---------------------------------------------------------------------------
Using CATALINA_BASE: /opt/atlassian/confluence
Using CATALINA_HOME: /opt/atlassian/confluence
Using CATALINA_TMPDIR: /opt/atlassian/confluence/temp
Using JRE_HOME: /opt/atlassian/confluence/jre/
Using CLASSPATH: /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar
Using CATALINA_PID: /opt/atlassian/confluence/work/catalina.pid
Tomcat started.

wget log

confluence:/opt/atlassian/confluence/bin # wget localhost:8090
--2018-06-06 13:57:50-- http://localhost:8090/
Resolving localhost (localhost)... ::1, 127.0.0.1
Connecting to localhost (localhost)|::1|:8090... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-06-06 13:57:50 ERROR 404: Not Found.

Postgres status

confluence:/opt/atlassian/confluence/bin # service postgresql status
* postgresql.service - PostgreSQL database server
Loaded: loaded (/usr/lib/systemd/system/postgresql.service; enabled; vendor preset: disabled)
Active: active (running) since Wed 2018-06-06 14:00:52 AWST; 4s ago
Process: 6194 ExecStop=/usr/lib/postgresql-init stop (code=exited, status=0/SUCCESS)
Process: 6205 ExecStart=/usr/lib/postgresql-init start (code=exited, status=0/SUCCESS)
Main PID: 6218 (postgres)
Tasks: 7 (limit: 512)
CGroup: /system.slice/postgresql.service
|-6218 /usr/lib/postgresql96/bin/postgres -D /var/lib/pgsql/data
|-6219 postgres: logger process
|-6221 postgres: checkpointer process
|-6222 postgres: writer process
|-6223 postgres: wal writer process
|-6224 postgres: autovacuum launcher process
`-6225 postgres: stats collector process

Jun 06 14:00:51 confluence systemd[1]: Starting PostgreSQL database server...
Jun 06 14:00:51 confluence postgresql-init[6205]: 2018-06-06 14:00:51 AWST LOG: redirecting log output to logging collector process
Jun 06 14:00:51 confluence postgresql-init[6205]: 2018-06-06 14:00:51 AWST HINT: Future log output will appear in directory "pg_log".
Jun 06 14:00:52 confluence systemd[1]: Started PostgreSQL database server.

catalina.2018-06-06.log

https://pastebin.com/r6DCVfUq

ps -ef | grep confluence

confluence:/opt/atlassian/confluence/bin # ps -ef | grep confluence
conflue+ 5963 1 4 13:54 ? 00:00:28 /opt/atlassian/confluence/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/confluence/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dconfluence.context.path= -Datlassian.plugins.startup.options= -Dorg.apache.tomcat.websocket.DEFAULT_BUFFER_SIZE=32768 -Dsynchrony.enable.xhr.fallback=true -Xms1024m -Xmx1024m -XX:+UseG1GC -Datlassian.plugins.enable.wait=300 -Djava.awt.headless=true -XX:G1ReservePercent=20 -Xloggc:/opt/atlassian/confluence/logs/gc-2018-06-06_13-54-52.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -XX:-PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintTenuringDistribution -Dignore.endorsed.dirs= -classpath /opt/atlassian/confluence/bin/bootstrap.jar:/opt/atlassian/confluence/bin/tomcat-juli.jar -Dcatalina.base=/opt/atlassian/confluence -Dcatalina.home=/opt/atlassian/confluence -Djava.io.tmpdir=/opt/atlassian/confluence/temp org.apache.catalina.startup.Bootstrap start
root 6250 3578 0 14:06 pts/0 00:00:00 grep --color=auto confluence

[Shankar Asam {Appfire} · Accepted solution]

This look like a duplicate of below;

https://community.atlassian.com/t5/Confluence-questions/Cant-start-confluence-and-connect-through-browser-8090/qaq-p/814941#M110093

[Oliver Dalton]

HI Shankar, 

Thank you for the response.

The /etc/hosts file does contain the hostname and IP address of the server.

As I said the server had been running fine, then just hung and wouldn't restart the service instead deciding to throw lots of Java errors.

I managed to get this working again by using these CMDs.

ps -ef | grep confluence

ps -ef | grep postgres - (we are using postgres)

It seemed that a PostgreSQL process had remained open and was preventing the confluence service from to fully starting.

I had a look at the "atlassian-confluence.log" @ /var/atlassian/application-data/confluence/logs but I couldn't see any useful information here.

I found the "catalina.out" @ /opt/atlassian/confluence/logs had information about confluence not starting.

This cmd ps -ef | grep Postgres showed that a Postgres process was running and killing this allowed the service to restart successfully.

When the server starts up correctly you should see in the "atlassian-confluence.log".

--------------------------
Build Information
--------------------------

--------------------------
Server Information
--------------------------

--------------------------
Database Information
--------------------------

--------------------------
Global Settings
--------------------------

--------------------------
Usage Info
--------------------------

--------------------------
Enabled Plugins
--------------------------

etc

Thanks

[Elina Williams]

At the point when ANY client attempts to open Jira in Firefox, it sets long time range to open and same for any activities we perform like it requires investment to load the menu when we tap on the drop-downs and loads quick in Chrome. Visit Mozilla Support to know further.