-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed: Upgrade from 5.0.7 -> 5.1.2 on Synology Docker #549
Comments
testing_5.0.7_upgrade_to_5.1.2_mariadb.log Tested upgrading a blank new server from 5.0.7 to 5.1.2. This was successful though the first boot into 5.1.2 the database upgrade took longer than redmine was willing to wait. Note making sure to bring down the docker compose between upgrades is important I think. Could you post your before and after docker-compose? Also posting the full log is a lot more helpful than just a snippet. Make sure your making backups before doing these upgrades. |
Note there is a chance this is a old kernel issue, especially if this is run on a synology: sameersbn/docker-gitlab#2872 |
It looks like with_advisory_lock is a new dependency between 5.0.7 and 5.1.2, which is using the urandom call so the previous link is looking more likely
|
I can well imagine that it is due to the Docker version of this Synology Station (DSM 6.2). |
When I try to update my current 5.0.7 to 5.1.2, an error occurs during the migration of the database - plugins are not yet integrated in this step:
Migrating database. Please be patient, this could take a while...
rake aborted!
(Checking transaction isolation level... REPEATABLE-READ)
...
Bundler::GemRequireError: There was an error while trying to load the gem 'with_advisory_lock'. (Bundler::GemRequireError)
Gem Load Error is: failed to get urandom
The DB version used: 10.3.29-MariaDB (cannot be updated)
Is the cause in the database or somewhere else?
Thanks for the support, Carsten
The text was updated successfully, but these errors were encountered: