Cant start confluence Unable to connect
Asked by amadrigal10:

im just getting this output dont know what to do, little help please!

/opt/atlassian/confluence/bin$ sudo ./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  
2019-05-08 11:29:27,504 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  
08-May-2019 11:29:27.944 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin \[SetPropertiesRule\]{Server} Setting property 'debug' to '0' did not find a matching property.  
08-May-2019 11:29:28.017 WARNING \[main\] org.apache.catalina.startup.SetAllPropertiesRule.begin \[SetAllPropertiesRule\]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.  
08-May-2019 11:29:28.132 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin \[SetPropertiesRule\]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.  
08-May-2019 11:29:28.140 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin \[SetPropertiesRule\]{Server/Service/Engine/Host} Setting property 'debug' to '0' did not find a matching property.  
08-May-2019 11:29:28.184 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin \[SetPropertiesRule\]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.  
08-May-2019 11:29:28.207 WARNING \[main\] org.apache.tomcat.util.digester.SetPropertiesRule.begin \[SetPropertiesRule\]{Server/Service/Engine/Host/Context} Setting property 'debug' to '0' did not find a matching property.  
08-May-2019 11:29:28.503 INFO \[main\] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler \["http-nio-8090"\]  
08-May-2019 11:29:28.517 INFO \[main\] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read  
08-May-2019 11:29:28.526 INFO \[main\] org.apache.catalina.startup.Catalina.load Initialization processed in 668 ms  
08-May-2019 11:29:28.537 INFO \[main\] org.apache.catalina.core.StandardService.startInternal Starting service \[Tomcat-Standalone\]  
08-May-2019 11:29:28.537 INFO \[main\] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/9.0.12  
08-May-2019 11:29:30.011 INFO \[localhost-startStop-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.  
08-May-2019 11:29:30.251 INFO \[localhost-startStop-2\] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: \[com.atlassian.synchrony.proxy.SynchronyDispatcherServletInitializer@54f73682\]  
08-May-2019 11:29:30.480 INFO \[localhost-startStop-2\] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'  
08-May-2019 11:29:30.480 INFO \[localhost-startStop-2\] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization started  
08-May-2019 11:29:30.486 INFO \[localhost-startStop-2\] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.prepareRefresh Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date \[Wed May 08 11:29:30 CDT 2019\]; root of context hierarchy  
08-May-2019 11:29:30.545 INFO \[localhost-startStop-2\] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.loadBeanDefinitions Registering annotated classes: \[class com.atlassian.synchrony.proxy.websocket.WebSocketConfig,class com.atlassian.synchrony.proxy.web.SynchronyWebMvcConfig\]  
08-May-2019 11:29:31.081 INFO \[localhost-startStop-2\] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService 'defaultSockJsTaskScheduler'  
08-May-2019 11:29:31.124 INFO \[localhost-startStop-2\] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path \[/v1/bayeux-sync1\] onto handler of type \[class org.springframework.web.socket.server.support.WebSocketHttpRequestHandler\]  
08-May-2019 11:29:31.526 INFO \[localhost-startStop-2\] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{\[/healthcheck\]}" onto public com.atlassian.synchrony.proxy.web.HealthCheckResult com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.getSynchronyProxyInfo()  
08-May-2019 11:29:31.527 INFO \[localhost-startStop-2\] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerMapping.register Mapped "{\[/reload\],methods=\[PUT\]}" onto public org.springframework.http.ResponseEntity com.atlassian.synchrony.proxy.web.SynchronyProxyRestController.reloadConfiguration(com.atlassian.synchrony.proxy.web.SynchronyProxyConfigPayload)  
08-May-2019 11:29:31.552 INFO \[localhost-startStop-2\] org.springframework.web.servlet.handler.SimpleUrlHandlerMapping.registerHandler Mapped URL path \[/\*\*\] onto handler of type \[class org.springframework.web.servlet.resource.DefaultServletHttpRequestHandler\]  
08-May-2019 11:29:31.591 INFO \[localhost-startStop-2\] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date \[Wed May 08 11:29:30 CDT 2019\]; root of context hierarchy  
08-May-2019 11:29:31.718 INFO \[localhost-startStop-2\] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647  
08-May-2019 11:29:31.743 INFO \[localhost-startStop-2\] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 1263 ms  
2019-05-08 11:29:34,273 INFO \[localhost-startStop-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 6.15.2 \[build 8100 based on commit hash 4410012ac87e845516b70bc69b6f7a893eabaa5a\] - synchrony version 2.1.0-master-9d112c9d  
Killed


Answers:
author: sara
body: This logs doesn't have any error info.

Can you please grep for error in the logs?

comments: author: amadrigal10
body: Thank you sarath, i was finally able to start the server, turns out there were no permissions to write to a tomcat server log.

Thank you for the help!


author: sankar sankar
body: Please Use this It will start Your confluence

export JAVA_OPTS="-Xms6144m -Xmx6144m -XX:NewSize=256m -XX:MaxNewSize=356m -XX:PermSize=256m -XX:MaxPermSize=1024m -XX:+CMSClassUnloadingEnabled -XX:+CMSPermGenSweepingEnabled"


author: Nic Brough -Adaptavist-
body: No, it wont, not until the underlying problem is fixed, as it was explained 2 years ago.


author: Nic Brough -Adaptavist-
body: Ouch. The "killed" at the bottom usually means "something in the operating system terminated the process" The rest of the log is mostly just information about what it's doing, and a couple of warnings.

We'll need to debug what in the OS is killing it. I'd have a quick look at the application log in confluence-home/logs/atlassian-confluence.log to see if there are any pointers in there (like memory or disk errors), but then we're into trying to see why the OS killed it.

comments: author: amadrigal10
body: This is what is on the log, from yesterday nothing from today, is there other place a can look up for errors?

2019-05-07 15:49:55,922 INFO \[localhost-startStop-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 6.4.1 \[build 7401 based on commit hash 3608c8876205b2370b6e8ba55434a77072ed5a3e\] - synchrony version 1.0.0-release-confluence_6.1-4020a123  
2019-05-07 15:49:59,061 INFO \[localhost-startStop-1\] \[atlassian.confluence.cluster.DefaultClusterConfigurationHelper\] lambda$populateExistingClusterSetupConfig$1 Populating setup configuration if running with Cluster mode...  
2019-05-07 15:49:59,314 INFO \[localhost-startStop-1\] \[springframework.web.context.ContextLoader\] initWebApplicationContext Root WebApplicationContext: initialization started  
2019-05-07 15:50:36,392 INFO \[localhost-startStop-1\] \[com.atlassian.confluence.lifecycle\] contextInitialized Starting Confluence 6.4.1 \[build 7401 based on commit hash 3608c8876205b2370b6e8ba55434a77072ed5a3e\] - synchrony version 1.0.0-release-confluence_6.1-4020a123  
2019-05-07 15:50:39,740 INFO \[localhost-startStop-1\] \[atlassian.confluence.cluster.DefaultClusterConfigurationHelper\] lambda$populateExistingClusterSetupConfig$1 Populating setup configuration if running with Cluster mode...  
2019-05-07 15:50:39,858 INFO \[localhost-startStop-1\] \[springframework.web.context.ContextLoader\] initWebApplicationContext Root WebApplicationContext: initialization started


author: Nic Brough -Adaptavist-
body: You will need to look at what the operating system is doing to kill the process.

Your logs look like a well-behaving application before the OS kills it.


author: amadrigal10
body: Thank you Nic, i was finally able to start the server, turns out there were no permissions to write to a tomcat server log.

Thank you for the help!


Tags: confluence-server

server