sqlite3.OperationalError: database is locked error

Hi there,

I’m attempting to run this in portainer and getting the following error whenever starting the container:

Outdated jbos table, cleaning up and recreating
Traceback (most recent call last):
  File "./youtube-dl-server.py", line 114, in <module>
    JobsDB.init_db()
  File "/usr/src/app/ydl_server/logdb.py", line 72, in init_db
    cursor.execute("CREATE TABLE if not exists jobs \
sqlite3.OperationalError: database is locked

Any ideas?

[damntourists]

Ok, that seems to have worked! This is what I wound up using:

---
version: "2.1"
services:
  youtube-dl:
    image: "nbr23/youtube-dl-server:latest"
    container_name: youtube-dl
    environment:
      - YDL_CONFIG_PATH=/usr/src/app/config.yml
    volumes:
      - /mnt/nas/sync/youtube-dl:/youtube-dl
      - /mnt/nas/projects/homelab/configurations/youtube-dl-server/config.yml:/usr/src/app/config.yml:ro
    ports:
      - 8888:8080
    restart: always

I added in the environment variable because it appears it was defaulting to /app_config/config.yml.

Thanks again for your help! It’s working perfectly now!

[damntourists]

Hi there, sorry to revive a previously closed ticket – I think I’ve figured out why this was causing errors and figured I’d let you know in case you weren’t aware.

I had mounted a volume pointing to my network SMB 2 share which is mounted on ubuntu using cifs. It appears that sqlite does not behave well using NFS mounts, which is why I have been encountering this error.

2.1. Filesystems with broken or missing lock implementations

SQLite depends on the underlying filesystem to do locking as the documentation says it will. But some filesystems contain bugs in their locking logic such that the locks do not always behave as advertised. This is especially true of network filesystems and NFS in particular. If SQLite is used on a filesystem where the locking primitives contain bugs, and if two or more threads or processes try to access the same database at the same time, then database corruption might result.

source: https://sqlite.org/howtocorrupt.html

Is it possible to write the downloads out to a different directory instead of keeping them along side the db files?