Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Installing Jira + Confluence + Bitbucket together in Digital Ocean

eugene tang
eugene tang October 13, 2017

hi im installing confulence jira and bitbucket into the same server. 

 

i have tried the installation which i have both installed successfully on the shell command.

 

but on the website 

 

http://139.59.115.69:8080 <-- i am only able to view this (JIRA)

 

But not this http://139.59.115.69:8090 <-- Confluence

 

it redirects to this link which i dont know whats wrong please advise

http://139.59.115.69:8090/bootstrap/selectsetupstep.action

 

 

Answer
Watch
Like Be the first to like this
1895 views

4 answers

0 votes
eugene tang
eugene tang October 15, 2017

any idea ?

View More Comments
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
October 16, 2017

Yes, there's something already running on the server on that port.

Try running "netstat -plant | grep 8090" to see what it is.

Like
eugene tang
eugene tang October 18, 2017

root@renolah:~# netstat -plant | grep 8090

root@renolah:~# netstat -plant | grep 8090

root@renolah:~#

Like
AnnWorley
AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 18, 2017

I am suspecting port 8000, the default "server port" for Tomcat is the one that is occupied because of this in your log:

14-Oct-2017 15:53:35.441 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8000]:
java.net.BindException: Address already in use (Bind failed)

That port is designated in <confluence install dir>/conf/server.xml. It usually looks something like this:

<Server port="8000" shutdown="SHUTDOWN" debug="0">
 <Service name="Tomcat-Standalone">
 <Connector port="8090" connectionTimeout="20000" redirectPort="8443"
 maxThreads="48" minSpareThreads="10"
 enableLookups="false" acceptCount="10" debug="0" URIEncoding="UTF-8"
 protocol="org.apache.coyote.http11.Http11NioProtocol" />
  • Please run Nic's suggested grep on port 8000 to see if something is taking up that port.
  • Please make sure Confluence shuts down completely between restarts.
Like
Reply
0 votes
eugene tang
eugene tang October 14, 2017

i tried running in the command line below it shows this

 

please advise

 

root@renolah:/opt/atlassian/confluence/bin# ./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

2017-10-14 15:53:19,636 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

14-Oct-2017 15:53:20.252 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server} Setting property 'debug' to '0' did not find a matching property.

14-Oct-2017 15:53:20.417 WARNING [main] org.apache.catalina.startup.SetAllPropertiesRule.begin [SetAllPropertiesRule]{Server/Service/Connector} Setting property 'debug' to '0' did not find a matching property.

14-Oct-2017 15:53:20.440 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine} Setting property 'debug' to '0' did not find a matching property.

14-Oct-2017 15:53:20.452 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.

14-Oct-2017 15:53:20.535 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.

14-Oct-2017 15:53:20.584 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.

14-Oct-2017 15:53:21.085 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-8090"]

14-Oct-2017 15:53:21.100 SEVERE [main] org.apache.coyote.AbstractProtocol.init Failed to initialize end point associated with ProtocolHandler ["http-nio-8090"]

java.net.BindException: Address already in use

at sun.nio.ch.Net.bind0(Native Method)

at sun.nio.ch.Net.bind(Net.java:433)

at sun.nio.ch.Net.bind(Net.java:425)

at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)

at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:350)

at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:823)

at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:476)

at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:120)

at org.apache.catalina.connector.Connector.initInternal(Connector.java:960)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

at org.apache.catalina.core.StandardService.initInternal(StandardService.java:568)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:871)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

at org.apache.catalina.startup.Catalina.load(Catalina.java:581)

at org.apache.catalina.startup.Catalina.load(Catalina.java:604)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)

 

14-Oct-2017 15:53:21.101 SEVERE [main] org.apache.catalina.core.StandardService.initInternal Failed to initialize connector [Connector[HTTP/1.1-8090]]

org.apache.catalina.LifecycleException: Failed to initialize component [Connector[HTTP/1.1-8090]]

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:107)

at org.apache.catalina.core.StandardService.initInternal(StandardService.java:568)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

at org.apache.catalina.core.StandardServer.initInternal(StandardServer.java:871)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

at org.apache.catalina.startup.Catalina.load(Catalina.java:581)

at org.apache.catalina.startup.Catalina.load(Catalina.java:604)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.apache.catalina.startup.Bootstrap.load(Bootstrap.java:310)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:484)

Caused by: org.apache.catalina.LifecycleException: Protocol handler initialization failed

at org.apache.catalina.connector.Connector.initInternal(Connector.java:962)

at org.apache.catalina.util.LifecycleBase.init(LifecycleBase.java:102)

... 12 more

Caused by: java.net.BindException: Address already in use

at sun.nio.ch.Net.bind0(Native Method)

at sun.nio.ch.Net.bind(Net.java:433)

at sun.nio.ch.Net.bind(Net.java:425)

at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223)

at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74)

at org.apache.tomcat.util.net.NioEndpoint.bind(NioEndpoint.java:350)

at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:823)

at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:476)

at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:120)

at org.apache.catalina.connector.Connector.initInternal(Connector.java:960)

... 13 more

 

14-Oct-2017 15:53:21.102 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1025 ms

14-Oct-2017 15:53:21.110 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Tomcat-Standalone

14-Oct-2017 15:53:21.110 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.46

14-Oct-2017 15:53:23.769 INFO [localhost-startStop-2] org.apache.catalina.core.ApplicationContext.log Spring WebApplicationInitializers detected on classpath: [com.atlassian.synchrony.proxy.SynchronyDispatcherServletInitializer@254cedaf]

2017-10-14 15:53:24,038 INFO [localhost-startStop-1] [com.atlassian.confluence.lifecycle] contextInitialized Starting Confluence 6.4.2 [build 7401 based on commit hash e170a3915839da2821803843481d4419ff03b453] - synchrony version 1.0.0-release-confluence_6.1-4020a123

2017-10-14 15:53:28,252 INFO [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Populating setup configuration if running with Cluster mode...

2017-10-14 15:53:28,254 WARN [localhost-startStop-1] [atlassian.confluence.cluster.DefaultClusterConfigurationHelper] lambda$populateExistingClusterSetupConfig$1 Could not find shared config file.

14-Oct-2017 15:53:28.297 WARNING [localhost-startStop-2] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [4,449] milliseconds.

14-Oct-2017 15:53:28.596 INFO [localhost-startStop-2] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'dispatcher'

14-Oct-2017 15:53:28.597 INFO [localhost-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization started

14-Oct-2017 15:53:28.611 INFO [localhost-startStop-2] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.prepareRefresh Refreshing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Sat Oct 14 15:53:28 UTC 2017]; root of context hierarchy

14-Oct-2017 15:53:28.691 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]

14-Oct-2017 15:53:29.115 INFO [localhost-startStop-2] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.initialize Initializing ExecutorService  'defaultSockJsTaskScheduler'

14-Oct-2017 15:53:29.510 INFO [localhost-startStop-2] org.springframework.web.socket.server.support.WebSocketHandlerMapping.registerHandler Mapped URL path [/sockjs/v1/**] onto handler of type [class org.springframework.web.socket.sockjs.support.SockJsHttpRequestHandler]

14-Oct-2017 15:53:29.832 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]

14-Oct-2017 15:53:30.049 INFO [localhost-startStop-2] org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.initControllerAdviceCache Looking for @ControllerAdvice: WebApplicationContext for namespace 'dispatcher-servlet': startup date [Sat Oct 14 15:53:28 UTC 2017]; root of context hierarchy

14-Oct-2017 15:53:30.172 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()

14-Oct-2017 15:53:30.173 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)

14-Oct-2017 15:53:30.256 INFO [localhost-startStop-2] org.springframework.context.support.DefaultLifecycleProcessor.start Starting beans in phase 2147483647

14-Oct-2017 15:53:30.293 INFO [localhost-startStop-2] org.springframework.web.servlet.DispatcherServlet.initServletBean FrameworkServlet 'dispatcher': initialization completed in 1696 ms

14-Oct-2017 15:53:35.439 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 14336 ms

14-Oct-2017 15:53:35.441 SEVERE [main] org.apache.catalina.core.StandardServer.await StandardServer.await: create[localhost:8000]:

java.net.BindException: Address already in use (Bind failed)

at java.net.PlainSocketImpl.socketBind(Native Method)

at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)

at java.net.ServerSocket.bind(ServerSocket.java:375)

at java.net.ServerSocket.<init>(ServerSocket.java:237)

at org.apache.catalina.core.StandardServer.await(StandardServer.java:438)

at org.apache.catalina.startup.Catalina.await(Catalina.java:718)

at org.apache.catalina.startup.Catalina.start(Catalina.java:664)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)

at java.lang.reflect.Method.invoke(Method.java:498)

at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)

at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)

 

14-Oct-2017 15:53:35.442 INFO [main] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-8090"]

14-Oct-2017 15:53:35.442 INFO [main] org.apache.catalina.core.StandardService.stopInternal Stopping service Tomcat-Standalone

14-Oct-2017 15:53:35.454 INFO [localhost-startStop-4] org.apache.catalina.core.ApplicationContext.log Destroying Spring FrameworkServlet 'dispatcher'

14-Oct-2017 15:53:35.458 INFO [localhost-startStop-4] org.springframework.web.context.support.AnnotationConfigWebApplicationContext.doClose Closing WebApplicationContext for namespace 'dispatcher-servlet': startup date [Sat Oct 14 15:53:28 UTC 2017]; root of context hierarchy

14-Oct-2017 15:53:35.460 INFO [localhost-startStop-4] org.springframework.context.support.DefaultLifecycleProcessor.stop Stopping beans in phase 2147483647

14-Oct-2017 15:53:35.466 INFO [localhost-startStop-4] org.springframework.context.support.DefaultLifecycleProcessor.stop Stopping beans in phase 0

14-Oct-2017 15:53:35.470 INFO [localhost-startStop-4] org.springframework.scheduling.concurrent.ThreadPoolTaskScheduler.shutdown Shutting down ExecutorService 'defaultSockJsTaskScheduler'

14-Oct-2017 15:53:35.629 WARNING [localhost-startStop-3] 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.

14-Oct-2017 15:53:35.639 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-8090"]

14-Oct-2017 15:53:35.640 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-8090"]

root@renolah:/opt/atlassian/confluence/bin#

Reply
0 votes
AnnWorley
AnnWorley
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
October 13, 2017

Eugene, your Confluence instance is displaying the error from this article:

Confluence does not start due to Spring Application context has not been set

The most common cause is lack of necessary file system permissions for the user running Confluence. There are other possible causes as well:

  1. The user running Confluence does not have write permissions to the home folder defined in <install>/confluence/WEB-INF/classes/confluence-init.properties or the install directory.
  2. You are running Confluence as the root user or if you have an application firewall enabled (SeLinux or AppArmor).
  3. The database driver is not located in the <install>/confluence/WEB-INF/lib folder or you are using a database version that is incompatible with the bundled driver.
  4. The hostname of the server can not be resolved.
    The server does not have enough memory during installation to set up the database, and restarts return this error.
  5. After upgrading the OS, the installation directory might become defective.

The article has suggested resolutions for each cause. Please let us know which one resolves the issue for you. If you run into questions about the resolutions please let us know so we can help.

View More Comments
eugene tang
eugene tang October 14, 2017

i installed it as root in digital ocean as i dont have other users in already

Like
eugene tang
eugene tang October 14, 2017

im using the latest os

 

the host name is not conflicting as its running on 8090

 

i have imported the database into the /confluence/WEB-INF/lib folder

 

i have also set a+x to this filename /confluence/WEB-INF/classes/confluence-init.properties

 

im still getting the same error

Like
Reply
0 votes
Nic Brough -Adaptavist-
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Become a leader
October 13, 2017

Confluence has not finished installing, so you need to answer the questions on that screen.

View More Comments
eugene tang
eugene tang October 14, 2017

theres no answer as it says successfully installed and ask me to go into the link localhost:8090

Like
Reply

Suggest an answer

Log in or Sign up to answer
Confluence
Confluence
TAGS
AUG Leaders

Atlassian Community Events

    See all events