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

Auto upgrade failing with - Error: file is not a database in "PRAGMA journal_mode = WAL"... #5643

Closed
just-my-opinion opened this issue Nov 15, 2021 · 9 comments

Comments

@just-my-opinion
Copy link

  • [ X] I have searched open and closed issues for duplicates
  • [X ] I am using Signal-Desktop as provided by the Signal team, not a 3rd-party package.

Bug Description

When allowing Signal (win) to upgrade to latest release, install failed with the following message:
Error: file is not a database in "PRAGMA journal_mode = WAL"
statement aborts at 1: [PRAGMA user_version;] file is not a database
at Worker. ([REDACTED]\ts\sql\main.js:44:34)
at Worker.emit (events.js:315:20)
at MessagePort. (internal/worker.js:207:53)
at MessagePort.[nodejs.internal.kHybridDispatch] (internal/event_target.js:354:41)
at MessagePort.exports.emitMessage (internal/per_context/messageport.js:18:26)

Steps to Reproduce

  1. uninstalled Signal completely
  2. downloaded the most recent version of Signal (win) from https://signal.org/download/ signal-desktop-win-5.23.1.exe
  3. attempted to install that release
  4. It failed with the identical error and error message

Actual Result:

Expected Result:

Screenshots

Platform Info

Signal Version:

Operating System:

Linked Device Version:

Link to Debug Log

@just-my-opinion
Copy link
Author

Hey, is no one else experiencing this issue? I really could use some assistance...

@just-my-opinion just-my-opinion changed the title Unhandled Promise Rejection - Error: file is not a database in "PRAGMA journal_mode = WAL"... Auto upgrade failing with - Error: file is not a database in "PRAGMA journal_mode = WAL"... Nov 17, 2021
@hiqua
Copy link
Contributor

hiqua commented Nov 17, 2021

@indutny-signal
Copy link
Contributor

Sorry for a delay on our end. We are aware of db corruption issues happening to some users and are looking into the root cause of this, but unfortunately we don't have any suggestions other than what @hiqua brought up above.

@indutny-signal
Copy link
Contributor

indutny-signal commented Nov 17, 2021

Duplicate of #5467

@indutny-signal indutny-signal marked this as a duplicate of #5467 Nov 17, 2021
@indutny-signal
Copy link
Contributor

@just-my-opinion could you confirm that Signal offered you to erase your database when you saw that error message, please?

@just-my-opinion
Copy link
Author

just-my-opinion commented Nov 17, 2021 via email

@indutny-signal
Copy link
Contributor

Oh, this sounds bad! I think I understand why this has happened. We'll see if we can improve here!

@just-my-opinion
Copy link
Author

just-my-opinion commented Nov 17, 2021 via email

@indutny-signal
Copy link
Contributor

Sorry for the confusion, I meant that it is bad that it didn't offer you to erase the faulty data and relink and you had to do it yourself!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants