Skip to content
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

Database upgrade issue #792

Closed
qovert opened this issue Jun 24, 2020 · 1 comment
Closed

Database upgrade issue #792

qovert opened this issue Jun 24, 2020 · 1 comment

Comments

@qovert
Copy link

qovert commented Jun 24, 2020

Having an issue upgrading an onprem bitwarden host.

OS:
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic

Steps taken:
bitwarden.sh updateself
bitwarden.sh update

On advice from other issues, I waited and attempted a bitwarden.sh updatedb and received the same result:

Docker version 18.06.1-ce, build e68fc7a
docker-compose version 1.18.0, build 8dd22a9

Status: Image is up to date for bitwarden/setup:1.34.0

Migrating database.
Database is in script upgrade mode. Trying again (attempt #2)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #3)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #4)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #5)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #6)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #7)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #8)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #9)...
Migrating database.
Database is in script upgrade mode. Trying again (attempt #10)...
Migrating database.
Unhandled exception. System.Data.SqlClient.SqlException (0x80131904): Login failed for user 'sa'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 193
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.MigrateDatabase(Int32 attempt) in /home/appveyor/projects/server/util/Setup/Program.cs:line 190
at Bit.Setup.Program.Update() in /home/appveyor/projects/server/util/Setup/Program.cs:line 140
at Bit.Setup.Program.Main(String[] args) in /home/appveyor/projects/server/util/Setup/Program.cs:line 65
ClientConnectionId:cbe6f208-f2c2-424f-8e10-e04fe52cff6d
Error Number:18401,State:1,Class:14

Checking out the errorlog in the mssql container yielded this:

2020-06-24 20:12:22.78 Logon Error: 18401, Severity: 14, State: 1.
2020-06-24 20:12:22.78 Logon Login failed for user 'sa'. Reason: Server is in script upgrade mode. Only administrator can connect at this time.

@qovert
Copy link
Author

qovert commented Jun 24, 2020

I figured it out. There was a zombie process in the bitwarden-mssql container. Once that was taken care of, I:
./bitwarden.sh restart
./bitwarden.sh update
./bitwarden.sh updatedb

Migration was successful and the output of docker container ps became healthy. Thanks!

@qovert qovert closed this as completed Jun 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant