500 Internal Server Error when adding new channel about tubesync HOT 4 CLOSED

Interesting, that error is caused by an OperationalError raised due to being unable to lock the SQLite database most likely. Try restarting the container. You can also start TubeSync with -e TUBESYNC_DEBUG=True which should enable Django debugging so you'll get a stack trace in the browser, but that'll just probably show the error raised by an add_task style function. But I'm pretty sure that's just an issue locking the SQLite database. Are you on an esoteric platform or did you access the SQLite DB some other way at all?

Also check your SQLite database is OK, you can just open it from your host OS with $ sqlite3 db.sqlite3 from your config dir then execute a pragma integrity_check; command.

from tubesync.

Thanks for the feedback.

I'm wondering if this is permissions related as my config is on an NFS share. Im a rookie with these permissions so I may move the config to a local drive to rule that out.

Im running docker on a mac mini.

from tubesync.

I think this was permissions related. Not sure why it was intermittent but I will re-open should the issue resurface.

from tubesync.

Just to follow up, yes, running an SQLite database on an NFS share is going to cause all sorts of lock issues with even a moderate write load. See "(5) Can multiple applications or multiple instances of the same application access a single database file at the same time?" on https://www.sqlite.org/faq.html

I would strongly suggest you move the config volume to the local machine you're running the container on to avoid this.

from tubesync.