Rick_Sanchez

What if you delete and reinstall the image? Does that work?

What do your template settings look like?

Can you uninstall / reinstall the plex app on the shield?

I'm curious - do you have an adblocker turned on? I would start by turning that off. Alternatively, what if you setup a "watch" folder and just drop the torrent files in there? What is your setup and workflow like?

If you are using the docker container, it should automatically have WebUI enabled (you don't need to check the box). What happens when enter the IP and Port into Organizr?

Can you use the automatic template to create your plex docker container?

What is at 92 on your network? It sounds like something is requesting from that address - I'd say look at see if anything is mapped to that IP. Also I think you are right about the SSD, swap it out and see if that makes any improvement.

Interesting - any changes? Are the higher profile getting deleted or is it still persisting in Deluge?

I forgot to ask also - are you using the 'label' plugin? And what is your label in Sonarr in your Indexer settings?

Here is the website discussing the login options: https://hub.shinobi.video/articles/view/yX5mMukjGToZ1HM This user is an administrative user. This user does not have cameras to manage nor can it see any cameras. Its purpose is to manage Admin accounts settings and limitations, view system logs, and manage system configuration. The Superuser page can be accessed at http://xxx.xxx.xxx.xxx/super. The Login button will become Red to signify that you are at the correct gate for Superuser access. The login to use would be found in the super.json file located in the Shinobi installation directory. By default this is /home/Shinobi. The default login is as below. Username : [email protected] Password : admin

Wondering if anyone can help. I tried the hotfix as above, and the docker container logs show shinobi as ready. I go to the landing page, and my username/password are not accepted. I've tried a combination of the default user/pass, the docker container user/pass. None of these seem to work and the logs don't show anything. Any thoughts?

Is the file still seeding after it is moved, or is it in a paused state? You could still turn down the Share Ratio, Time Ratio, and Time to as close to zero while testing. It could be a permissions issue. Do the sonarr logs point to anything?

Thanks for sending those. I'd say try these changes and see if you have success: Change your download folder directory. Right now, your completed downloads are 'upstream' of your downloads in progress. I'm not sure if you HAVE to do this, but it might be worth a try. Create a /Downloads/complete directory and keep your current /Downloads/incomplete. Check the box for 'Share Ratio', then keep the bubble checked for 'Pause torrent.' Make the share ratio as low or high as you'd like. Maybe turn it down as low as you can while testing. Also, your downloads may not have been removed because they are set to seed for high share/time ratios. Decrease all the numbers for 'Seeding Rotation' while you are testing, then bump them back up to whatever you'd like.

You can make the assignment permanent with these instructions: http://hintshop.ludvig.co.nz/show/persistent-names-usb-serial-devices/

I've run through the steps here and am having some issues, wondering if anyone can spot a problem. I have /boot/config/rules.d/99-usb-rules.rules with the file SUBSYSTEM=="tty", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="1234", ATTRS{serial}=="myserial1", SYMLINK+="zigbee" SUBSYSTEM=="tty", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="1234", ATTRS{serial}=="myserial2, SYMLINK+="zwave" I have the UserScripts addon set to start 'At First Array Start Only' #!/bin/bash # add this to UserSctipt - StartUp at first Array start # Start the Management Utility /usr/local/sbin/emhttp & # copy persistent script from usb drive to drive at startup cp /boot/config/rules.d/99-usb-rules.rules /etc/udev/rules.d/ chmod 644 /etc/udev/rules.d/99-usb-rules.rules # udav has likely run before the copy completes so udev needs its rules refreshed udevadm control --reload-rules # a reset of the device is needed so the rules just copied can take hold udevadm trigger --attr-match=subsystem=tty Please note -- I added both the Start Management Utility and Reload rules parameters. Not sure if I require both. Script output at start of array: Script Starting Jan 09, 2021 06:33.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/99-usb-rules/log.txt emhttpd is already started Script Finished Jan 09, 2021 06:33.01 Full logs for this script are available at /tmp/user.scripts/tmpScripts/99-usb-rules/log.txt On reboot of my system and start of array: there are no USB devices listed in /dev/ - they are usually listed as /dev/ttyUSB0 and /dev/ttyACM0. Unplugging and plugging back the USB devices gets them recognized. the devices ARE recognized with lsusb in terminal BEFORE unplugging and plugging back in

@yanksno1 Can you also post screenshots of Deluge - Downloads, Queue? So far everything looks ok as far as settings. In your syslog, there are Disk Read errors for Disk 1. I'm not sure if this is of consequence, but that drive may be having issues. I would do research on this forum how to repair/rebuild/replace that drive if necessary.

Try setting the torrent to a paused state when it finished in the download client (deluge or qbittorrent) as opposed to having the download client delete it. Sonarr should then move the file and remove it from the client. Try restarting both containers after changing the settings. Let us know if you still have an issue and if so send us some screenshots of your settings.

I’m going to try and sudo nano the crontab.txt and see if that fixes the /bin/ash error I’m getting. I just read the comments above. Update: I've tried using the unraid terminal to nano the file and save it, and I've tried running the borgmatic container as an admin, but i'm still getting the crond: USER root pid 8 cmd PATH=$PATH:/usr/bin /usr/bin/borgmatic prune create -v 1 --stats 2>&1 /bin/ash: redir error Anyone have tips on how to fix this? Does the file need to be accessible to the 'root' user of unraid? The Fix: Same as above. Copy contents of crontab.txt move current crontab.txt file mv /path/to/crontab.txt /path/to/crontab.txt.old ssh into unraid, or, use the unraid terminal nano /path/to/crontab.txt Paste contents of crontab.txt Restart borg container

Hey @Greygoose - I setup my crontab.txt as follows, which is found in /appdata/borgmatic/config/ (note, this is the exact file - I have not changed any PATH directories) 0 1 * * * PATH=$PATH:/usr/bin /usr/bin/borgmatic prune create -v 1 --stats 2>&1 0 6 * * 3 PATH=$PATH:/usr/bin /usr/bin/borgmatic check -v 1 2>&1 The docker log output: crond: USER root pid 8 cmd PATH=$PATH:/usr/bin /usr/bin/borgmatic prune create -v 1 --stats 2>&1 /bin/ash: redir error I thought it may be a permissions issue, but the txt file is set as -rw-rw-rw-. I did find a post where someone put this in their crontab, but i'd prefer to use the proper method if possible: 0 6 * * * borg create -v --stats --compression lz4 /backup_repository::$(date +'%Y-%m-%d') /backup_sources

@Greygoose - Thank you for the push in the right direction. I'm testing my config file now after getting into a small fight with YAML syntax. the 'borgmatic' function has output 'starting a backup' - so I'm hopeful it's working. I'll check back if it's not working as intended. Thank you!!!

I'm hoping someone can help clarify the config.yaml and crontab.txt options that I've placed in my /appdata/borgmatic/config folder. I've created my own version of config.yaml based on the master configuration reference. Now I'm stuck on the crontab.txt. 0 1 * * * PATH=$PATH:/usr/bin /usr/bin/borgmatic --stats -v 0 2>&1 What is /usr/bin? Do I need to change '/usr/bin' to '/appdata/borgmatic' ? Also, will the borgmatic docker container automatically run the crontab itself? I should also clarify, I don't have a backup .sh script, just the config.yaml file. I'm hoping the cronjob will run this file. Thank you for your help!