Cant start confluence and connect through browser:8090
Asked by Oliver Dalton:

Our server hung so we restarted the service /etc/init.d/confluence restart and it never can back. see: (catalina.out log) <https://pastebin.com/NRahtGCz>

We are running the standalone server on Opensuse on a VM with 4 cpu 12gb ram 60gb hss, and the default config 8090 with the context path "" with a Postgres DB.

The service says that the confluence has started ok, but the browser never connects to the IP:PORT.

confluence:\~ # service confluence status  
\* confluence.service  
Loaded: loaded (/etc/init.d/confluence; bad; vendor preset: disabled)  
Active: active (exited) since Thu 2018-06-07 09:40:11 AWST; 26min ago  
Docs: man:systemd-sysv-generator(8)  
Process: 2012 ExecStart=/etc/init.d/confluence start (code=exited, status=0/SUCCESS)  
Tasks: 0 (limit: 512)

Jun 07 09:40:10 confluence su\[2019\]: (to confluence) root on none  
Jun 07 09:40:10 confluence su\[2019\]: pam_unix(su:session): session opened for user confluence by (uid=0)  
Jun 07 09:40:11 confluence confluence\[2012\]: If you encounter issues starting up Confluence, please see the Installation guide at <http://confluence.atlassian.com/display/DOC/Confluence+Installation+Guide>  
Jun 07 09:40:11 confluence confluence\[2012\]: Server startup logs are located in /opt/atlassian/confluence/logs/catalina.out  
Jun 07 09:40:11 confluence confluence\[2012\]: ---------------------------------------------------------------------------  
Jun 07 09:40:11 confluence confluence\[2012\]: Using Java: /opt/atlassian/confluence/jre//bin/java  
Jun 07 09:40:11 confluence confluence\[2012\]: 2018-06-07 09:40:11,909 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  
Jun 07 09:40:11 confluence confluence\[2012\]: ---------------------------------------------------------------------------  
Jun 07 09:40:11 confluence confluence\[2012\]: Tomcat started.  
Jun 07 09:40:11 confluence systemd\[1\]: Started confluence.service.

confluence:\~ # ps -ef \| grep confluence  
conflue+ 2078 1 2 09:40 ? 00:00:39 /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-07_09-40-11.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 2281 1889 0 10:12 pts/0 00:00:00 grep --color=auto confluence

The start of our atlassian-confluence.log (its such a big file we cant add it all!)

<https://pastebin.com/pxrKNMFS>

and the end of our atlassian-confluence.log

<https://pastebin.com/XPE3J060>

Thanks


Answers:
author: Shankar Asam {Appfire}
body: Hi Oliver,

You may take a look at below article for the issue you're experiencing with;

<https://confluence.atlassian.com/confkb/confluence-logs-errors-this-prevents-creation-of-a-guid-due-to-incorrect-host-name-235668247.html>

Typically, you will need to add the hostname to /etc/hosts file on the server with IP address.

thanks

comments: author: Oliver Dalton
body: 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


author: Shankar Asam {Appfire}
body: Good to know its working. :)


Tags: error

startup

tomcat