We are planning on upgrading our bitbucket server from 5.10.0 to 6.3.2.
Performing some tests, steping back from 6.3.2 to 5.10 an issue came up: SpringMVC dispatcher could not be started and upgrading again to 6.3.2 does not show any error. Is this because a schema change on the database after upgrading to 6.3.2 which make imposible step back without a db bu?
I guess there are changes on the db schema, just for clarifying heh
thanks!
Adri
Hi @Adrian Sanchez
Please review the following Atlassian document once and try to troubleshoot the issue.
Yoga
which are the right permissions for the folders/files inside /var/atlassian/application-data/bitbucket?
What is weird is that upgrading again from 5.10 to 6.3.2 it starts perfectly, which means
is not the root cause.
here you are the permissions inside /var/atlassian/application-data/bitbucke:
drwxr-xr-x 3 atlbitbucket atlbitbucket 23 Aug 26 13:23 ..
drwxr-x--- 3 atlbitbucket atlbitbucket 25 Aug 26 13:24 plugins
drwxr-x--- 3 atlbitbucket atlbitbucket 20 Aug 26 13:24 lib
drwxr-x--- 2 atlbitbucket atlbitbucket 6 Aug 26 13:24 export
-rw-r----- 1 atlbitbucket atlbitbucket 62 Aug 26 13:35 .version
-rw-r----- 1 atlbitbucket atlbitbucket 67 Aug 26 13:35 home.properties
drwxr-x--- 4 atlbitbucket atlbitbucket 42 Aug 26 13:36 bin
-rw-r--r-- 1 atlbitbucket atlbitbucket 280 Aug 26 13:47 .bashrc
drwxr-x--- 3 atlbitbucket atlbitbucket 243 Aug 26 13:47 log
drwxr-x--- 11 atlbitbucket atlbitbucket 310 Aug 26 13:47 tmp
drwxr-xr-x 11 atlbitbucket atlbitbucket 196 Aug 26 13:47 .
-rw-r----- 1 atlbitbucket atlbitbucket 32 Aug 26 13:47 .lock
drwxr-xr-x 9 atlbitbucket atlbitbucket 4096 Aug 26 13:48 shared
drwxr-x--- 6 atlbitbucket atlbitbucket 67 Aug 26 13:48 caches
drwxr-x--- 2 atlbitbucket atlbitbucket 309 Aug 26 13:48 analytics-logs
are they right?
Thanks in advance!
Adri
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.