MTerracciano

Members
  • Posts

    6
  • Joined

  • Last visited

MTerracciano's Achievements

Noob

Noob (1/14)

0

Reputation

  1. I have a minimum set but that doesn't solve the underlying issue that the cache drive temperature isn't being monitored by the plugin even though it's listed as a drive that can be "excluded"
  2. 100% agree, but main point is auto fan speed isn't reading the cache drive temp so everything will continue to heat up inside the case, less than ideal situation
  3. I've been using the auto fan plugin for a while now and just set my drives to spin down, with all the main array drives spun down, except the cache drive, auto fan turns off the fans: "autofan: Highest disk temp is 0C, adjusting fan speed from: FULL (100% @ 1976rpm) to: OFF (0% @ 738rpm)" But the cache drive starts to get really hot, over 40degC, it is included in the auto fan plugin drives list but it seems like the cache temperature is ignored when the main mechanical drives are spun down. Any ideas? Update: With (1) drive spun up auto fan detects it's temperature but still ignores the cache drive: autofan: Highest disk temp is 32C, adjusting fan speed from: FULL (100% @ 1567rpm) to: OFF (0% @ 597rpm)
  4. How would I know the network I'd be connecting from if, let's say, I'm just trying to view download progress in the qbittorrent remote app on my phone while on a mobile network?
  5. Have never been able to make qbittorrent accessible externally from the web, works locally but not extrenally, all other dockers (Sonarr, Radarr, Tautulli) are all set up similarly and are fully accessible from outside of my network via dyndns and port forwarding at my router, has any else experienced/solved this? Thank you for your help!
  6. I'm attempting to use the Tatulli docker notification agent to run a script to pause parity check while someone is streaming. I've setup the notification agent in a similar way to the example in this link: https://github.com/uraid/qbittorrent_throttle And have created a script (ResumeParityCheck.sh below) to call a Parity Tuning Plugin CLI command and placed it in a few different folders but Tatulli throws up a permission error when I try to run the script from within the webGUI: "Tautulli Notifiers :: Failed to run script: [Errno 13] Permission denied: '/scripts/ResumeParityCheck.sh'" ResumeParityCheck.sh #!/bin/bash /usr/local/emhttp/webGui/scripts/parity_control resume Anyone have any idea how to successfully call a script that interacts with the main console from within a docker? Any help is appreciated!