Bitbucket<->Jira Login

[FScheidig]

Hi,

we did a server (running Jira and Bitbucket) reboot. Since then I am not able to log into BitBucket. Jira works as expected: I can login using my username and password.

BitBucket is configured to look up the users and their pwd at Jira.

In the top left corner the services are listed for changing fast between them.

So in Jira I can change to BitBucket, but BitBucket does not list Jira. It seem's like BitBucket not finding Jira.

Catalina.log states one error:

09-Jul-2019 09:26:20.964 SCHWERWIEGEND [main] org.apache.catalina.core.StandardService.startInternal Failed to start connector [Connector[HTTP/1.1-8080]]
org.apache.catalina.LifecycleException: Failed to start component [Connector[HTTP/1.1-8080]]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:167)
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:440)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:793)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.startup.Catalina.start(Catalina.java:687)
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:353)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:493)
Caused by: org.apache.catalina.LifecycleException: Protocol handler start failed
at org.apache.catalina.connector.Connector.startInternal(Connector.java:1020)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
... 11 more
Caused by: java.net.BindException: Address already in use: bind
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:219)
at org.apache.tomcat.util.net.AbstractEndpoint.start(AbstractEndpoint.java:1156)
at org.apache.coyote.AbstractProtocol.start(AbstractProtocol.java:591)
at org.apache.catalina.connector.Connector.startInternal(Connector.java:1018)
... 12 more

 Bitbucket doesn't give any feedback, except a good start. I don't know further on.

I also don't have a local user in bitbucket at the moment.

Any help for logging into bitbucket is appreciated.

[Alexis Robert · Accepted solution]

Hi @FScheidig , 

in your log there is an error displayed:

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

This means that Bitbucket is trying to listen on a port that is already in use. You should check the processes on your server and see if there is not another instance running.

[FScheidig]

thanks for your answer. I did a netstat -a -b and the port is not listed so it is free. It is also the output of jira for port 8080 (so http), which I disabled, as I only use port 8443 for https.

Jira also starts the web-gui and seems to work fine. I think the problem is on the bitbucket side, but I do not get any feedback/ log/ output.

I found this instruction: https://confluence.atlassian.com/bitbucketserver061/lockout-recovery-process-968675157.html

and tried to go through them. I am not able to start bitbucket from command line. The Java window opens, after some seconds it is closing again. There is no output in the java window. Same behaviour for running without elasticsearch. So I am only able to run bitbucket as service, which then won't run in recovery mode. Here too: no log output or other information.

[Alexis Robert]

I would still change the bitbucket port, just to make sure that this is not the issue. Try changing it to 9090 for example.

[FScheidig]

thanks for your hard asking for this port.

It seems another application did start before jira started. Now that I shut it down, Jira and BitBucket restarted, everything is working as expected.

Thank you