SpringMVC dispatcher could not be started, but no errors in logs

We are currently in process of upgrading from stash 3.8 to the latest 4.10.1, and on our testplatform when we run startup.sh

We get this erorr on the webpage:

A fatal error has occurred
The following problem occurred, which prevents Atlassian Bitbucket from starting:
SpringMVC dispatcher [springMvc] could not be started

 

However in our catalina.out and localhost log file we get no errors.

In the localhost log it just hangs on Initializing Spring FrameworkServlet 'springMvc'
 

14-Oct-2016 13:03:46.537 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log 1 Spring WebApplicationInitializers detected on classpath
14-Oct-2016 13:03:48.005 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log Installing JUL to SLF4J bridge
14-Oct-2016 13:04:03.332 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: conf reload check disabled
14-Oct-2016 13:04:03.332 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: status display disabled
14-Oct-2016 13:04:03.434 INFO [localhost-startStop-1] org.apache.catalina.core.ApplicationContext.log org.tuckey.web.filters.urlrewrite.UrlRewriteFilter INFO: loaded (conf ok)
14-Oct-2016 13:04:03.898 INFO [spring-startup] org.apache.catalina.core.ApplicationContext.log Initializing Spring FrameworkServlet 'springMvc'

 

In the catalina out log it starts with no errors:

14-Oct-2016 13:03:25.555 INFO [main] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-7990"]
14-Oct-2016 13:03:25.556 INFO [main] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-7990"]
14-Oct-2016 13:03:30.000 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlValidation' to 'false' did not find a matching property.
14-Oct-2016 13:03:30.002 WARNING [main] org.apache.tomcat.util.digester.SetPropertiesRule.begin [SetPropertiesRule]{Server/Service/Engine/Host} Setting property 'xmlNamespaceAware' to 'false' did not find a matching property.
14-Oct-2016 13:03:30.070 INFO [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent The APR based Apache Tomcat Native library which allows optimal performance in production environments was not found on the java.library.path: /opt/atlassian/bitbucket/bitbucket_current/lib/native:/var/bitbucket-home/lib/native
14-Oct-2016 13:03:30.392 INFO [main] org.apache.coyote.AbstractProtocol.init Initializing ProtocolHandler ["http-nio-443"]
14-Oct-2016 13:03:31.100 INFO [main] org.apache.tomcat.util.net.NioSelectorPool.getSharedSelector Using a shared selector for servlet write/read
14-Oct-2016 13:03:31.105 INFO [main] org.apache.catalina.startup.Catalina.load Initialization processed in 1825 ms
14-Oct-2016 13:03:31.147 INFO [main] org.apache.catalina.core.StandardService.startInternal Starting service Catalina
14-Oct-2016 13:03:31.148 INFO [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet Engine: Apache Tomcat/8.0.36
14-Oct-2016 13:03:46.494 INFO [localhost-startStop-1] 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.
14-Oct-2016 13:04:03.017 INFO [localhost-startStop-1] org.apache.catalina.util.SessionIdGeneratorBase.createSecureRandom Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [14,824] milliseconds.
14-Oct-2016 13:04:03.660 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-443"]
14-Oct-2016 13:04:03.672 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 32566 ms

 

Database connection is ok, checked all paths, all permissions are set correctly including folder/file ownerships.

5 answers

This widget could not be displayed.

I have exactly this issue. With no clues in the log I am flummoxed.

This widget could not be displayed.

The error probably isnt a tomcat error, but an application error, whose logs go to another directory.

there are log files in your application directory AND your data directory, try to tail -f them all while starting the server and you might be given a more precise error.

 

This widget could not be displayed.

Yes, thanks so much! I was missing that there were logs in the BITBUCKET_HOME dir as well. A bit confusing, but once you know smile

This widget could not be displayed.

For us, it was a permission issue. Bitbucket could not write the logs. We had to change the owner of the data directory recursively with chown -R <user> <bitbucket-data-dir>.

This widget could not be displayed.

For me it was an issue with "Could not acquire change log lock.  Currently locked by ...", clearing the entries in DATABASECHANGELOGLOCK as indicated at https://confluence.atlassian.com/bitbucketserverkb/bitbucket-server-does-not-start-could-not-acquire-change-log-lock-779171307.html seems to have fixed the issue, at least I have a working WebUI. The server had crashed this morning for some unknown reason, and it seems to have let that entry in the DB (which is strange, as during normal operation it doesn't look like the entries aren't set). Maybe it crashed again during a new startup attempt, hard to tell.

Ran into this today. Turns out our database server data volume was full. Thanks to Daniel Faust for leading me to that.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

1,344 views 8 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you