![]() So far so good.Īfter this however, Sonarr does not pick up the file and add it to the TV share. The file is then shown as 'seeding' in Deluge. Deluge downloads the file and moves it from "Incomplete" to "Complete" in my main Downloads share. Sonarr is able to grab torrents and send them to Deluge to download just fine. Hi everyone! I am trying to troubleshoot an issue with Sonarr and Delugevpn. Any other ideas short of starting from scratch on my unraid configuration? No help on this? I've tried blowing away my entire docker/appdata, confirmed docker puts everything on the cache drive, and followed Space Invader's youtube videos exactly.same issues. Any ideas of what else I can try short of just blowing Sonarr away and starting over?Ģ0200524 Sonarr log with issues - truncated.txt 5.54 kB Looked at permissions for my /mnt/cache/Downloads files and folders, which were all set to 777 While attempting to resolve this I have confirmed/tried a few things:Ĭheck all my paths between SAB and Sonarr (both have exactly the same path set in docker, i.e., /data -> /mnt/cache/Downloads/)Įnsured all docker containers /config maps to /mnt/cache/appdata Sometimes Sonarr imports fine, sometimes I get the error and while the file is moved, Sonarr never recognizes this because of the database locked error. ![]() Hi all, seeing "database is locked" errors in SQLite for Sonarr on downloads. I'd like to minimize recreating my settings as much as possible.Įdit: I messed up something with my database trying some fixes and had to rebuild from scratch. Do you mean the appdata folder? Will the nzbdrone backup in the appdata folder help at all? I do have a few weeks of that. I'm trying to follow what you have written here to recreate but I don't see a /config anywhere. Unfortunately I have my appdata backups set to delete daily so restoring didn't solve the problem since it's been going on for a few days. It looks like I've got this same sqlite database corruption. To delete and start from scratch delete all files and folders in the host path for /config for this container, otherwise stop the container and restore from backup. If you go down the route of deleting the existing database then you will no doubt have to re-import all your tv series again and may loose some config as well, so just be prepared for this. You have sqlite database corruption, until this is fixed by either deleting the database and allowing it to re-create a blank database, or by restoring your config from a backup (recommended!) then you will continue to see issues. A custom network on the other hand provides service discovery, which allows to use the service or container name of a container within the same .SQLiteException (0x80004005): database disk image is malformed Note: while the default bridge network is easy to use, it lacks service discovery and as such requires the good old container linking for container to container commincation thru the default bridge network or bypassing the container network at all and access the target container using its published host port. ![]() What happens if you use this http url in a browser on your computer? In case you address the indexer-container by its ip, it is highly unlikely that AGH is responsible for the problem, as no dsn name resolution takes place.Īre the jacket/radarr running in a bridge network? If so, in the default bridge network or in a custom bridge network? Are those allowed in the syno firewall? A simple check is to fire up a terminal in one of the containers and use wget/curl to access the http url you had in your logs. you use inside a container to access the indexer-container and not a hostname/containername : The operation has timed out.: '(removed) -> : The operation has timed out.įWIW, the radarr/sonarr containers do have external connectivity (ex., Search). My radarr log, when setting up a new indexer gave this. Creating new jackett and radarr containers to test indexing using identical PGID/PUID).Refreshing the docker IP tables per Rusty's post in a previous thread I had a few months ago.Stopping Jellyfin (which also uses the Host network).Removing all AdguardHome container/image/DNS remnants (to the best of my recollection).Coincidence or not, this occurred when I was setting up a new AdGuardHome (AGH) instance.ĪGH was the first container I set up with Hosts network (as opposed to bridged), so my suspicions are that the use of Host broke my container inter-connectivity. My sonarr and radarr containers recently lost connection with other Docker containers (indexes, torrent package).
0 Comments
Leave a Reply. |