#tdarr GUI Not Loading

29 messages · Page 1 of 1 (latest)

upper vale
#

Hey there. I got tdarr setup and working on my TV library last night to start scanning all my tv directory, it was working fine last night. This evening the web-page is not avail, from proxmox it appears it is fully operational (CPU is pegged, same as ram and swap). Is there a way to either force pause / kill the node , or re-start GUI? Problem persists after rebooting both the container and the node itself. At a bit of a loss right now.

upbeat lintel
#

ss -tulpn to see what ports are open/listening

#

also check if services are running

#

systemctl status tdarr-server

#

systemctl status tdarr-node

upper vale
#

Ill give that a check this evening and post back

upper vale
#

Looks like node is going but server is not responsive. server shows as running thoguh it seems, or I am mis-understanding it

#

re ran the second command, loks like its connecting now

upbeat lintel
#

is your disk full?

upper vale
#

Bootdisk? Its getting there, about 90%

upbeat lintel
#

db service report SQLITE_FULL. its usually like that when disk is full

upper vale
#

Makes sense ... just doubled the size up and alls back to normal.

#

THanks!

upbeat lintel
#

np

upper vale
#

If i am having some issues that dont seem to occur outside of a proxmox environment, is this a place I can ask it?

upbeat lintel
#

what issues?

upper vale
#

Having an Error 13 and 18 when trying to copy back over the old file ... the lxc CLI can both create, and delete files / folders in the library ... been pulling my hair out today trying to figure this out ... lxc is working great for the encode part just not the file moving part lol

upper vale
#

@upbeat lintel hate to reopen this ... but having an issue with GUI not loading again ... Came home as it was going thru the library still GUI not responsive. See next couple messages for outputs from requested commands originally sent last week.

#

Both services seem to be loaded, but not communicating ... Have tried a few reboots of both the container and host, as well as running the update command on the host to see if there was anything there.

#

ofcourse ... the last time i rebooted it worked 😐 JFC ..

upbeat lintel
#

that really isnt scripts issue

#

just reboot untill they match up

#

the script runs the updated before server starts

#

so technicaly they should be always matching

#

i've seen reports of people it sometimes is slow on updating the node service, so just keep rebooting until it does