Atlassian confluence connect problem
Asked by ???:

Hello,

I recently install confluence on my server(CentOS).

1. I downloaded 'atlassian-confluence-7.2.0.tar.gz'.

2. I commanded 'tar -xvf atlassian-confluence-7.2.0.tar.gz'.

3. I edited 'confluence-home' path.

4. I started confluence using 'start-confluence.sh'.

Result.

When I commanded 'ps -ef \| grep tomcat', that returned tomcat information for confluence.

And I commanded 'netstat -tnlp', then there was 8090 port.

But, I can not connect it using browsers or curl command.

I checked the logs.

**confluence-home/logs/atlassian-confluence.log**

2019-12-20 16:10:18,352 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 7.2.0 \[build 8401 based on commit hash 912a577971fe711d4a876d9130277d03b009a0bf\] - synchrony version 3.1.0-master-0f086db5  
2019-12-20 16:10:20,074 WARN \[Catalina-utility-1\] \[com.atlassian.config.ApplicationConfig\] setApplicationHome Application home does not exist. Creating directory: confluence-home/shared-home  
2019-12-20 16:10:20,079 INFO \[Catalina-utility-1\] \[atlassian.confluence.cluster.DefaultClusterConfigurationHelper\] lambda$saveSetupConfigIntoSharedHome$9 Writing setup configuration into shared home...  
2019-12-20 16:10:20,142 INFO \[Catalina-utility-1\] \[atlassian.confluence.cluster.DefaultClusterConfigurationHelper\] lambda$saveSetupConfigIntoSharedHome$9 Finished writing setup configuration into shared home  
2019-12-20 16:10:21,181 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] lambda$earlyStartup$3 Plugin system earlyStartup begun  
2019-12-20 16:10:21,679 WARN \[Catalina-utility-1\] \[org.twdata.pkgscanner.ExportPackageListBuilder\] logDuplicateWarning Package Scanner found duplicates for package 'com.atlassian.integration.jira.applinks' with different versions. Files: confluence-7.2.0.jar and jira-integration-spi-6.2.0.jar  
'confluence/WEB-INF/lib/confluence-7.2.0.jar'  
'confluence/WEB-INF/lib/jira-integration-spi-6.2.0.jar'  
2019-12-20 16:10:22,483 WARN \[FelixStartLevel\] \[extender.internal.support.ExtenderConfiguration\] addDefaultDependencyFactories Gemini Blueprint extensions bundle not present, annotation processing disabled.  
2019-12-20 16:10:23,564 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] logTime Plugin system earlyStartup ended  
2019-12-20 16:10:23,566 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] lambda$lateStartup$4 Plugin system lateStartup begun  
2019-12-20 16:10:24,911 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] logTime Plugin system lateStartup ended  
2019-12-20 16:10:25,201 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] init Confluence is ready to serve  
2019-12-20 16:21:38,845 FATAL \[Catalina-utility-2\] \[atlassian.spring.container.SpringContainerContext\] getComponent Spring Application context has not been set  
2019-12-20 16:21:38,845 WARN \[Catalina-utility-2\] \[atlassian.confluence.plugin.PluginFrameworkContextListener\] contextDestroyed Failed to shut down plugin system during ServletContext shutdown: Spring Application context has not been set  
2019-12-20 16:21:38,857 INFO \[Catalina-utility-2\] \[com.atlassian.confluence.lifecycle\] contextDestroyed Stopping Confluence  
2019-12-20 16:21:38,859 INFO \[Catalina-utility-2\] \[atlassian.plugin.manager.DefaultPluginManager\] lambda$shutdown$5 Preparing to shut down the plugin system  
2019-12-20 16:21:38,860 INFO \[Catalina-utility-2\] \[atlassian.plugin.manager.DefaultPluginManager\] lambda$shutdown$5 Shutting down the plugin system  
2019-12-20 16:21:38,915 WARN \[FelixStartLevel\] \[plugin.osgi.factory.OsgiBundlePlugin\] disableInternal Cannot disable Bundle 'com.atlassian.platform.spring-velocity-support-0.0.7', not ACTIVE  
2019-12-20 16:21:45,288 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 7.2.0 \[build 8401 based on commit hash 912a577971fe711d4a876d9130277d03b009a0bf\] - synchrony version 3.1.0-master-0f086db5  
2019-12-20 16:21:47,612 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] lambda$earlyStartup$3 Plugin system earlyStartup begun  
2019-12-20 16:21:48,162 WARN \[Catalina-utility-1\] \[org.twdata.pkgscanner.ExportPackageListBuilder\] logDuplicateWarning Package Scanner found duplicates for package 'com.atlassian.integration.jira.applinks' with different versions. Files: confluence-7.2.0.jar and jira-integration-spi-6.2.0.jar  
'confluence/WEB-INF/lib/confluence-7.2.0.jar'  
'confluence/WEB-INF/lib/jira-integration-spi-6.2.0.jar'  
2019-12-20 16:21:48,960 WARN \[FelixStartLevel\] \[extender.internal.support.ExtenderConfiguration\] addDefaultDependencyFactories Gemini Blueprint extensions bundle not present, annotation processing disabled.  
2019-12-20 16:21:50,023 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] logTime Plugin system earlyStartup ended  
2019-12-20 16:21:50,025 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] lambda$lateStartup$4 Plugin system lateStartup begun  
2019-12-20 16:21:51,441 INFO \[Catalina-utility-1\] \[atlassian.plugin.manager.DefaultPluginManager\] logTime Plugin system lateStartup ended  
2019-12-20 16:21:51,723 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] init Confluence is ready to serve

**confluence/logs/catalina.out**

20-Dec-2019 16:10:16.932 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:10:16.967 WARNING \[main\] org.apache.catalina.startup.SetAllPropertiesRule.begin \[SetAllPropertiesRule\]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.  
20-Dec-2019 16:10:16.976 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:10:16.980 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:10:16.999 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:10:17.011 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:10:17.140 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:10:17.154 INFO \[main\] org.apache.catalina.startup.Catalina.load Server initialization in \[269\] milliseconds  
20-Dec-2019 16:10:17.158 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Tomcat-Standalone\]  
20-Dec-2019 16:10:17.158 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: \[Apache Tomcat/9.0.27\]  
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".  
SLF4J: Defaulting to no-operation (NOP) logger implementation  
SLF4J: See <http://www.slf4j.org/codes.html#StaticLoggerBinder> for further details.  
20-Dec-2019 16:10:17.984 INFO \[Catalina-utility-2\] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath  
20-Dec-2019 16:10:18.034 INFO \[Catalina-utility-2\] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.  
20-Dec-2019 16:10:18.120 INFO \[Catalina-utility-2\] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'  
2019-12-20 16:10:18,352 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 7.2.0 \[build 8401 based on commit hash 912a577971fe711d4a876d9130277d03b009a0bf\] - synchrony version 3.1.0-master-0f086db5  
2019-12-20 16:10:20,074 WARN \[Catalina-utility-1\] \[com.atlassian.config.ApplicationConfig\] setApplicationHome Application home does not exist. Creating directory: confluence-home/shared-home  
2019-12-20 16:10:20,079 INFO \[Catalina-utility-1\] \[atlassian.confluence.cluster.DefaultClusterConfigurationHelper\] lambda$saveSetupConfigIntoSharedHome$9 Writing setup configuration into shared home...  
2019-12-20 16:10:20,142 INFO \[Catalina-utility-1\] \[atlassian.confluence.cluster.DefaultClusterConfigurationHelper\] lambda$saveSetupConfigIntoSharedHome$9 Finished writing setup configuration into shared home  
20-Dec-2019 16:10:25.211 INFO \[main\] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:10:25.219 INFO \[main\] org.apache.catalina.startup.Catalina.start Server startup in \[8,065\] milliseconds  
20-Dec-2019 16:21:38.834 INFO \[main\] org.apache.catalina.core.StandardServer.await A valid shutdown command was received via the shutdown port. Stopping the Server instance.  
20-Dec-2019 16:21:38.835 INFO \[main\] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:21:38.842 INFO \[main\] org.apache.catalina.core.StandardService.stopInternal Stopping service \[Tomcat-Standalone\]  
20-Dec-2019 16:21:38.844 INFO \[Catalina-utility-1\] org.apache.catalina.core.ApplicationContext.log Destroying Spring FrameworkServlet 'dispatcher'  
20-Dec-2019 16:21:38.943 WARNING \[Catalina-utility-2\] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application \[ROOT\] registered the JDBC driver \[org.h2.Driver\] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.  
20-Dec-2019 16:21:38.949 INFO \[main\] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:21:38.950 INFO \[main\] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:21:43.869 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:21:43.902 WARNING \[main\] org.apache.catalina.startup.SetAllPropertiesRule.begin \[SetAllPropertiesRule\]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.  
20-Dec-2019 16:21:43.911 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:21:43.915 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:21:43.934 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:21:43.945 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin Match \[Server/Service/Engine/Host/Context\] failed to set property \[debug\] to \[0\]  
20-Dec-2019 16:21:44.074 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:21:44.088 INFO \[main\] org.apache.catalina.startup.Catalina.load Server initialization in \[266\] milliseconds  
20-Dec-2019 16:21:44.091 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Tomcat-Standalone\]  
20-Dec-2019 16:21:44.091 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: \[Apache Tomcat/9.0.27\]  
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".  
SLF4J: Defaulting to no-operation (NOP) logger implementation  
SLF4J: See <http://www.slf4j.org/codes.html#StaticLoggerBinder> for further details.  
20-Dec-2019 16:21:44.891 INFO \[Catalina-utility-2\] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath  
20-Dec-2019 16:21:44.934 INFO \[Catalina-utility-2\] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.  
20-Dec-2019 16:21:45.027 INFO \[Catalina-utility-2\] org.apache.catalina.core.ApplicationContext.log Initializing Spring DispatcherServlet 'dispatcher'  
2019-12-20 16:21:45,288 INFO \[Catalina-utility-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 7.2.0 \[build 8401 based on commit hash 912a577971fe711d4a876d9130277d03b009a0bf\] - synchrony version 3.1.0-master-0f086db5  
20-Dec-2019 16:21:51.731 INFO \[main\] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler \["http-nio-8090"\]  
20-Dec-2019 16:21:51.738 INFO \[main\] org.apache.catalina.startup.Catalina.start Server startup in \[7,650\] milliseconds

**confluence/logs/synchrony-proxy-watchdog.log**

2019-12-20 16:10:16,704 INFO \[main\] \[atlassian.confluence.bootstrap.SynchronyProxyWatchdog\] A Context element for ${confluence.context.path}/synchrony-proxy is found in confluence/conf/server.xml. No further action is required


Answers:
author: brbojorque
body: Hi [@???](/t5/user/viewprofilepage/user-id/3684380) ,

From the looks of it, the startup logs is normal.

In one of the logs it says Confluence is ready to serve.

-

Try to diagnose the firewall and make sure the server is accessible externally.

use iptables or firewall-cmd, make sure the inbound port 8090 is accesible.

If you are using AWS / Azure, make sure the Security group is open to accept 8090 port.


author: DPKJ
body: [@???](/t5/user/viewprofilepage/user-id/3684380) Welcome to the community!

With the logs you have provided it is not clear that if your Confluence setup have any issues.

Have you gone through this - <https://confluence.atlassian.com/confkb/confluence-is-not-accessible-after-installation-on-centos-7-712411366.html>

If not please take a look at this, and see if issue get resolved.


Tags: confluence-server

server