signal-cli icon indicating copy to clipboard operation
signal-cli copied to clipboard

[SQLITE_BUSY] The database file is locked error since signal-cli 0.13.0

Open Lukom opened this issue 5 months ago • 1 comments

I've started receiving [SQLITE_BUSY] The database file is locked error recently after update to signal-cli 0.13.0 and it fails on 0.13.1 as well. To reproduce just run this:

JAVA_HOME=/usr/local/Cellar/openjdk/21.0.2/libexec/openjdk.jdk/Contents/Home /Users/username/Downloads/signal-cli-0.13.1/bin/signal-cli -a +380631234567 --output json daemon --socket

and after couple of minutes it happens (there should be also some messages flying around for this to happen). It shows such error in output:

java.lang.RuntimeException: Failed read from session store
...
Caused by: org.sqlite.SQLiteException: [SQLITE_BUSY] The database file is locked (database is locked)
...

full output is here: https://gist.github.com/Lukom/71fbd2f643b32a12a253beee5b1b452a

It happens on my macbook and on Ubuntu 22 server as well, both openjdk-21. On Ubuntu server I have a lot of traffic inside signal and this error is triggered every 2 minutes. I'm sure I have enough space on devices, and also there are no any tricky manipulations with session database - everything was working fine before 0.13.0.

I've found similar closed issues: SQLITE_BUSY The database file is locked (database is locked) SQLite locks when messages are sent concurrently but suggested fix of adding --disable-send-log isn't helping.

Lukom avatar Mar 02 '24 22:03 Lukom