Closed senshinya closed 3 months ago
I have also noted that. It appears to occur when using the Riven UI to update the scrapers. Once the scrapers settings are saved, it appears to cause the backend to crash. I'm not sure if this is an issue related to the current release of the riven frontend - v0.2.5 - or something else... I may consider adding a process monitor to restart the processes if they crash; otherwise, try restarting the container to see if the 500 error is resolved.
Jul 26, 2024 13:31:10 - INFO - Riven_backend: | š¾ API | main.dispatch - GET /settings/load - 200 - 1.94s
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: TypeError: fetch failed
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: at node:internal/deps/undici/undici:12500:13
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: at process.processTicksAndRejections (node:internal/process/task_queues:95:5) {
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: [cause]: Error: connect ECONNREFUSED 127.0.0.1:8080
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1605:16) {
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: errno: -111,
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: code: 'ECONNREFUSED',
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: syscall: 'connect',
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: address: '127.0.0.1',
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: port: 8080
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: }
Jul 26, 2024 13:31:11 - INFO - Riven_frontend: }
Jul 26, 2024 13:31:26 - ERROR - The Riven backend process is not running.
I tried the "raw" method to deploy the stack. It seems when settings have some errors or incomplete , the onboard setting page function normally. But with correct complete settings or finish the onboard settings, 500 error occurred
Manually changing the Riven settings.json to include the below appears to resolve the errors:
},
"database": {
"host": "sqlite:////riven/backend/data/media.db"
}
}
DMB is supposed to be setting that automatically, but it appears to be a bug...
Hopefully, this is resolved with Version [3.0.0]. If not, you can reopen this issue.
Great, it finally works! Though every time starting docker container needs to init poetry environment, really takes a long time
Describe the bug
After initing, access riven dashboard gets 500 Internal Error
Docker Compose
Logs
It seems backend get the request:
main.dispatch - GET /services - 200 - 0.00s
, but somehow frontend timeout