Not sure why it does not work with one specific database

[Zottelchen]

I am having an issue with Litestream. I've setup multiple DBs to stream to B2, but the paperless database just does not work. No error message, no nothing. No issues with the other databases. What is happening?

access-key-id: <removed>
secret-access-key: <removed>

dbs:
  - path: /var/lib/docker/volumes/paperlessngx/_data/db.sqlite3  # not working
    replicas:
      - type: s3
        bucket: Litestream-NUC1
        path: paperless
        endpoint: s3.eu-central-003.backblazeb2.com
        force-path-style: true

  - path: /var/lib/docker/volumes/actualbudget/_data/server-files/account.sqlite # working
    replicas:
      - type: s3
        bucket: Litestream-NUC1
        path: actual/server-files
        endpoint: s3.eu-central-003.backblazeb2.com
        force-path-style: true

Oct 12 15:00:19 nuc1 litestream[48627]: litestream v0.3.9
Oct 12 15:00:19 nuc1 litestream[48627]: initialized db: /var/lib/docker/volumes/paperlessngx/_data/db.sqlite3
Oct 12 15:00:19 nuc1 litestream[48627]: replicating to: name="s3" type="s3" bucket="Litestream-NUC1" path="paperless" region="" endpoint="s3.eu-central-003.backblazeb2.com" sync-interval=1s
Oct 12 15:00:19 nuc1 litestream[48627]: initialized db: /var/lib/docker/volumes/actualbudget_data/_data/server-files/account.sqlite
Oct 12 15:00:19 nuc1 litestream[48627]: replicating to: name="s3" type="s3" bucket="Litestream-NUC1" path="actual/server-files" region="" endpoint="s3.eu-central-003.backblazeb2.com" sync-interval=1s
Oct 12 15:00:20 nuc1 litestream[48627]: /var/lib/docker/volumes/actualbudget/_data/server-files/account.sqlite: sync: new generation "ea090b23aba4a8f2", no generation exists
Oct 12 15:00:21 nuc1 litestream[48627]: /var/lib/docker/volumes/actualbudget/_data/server-files/account.sqlite(s3): snapshot written ea090b23aba4a8f2/00000000

[hifi]

Usually it means the database doesn't exist if Litestream does nothing. I'd execute a shell in container and check that the database file is in the exact path you expect it to be in the configuration file.