Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

18 Good

About Gog

  • Rank
    Advanced Member


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Better that then the other way! Good luck
  2. So appdata is only present on your cache, that's good and your mariaDB path is OK. And you are right, moving from a share (/mnt/user) directly to a disk is a bad idea. Always copy share to share or disk to disk. Have you tried installing MariaDB to a new appdata like /mnt/cache/appdata/mariadb2, verify that this works, stop the container, copy the content of the mariadb dir to the mariadb2 dir, pray a bit and start it back up? Without real backup, that's the only thing I can think of.
  3. What are your mappings for the mariaDB container? What do you use for your appdata directory? Is it possible that your dockers are configured to use only the cache content like /mnt/cache/appdata/... and that you have application data on the array and not on the cache like /mnt/user/appdata/...? Make sure your appdata is a cache-only share so that data in /mnt/cache/appdata never gets moved to the array and becomes unavailable for your containers.
  4. flip the Basic View/Advanced View togle top right in the docker config. It's configured in the webui field to use the variables declared in the form but instead of http://[IP]:[PORT:8080]/ you should be able to enter http://[IP]:9090/
  5. remove it and create a new one Sent from my SM-G930W8 using Tapatalk
  6. almost there. click on the Edit button for host port 3. Container port and host port BOTH need to be 9090
  7. As documented in the container's readme, the WEBUI_PORT variable needs to match the port setting and you can't remap the port so set 9090=9090 and set the variable WEBUI_PORT=9090
  8. There is a paragraph for that at the end of the readme: Due to issues with CSRF and port mapping, should you require to alter the port for the webui you need to change both sides of the -p 8080 switch AND set the WEBUI_PORT variable to the new port. For example, to set the port to 8090 you need to set -p 8090:8090 and -e WEBUI_PORT=8090
  9. I've seen a few discussions on that but no clean way of doing it. You could start the second sonarr from a backup of the first but you won't get new series added to the second sonarr...
  10. I think the remote path mapping is not done because there is nothing mapped to /home11/mihcox/files. You mapped /home11/mihcox/files/Completed but completed is not part of the path in your art of killing example. Can you try to rename /downloads/Torrents/Completed - SeedBox to /downloads/Torrents/Completed and change your remote path mapping to /home11/mihcox/files -> /downloads/Torrents/
  11. Looks like for some reason sonarr doesn't see your downloaded file. And yes, there is a difference. Say you have a file /mnt/cache/Downloads/1.txt, it also exists as /mnt/user/Downloads/1.txt BUT, /mnt/disk1/Downloads/1.txt, which is visible in the user path, will NOT be visible in the cache path. So once the mover script has run, the /mnt/cache path will not see those files.
  12. OK, I understand what you're trying to do now. Can you screenshot your sonarr's download client remote path settings and your sonarr docker container's path mapping?
  13. Whoa, context switch, I was probably wrong then. Thinking about it...
  14. Is the download still in sonarr's activity list? what if you hover on the image tag on the left of the download? Either way, the sonarr logs should have info on the processing of the completed download. Good, it was to double-check that from the container's point of vue the file exists for everyone.