Error: SqliteError: file is not a database

[samuela]

• I have searched open and closed issues for duplicates

#3869
#3625
#5467
#4513

---

Bug Description

I just opened to re-opened Signal today -- possibly after a Signal upgrade, I don't recall -- and came across this nasty error message: "Error: SqliteError: file is not a database".

Steps to Reproduce

1. Upgrade signal(?) Not exactly clear what causes this.
2. Attempt to open Signal.

Actual Result:

On a separate note, it's also worth noting that the "Copy error and quit" button does not work: it quits but does not copy the error to the clipboard. I think a much more robust solution here would be to make the error message text selectable, enabling the user to copy to the clipboard manually if they need to.

Expected Result:

Signal to open without issue.

Screenshots

Platform Info

Signal Version: 5.14.0

Operating System: Ubuntu 20.04.2 LTS, with signal-desktop installed via Nix.

Linked Device Version: n/a

Link to Debug Log

n/a

[ddshore]

You linked to my issue and it's the exact same problem. I used signaltop to check if the messages were exportable and whether the db wasn't corrupted, and it exported the messages. You might want to try that too in order to validate it, but this is a signal bug.

[samuela]

@ddshore I ended up just deleting the database and starting fresh, but I'll def keep that in mind for the future! It would be great to have a workaround for when this happens again...

[ITaluone]

I had the same problem: Mine was caused by not quitting Signal properly (Settings => minimize to taskbar (Signal in background) => shutdown PC). The next day this error occures and only was solvable with deleting DB and start from scratch.

[samuela]

I had the same problem: Mine was caused by not quitting Signal properly (Settings => minimize to taskbar (Signal in background) => shutdown PC). The next day this error occures and only was solvable with deleting DB and start from scratch.

That sounds like a totally reasonable way to shut down signal imho!

[scottnonnenberg-signal]

I'm sorry this happened to all of you! We have merged a change in the latest builds which may help prevent this in the future.

Going forward, please provide debug logs so we have more information to try to track down what went wrong.

I'm going to close this as a duplicate of the bugs you yourself linked to.

[samuela]

Going forward, please provide debug logs so we have more information to try to track down what went wrong.

How do we find debug logs?

[scottnonnenberg-signal]

View -> Debug Log

[samuela]

I can't test it atm but I don't think that's possible if the application refuses to start with only a modal dialog.

[scottnonnenberg-signal]

You can get it directly from disk at ~/.config/Signal/logs or ~/Library/Application Support/Signal/logs

[tbvdm]

We have merged a change in the latest builds which may help prevent this in the future.

@scottnonnenberg-signal Could you say what that change is? Thanks.

[ddshore]

I'm sorry this happened to all of you! We have merged a change in the latest builds which may help prevent this in the future.

Is there a way to recover my history? I still have about 20 days to go before my devices becomes unlinked.

Going forward, please provide debug logs so we have more information to try to track down what went wrong.

The problem is that signal won't open (so I can't see the logs) and the log folders are empty. Is there a way to force the logs to generate?

[scottnonnenberg-signal]

@ddshore You can get logs from disk - see my comment above.

@tbvdm The change is to ensure we close the database connection on close of the app, all the time.

[ddshore]

You can get logs from disk - see my comment above.

I did try it, but as I mentioned above, those log folders are empty.

total 8.0K
6947710 -rw------- 1 dd dd 0 Aug 27 13:08 main.log
7020679 drwx------ 2 dd dd 4.0K Aug 27 13:08 .
7020667 drwx------ 20 dd dd 4.0K Aug 27 13:09 ..

Meanwhile, Is there anyway that I can reestablish my signal if my database is still readable while my devices are still linked?

[EvanHahn-Signal]

You may be able to take your config directory (~/.config/Signal for production Linux) and use it to power a new instance, but you may need to delete all of the app's data and relink. Apologies.