- UNRAID SONARR DOCKER UPDATE UPDATE
- UNRAID SONARR DOCKER UPDATE PATCH
- UNRAID SONARR DOCKER UPDATE SERIES
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.
UNRAID SONARR DOCKER UPDATE SERIES
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.
Thank you for answering, but that was me even f.g up the replace when I copied in the .SQLiteException (0x80004005): database disk image is malformed From the ports you provided there are 6's in front of some of your ports. If you click on the sonarr icon, click on it and go to edit settings, what is the ports for sonarr and what is the puid and pgid? 401 means you are not authorized, as Im sure you are aware. and requesting webUI from Unraid I get this line in the log: Auth: Auth-Unauthorized ip url ' I have to admit that routing inside Unraid still is a little mysterious for me and I don't quite understand what I'm doing :-$ I can reach the logfiles and have shell access to the dockers.Ĭhecking the logfiles for sonarr I see I'm running Version 3. The dockers starts fine, there are no general Error what I can see. It must be something basic that I overlooked and/or don't understand when so much breaks at the same time 😞 So, it's not only binhex-sonarr, but I had to start somewhere. Nextcloud, plex, tautulli and ombi are still working which all have the same basic setup as the binex dockers running through swag (where I set all x.nf in appdata\swag\nginx\proxy-confs to LAN IP). I get a 401 from LAN, and from WAN I get the browser log on messege for the services, but my usr/passwd is not accepted. So my problem started when, and I have a hard time understanding that it would be because, I changed the log level on sonarr, radarr and lidarr to 'debug' (had som problem with lidarr and was looking for clues), restarted the containers and now I can't get into the webUI to any binhex dockers (except binhex-plexpasshost).
UNRAID SONARR DOCKER UPDATE UPDATE
I had SWAG setup to use my cloudflare subdomains running with DNS update so the only NAT I have configured is 443 (and the one for PLEX). until now - everything starting with binhex broke 😞īinhex-delugevpn - bridge. My first Unraid server have been online for a couple of weeks now and everything have been pretty smooth sailing so far even if I'm a total noob at using anything of the SW listed here under. It's bitten me twice now (other one was delugevpn and the iptables changes, which I had to revert).
UNRAID SONARR DOCKER UPDATE PATCH
just patch releases), I'll turn off auto-updates for now in Unraid. Guess I caught this same issue during the 'grey' area between 'push to release' and end clients seeing the :latest update today and then being prompted for the update.Īnd now, UI parity between radarr and sonarr! Cheers for the work, and for your contributions to the community!Įdit - that said, maybe with the feature releases going on in the containers now (vs. I'm sure I would have been fixed tonight after my next nightly update of dockers and another update check. So all you need to do is go to unraid webui/docker/click on 'check for updates' then click on 'update all', you do not need to manually delete containers or images, this is all managed for you via the unraid web ui. There was an update, but due to the switch to v3 from v2 it broke things, this has now been fixed and the 'latest' tagged image is fully working.
0 kommentar(er)
