Jump to content

cinema-plug

Members
  • Posts

    4
  • Joined

  • Last visited

cinema-plug's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Fixed it. It was a permissions issue.
  2. I’ll have to look into that but I’d still much rather find out why mover tuner doesn’t seem to be running my start/stop scripts. I’ve verified that the scripts work when called manually in the console.
  3. I was attempting to follow the information I found here: https://www.reddit.com/r/unRAID/comments/10a1u6h/comment/j4200rb/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button The idea is that I've ignored the active downloads folder /mnt/user/data/torrents/, however, if qbittorrent remains active and continues downloading (and finishing downloads) then I'll have an edge case where mover starts, qbittorrent finishes a download and moves it from /mnt/user/data/torrents/movies to /mnt/user/data/media/movies (which is actively being moved). I'd prefer for qbit to be stopped, mover to be initiated, then once mover is finished qbit is started, and apps that interact with qbit to restart (ensuring they maintain a proper connection to qbit).
  4. Howdy, I've installed mover tuning and configured it with the following information: Disable Mover running on a schedule: No Only move at this threshold of used cache space: 10% Script to run before mover (No checks, always runs): /mnt/user/appdata/mover-tuning/stop_qbit.sh Script to run after mover (No checks, always runs): /mnt/user/appdata/mover-tuning/start_qbit.sh Move Now button follows plug-in filters: Yes The share currently has 197GB used of 1TB (19.7%, which is > 10%) Where stop_qbit.sh contains: #!/bin/bash docker stop qbittorrent-vpn Where start_qbit.sh contains: #!/bin/bash sleep 3 docker start qbittorrent-vpn sleep 90 docker restart radarr sleep 3 docker restart sonarr And finally, a screenshot of my docker containers: For some reason, whenever I manually initiate the mover it never stops qbittorrent-vpn. Am I misunderstanding a setting or where did I go wrong? Checking the system log I see the following output which indicates it's initiating the move with the appropriate settings, but still qbit doesn't shutdown. Dec 20 13:10:34 Cinema-Plug root: ionice -c 2 -n 0 nice -n 0 /usr/local/emhttp/plugins/ca.mover.tuning/age_mover start 0 0 0 "/mnt/user/appdata/mover-tuning/ignorelist.txt" ".part,.!qB" "/mnt/user/appdata/mover-tuning/stop_qbit.sh" "/mnt/user/appdata/mover-tuning/start_qbit.sh" '' '' '' '' 10
×
×
  • Create New...