You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The correct credentials are provided as environment values.
Every now and then, Litestream seemingly just gives up on replication, with no log output. As far as I can tell, this happens after repeated database is locked errors.
If I then call systemctl stop litestream or systemctl restart litestream, the SIGTERM sent by systemd suddenly seems to "wake up" litestream and it races to catch on on WAL uploads before being killed.
Usually, it can't catch up before systemd force-kills it. Subsequent starts of the litestream service result in it complaining about a WAL header mismatch and force generating a snapshot, before continuing with WAL uploads until it gets stuck again.
I'm using litestream with a systemd service (on NixOS
The systemd unit file is:
I'm replicating to Cloudflare R2 using the S3 type as follows:
The correct credentials are provided as environment values.
Every now and then, Litestream seemingly just gives up on replication, with no log output. As far as I can tell, this happens after repeated
database is locked
errors.If I then call
systemctl stop litestream
orsystemctl restart litestream
, theSIGTERM
sent by systemd suddenly seems to "wake up" litestream and it races to catch on on WAL uploads before being killed.Usually, it can't catch up before systemd force-kills it. Subsequent starts of the litestream service result in it complaining about a WAL header mismatch and force generating a snapshot, before continuing with WAL uploads until it gets stuck again.
This is a fairly large database (~60GB), with
busy_timeout = 30000
andsynchronous=NORMAL
The text was updated successfully, but these errors were encountered: