Startup post upgrade of stash from 1.1.0 -> 1.2.2 posts many sql errors resulting in the following when browsing the web app:
A fatal error has occurred
The following problem occurred which prevents Atlassian Stash from starting correctly:
The Spring WebApplicationContext could not be started
Tried one of the sql statements with the root account, so doesn't appear to be a permissions issue:
mysql> SQL ALTER TABLE `stashdb`.`cs_repo_membership` DROP FOREIGN KEY `fk_cs_repo_membership_changeset`; ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SQL ALTER TABLE `stashdb`.`cs_repo_membership` DROP FOREIGN KEY `fk_cs_repo_memb' at line 1
MySQL version: mysql Ver 14.14 Distrib 5.5.24, for debian-linux-gnu (x86_64) using readline 6.2
Mysql Client: mysql-connector-java-5.1.21-bin.jar
jdbc.url=jdbc:mysql://localhost:3306/stashdb?useUnicode=true&characterEncoding=utf8&sessionVariables=storage_engine=InnoDB jdbc.user= jdbc.password= jdbc.driver=com.mysql.jdbc.Driver
Stash 1.1.0 still working, rolled back and can retry upgrade.
The solution to this is now available in the form of Stash release 1.2.3.
It worked a treat.
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot