-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Admin terminated by SIGABRT - Can't DROP INDEX PRIMARY
#3637
Comments
@karolszklarski would you be able to upgrade your MariaDB instance to the latest and try again? We aren't testing with Maria and also can't replicate this on MySQL 8. The Pomelo library that's used to perform these migrations reported such an issue but it was resolved ~3 years ago and we are suspecting that this has something to do with Maria installations. |
I upgraded to the latest available release in debian "testing" repository Isn't it the same issue as #3635 ? |
Yes, same issue most likely even though the error messages for the migration aren't included. I see you're still on Maria 10.x -- would you be willing to try using 11.x, even though it's not LTS? Or MySQL 8? |
I have upgraded to Maria 11.0, same issue persists. |
@karolszklarski can you pull the latest from |
I'm running a MariaDB backend also. Seeing this exact issue with the latest Docker image |
Same exact issue using 10.11.2-MariaDB backend. Had to revert to 2024.1.0-beta. |
|
That's not what I'm seeing. If I run bitwarden/self-host:beta or specifically 2024.1.1-beta I get the error.
I can run 2024.1.0-beta without any issues. |
That error may be due to something else? There are admin logs that would reveal more. |
Here is the entry from the admin log when running 2024.1.1-beta
|
My docker file.. `version: "3.8" services: |
#3651 (comment) may be what you need. |
Ok thanks @withinfocus! that worked. |
I confirm, it works :)
|
Steps To Reproduce
Install bitwarden image and standalone mariadb database (a service, not a docker image).
bitwarden/self-host b11825cadef4 (old dev) works fine
bitwarden/self-host 74ccd545df9c (current dev) and e1a1833fcc06 (current beta) - admin module enters a crash loop.
gitHash cf4d8a4 is working, ea162d5 is not
Expected Result
Bitwarden should start normally.
Actual Result
Admin enters a crash loop
Admin logs
Screenshots or Videos
No response
Additional Context
docker image tag bitwarden/self-host:beta bitwarden/self-host:prod
docker-compose.yml
settings.env
Githash Version
919d759-dirty
Environment Details
Database Image
mysql Ver 15.1 Distrib 10.5.21-MariaDB, for debian-linux-gnueabihf (armv7l) using EditLine wrapper
Issue-Link
#2480
Issue Tracking Info
The text was updated successfully, but these errors were encountered: