Database is locked constantly with alpha 1.50

[mjefferys]

telly release with the issue:
telly, version 1.5.0 (branch: HEAD, revision: d56d292)
build user: root@873a25215547
build date: 20180916-03:58:34
go version: go1.10.3

Last working telly release (if known):
n/a

Operating environment (Docker/Windows/Linux/QNAP, etc.):
Linux Ubuntu 18.04

Description of problem:
Pretty much perfoming any action will result in the database locking for a long period of time and the UI appearing to be frozen.

Adding my m3u from eternal which has ~ 5k channels in. Locked the ui for about 10 minutes with no feedback as to where it was in the process of importing. Only realized when looking at the console.

Trying to create a lineup again with more than about 10 channels results in the database locking up, with the ui blocking and no feedback as to what's happening.

telly or docker log:

ERRO[2018-09-16T16:33:38+02:00] Error while serving request                   error="Error #01: database is locked\n" fields.time="2018-09-16T14:33:38Z" ipAddress= latency=5.004167606s method=GET path=/api/video_sources status=500 userAgent="Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36"

Additional information:
Appreciate the work being done on this, it's going to be baller when it works. Am on discord as @thomax if someone wants to ping me to debug this in real time

[robbiet480]

What version of SQLite are you on?

[mjefferys]

sqlite3 --version 3.22.0 2018-01-22 18:45:57 0c55d179733b46d8d0ba4d88e01a25e10677046ee3da1d5b1581e86726f2alt1

What ever has shipped with a default ubuntu 18.04

[mjefferys]

Seems this extends even to starting streams for me

ERRO[2018-09-16T22:41:03+02:00] Error when starting streaming error="database is locked" ERRO[2018-09-16T22:41:03+02:00] Error while serving request error="Error #01: database is locked\n" fields.time="2018-09-16T20:41:03Z" ipAddress=127.0.0.1 latency=5.008513423s method=GET path=/auto/v4 status=500 userAgent=Lavf/58.9.100

[htilly]

Same issue. Running latest docker with 1.5.
Adding M3U with ~7k.

[htilly]

Same issue. Running latest docker with 1.5.
Adding M3U with ~7k.

Replying to my own problem. I was missing a port when creating the container. This lead to database lock and a "really" slow app. When the port issue was solved everything worked as normal!