Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Unable connect to confluence

WHK September 17, 2016

My confluence works fine, but when restart phicical server does not work.

I try start service:

[root@server logs]# service confluence start

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 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.

And the port is opened correctely:

[root@server /]# ps -aux | grep confluence
conflue+   850 27.6 82.4 4056880 1552664 ?     Sl   14:51   3:33 /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 -Xms1024m -Xmx1024m -XX:+UseG1GC -Datlassian.plugins.enable.wait=300 -Djava.awt.headless=true -Xloggc:/opt/atlassian/confluence/logs/gc-2016-09-17_14-51-27.log -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=5 -XX:GCLogFileSize=2M -XX:-PrintGCDetails -XX:+PrintGCDateStamps -XX:-PrintTenuringDistribution -Djava.endorsed.dirs=/opt/atlassian/confluence/endorsed -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      2672  0.0  0.0 112668   972 pts/0    S+   15:04   0:00 grep --color=auto confluence

[root@server /]# netstat -noa | grep 8090
tcp       11      0 0.0.0.0:8090            0.0.0.0:*               LISTEN      keepalive (0,09/0/0)
tcp        0      0 192.168.122.10:8090     10.8.0.10:52132         SYN_RECV    on (3,69/2/0)
tcp      366      0 127.0.0.1:8090          127.0.0.1:36380         CLOSE_WAIT  off (0.00/0/0)
tcp      314      0 127.0.0.1:8090          127.0.0.1:36466         CLOSE_WAIT  off (0.00/0/0)
tcp      312      0 127.0.0.1:8090          127.0.0.1:36428         CLOSE_WAIT  off (0.00/0/0)
tcp      312      0 127.0.0.1:8090          127.0.0.1:36436         CLOSE_WAIT  off (0.00/0/0)
tcp      314      0 127.0.0.1:8090          127.0.0.1:36514         CLOSE_WAIT  off (0.00/0/0)
tcp      316      0 127.0.0.1:8090          127.0.0.1:36524         CLOSE_WAIT  off (0.00/0/0)
tcp        1      0 192.168.122.10:8090     10.8.0.10:51692         CLOSE_WAIT  off (0.00/0/0)
tcp      368      0 127.0.0.1:8090          127.0.0.1:36414         CLOSE_WAIT  off (0.00/0/0)
tcp      584      0 192.168.122.10:8090     10.8.0.13:51872         CLOSE_WAIT  off (0.00/0/0)
tcp      314      0 127.0.0.1:8090          127.0.0.1:36484         CLOSE_WAIT  off (0.00/0/0)
tcp      366      0 127.0.0.1:8090          127.0.0.1:36384         CLOSE_WAIT  off (0.00/0/0)

But the browser is freeze in "sending request".

The firewall (firewalld and iptables) is down.

Other request works fine:

  • http://192.168.122.10/ -> it works! (apache2)
  • http://192.168.122.10:8090/ -> freeze

Whats happens?

 

2 answers

0 votes
noamdah
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 17, 2016

By the information provided everything looks good.
Another good way to check out the status of your confluence state is by going to this URL:
http://<url>/status
As you have mentioned that after 10 minutes everything looks ok, this is usual especially in big envs as confluence takes a while to start up especially after a reboot.
To reduce startup time go you can add more resources to the server. (CPU / RAM)

Another thing is when seeing the "freezes" as you have mentioned that could also be due to confluence database connection.
If this keeps on happening and is affecting your work/users raise a support ticket at Atlassian Support.

0 votes
WHK September 17, 2016

Finally the confluence works after 10 minutes of starting. Why it happened?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events