WexfordStyle

Did you do anything special to get this to work? I am having trouble adding the data source to Grafana. I am following the guide here: https://github.com/HStep20/Ultimate-Unraid-Dashboard-Guide Which details how to add the data source below: UnraidAPI Hit 'Add Data Source' and choose an 'JSON API' data type With the containers being on the same docker compose network, we can refer to them by container name in URLs. Top fields: URL - http://YOURSERVERIP:YOURUNRAIDAPIPORT/api/getServers Note: The default unraidapiport is 3005. If you did not edit the docker-compose.yml, set the port to 3005 When I do this, I am presented with the following error: JSON API: Internal Server Error Any advice on how to get this to work?

I just came back here to follow-up and saw your post. When I went to do the steps in the link and tried to access the website and it randomly is working again!? Was there a fix for something?

I am also having issues with accessing the WebUI all of a sudden for this container. It just times out... I am using PIA with wireguard and tried deleting the wg0.conf and starting fresh based on the comment above but no luck. It seems like the container starts OK!?! Container logs are below: 2023-04-07 10:09:00,240 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '34242' 2023-04-07 10:09:20,555 DEBG 'watchdog-script' stdout output: [info] Deluge listening interface IP 0.0.0.0 and VPN provider IP 10.36.156.178 different, marking for reconfigure 2023-04-07 10:09:20,560 DEBG 'watchdog-script' stdout output: [info] Deluge not running 2023-04-07 10:09:20,565 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI not running 2023-04-07 10:09:20,566 DEBG 'watchdog-script' stdout output: [info] Deluge incoming port 6890 and VPN incoming port 34242 different, marking for reconfigure 2023-04-07 10:09:20,566 DEBG 'watchdog-script' stdout output: [info] Attempting to start Deluge... [info] Removing deluge pid file (if it exists)... 2023-04-07 10:09:21,070 DEBG 'watchdog-script' stdout output: [info] Deluge key 'listen_interface' currently has a value of '10.11.249.36' [info] Deluge key 'listen_interface' will have a new value '10.36.156.178' [info] Writing changes to Deluge config file '/config/core.conf'... 2023-04-07 10:09:21,446 DEBG 'watchdog-script' stdout output: [info] Deluge key 'outgoing_interface' currently has a value of 'wg0' [info] Deluge key 'outgoing_interface' will have a new value 'wg0' [info] Writing changes to Deluge config file '/config/core.conf'... 2023-04-07 10:09:21,789 DEBG 'watchdog-script' stdout output: [info] Deluge key 'default_daemon' currently has a value of 'c1954debc9694ab798b3aa0100ea3e86' [info] Deluge key 'default_daemon' will have a new value 'c1954debc9694ab798b3aa0100ea3e86' [info] Writing changes to Deluge config file '/config/web.conf'... 2023-04-07 10:09:22,274 DEBG 'watchdog-script' stdout output: [info] Deluge process started [info] Waiting for Deluge process to start listening on port 58846... 2023-04-07 10:09:22,621 DEBG 'watchdog-script' stdout output: [info] Deluge process listening on port 58846 2023-04-07 10:09:26,479 DEBG 'watchdog-script' stdout output: Setting "random_port" to: False Configuration value successfully updated. 2023-04-07 10:09:26,480 DEBG 'watchdog-script' stderr output: <Deferred at 0x1463e4293580 current result: None> 2023-04-07 10:09:30,379 DEBG 'watchdog-script' stdout output: Setting "listen_ports" to: (34242, 34242) Configuration value successfully updated. 2023-04-07 10:09:30,380 DEBG 'watchdog-script' stderr output: <Deferred at 0x14d96cc935b0 current result: None> 2023-04-07 10:09:34,583 DEBG 'watchdog-script' stderr output: <Deferred at 0x1491bcf63400 current result: None> 2023-04-07 10:09:34,666 DEBG 'watchdog-script' stdout output: [info] No torrents with state 'Error' found 2023-04-07 10:09:34,667 DEBG 'watchdog-script' stdout output: [info] Starting Deluge Web UI... 2023-04-07 10:09:34,667 DEBG 'watchdog-script' stdout output: [info] Deluge Web UI started

Is there a reason this plugin doesn't show up in community apps anymore? Is it not compatable with the latest versions of unraid?

Did you ever get this figured out? I am having a similar issue. I set up my Windows VM and the install went fine, installed drivers, etc. I enabled Windows Remote Desktop and edited the VM template to use my GTX 1050 instead of VNC and it never booted. Removed the GTX 1050 and set it back to VNC and was presented with the same prompt as above.

I just tried to erase and format an nvme drive and I selected btrfs and got vfat and now I cant mount it... Is this normal? Mar 20 20:45:50 Datasaurusrex unassigned.devices: Removing all partitions from disk '/dev/nvme0n1'. Mar 20 20:47:32 Datasaurusrex unassigned.devices: Format device '/dev/nvme0n1'. Mar 20 20:47:32 Datasaurusrex unassigned.devices: Device '/dev/nvme0n1' block size: 976773168. Mar 20 20:47:32 Datasaurusrex unassigned.devices: Clearing partition table of disk '/dev/nvme0n1'. Mar 20 20:47:32 Datasaurusrex unassigned.devices: Clear partition result: 1+0 records in 1+0 records out 2097152 bytes (2.1 MB, 2.0 MiB) copied, 0.0107248 s, 196 MB/s Mar 20 20:47:34 Datasaurusrex unassigned.devices: Reloading disk '/dev/nvme0n1' partition table. Mar 20 20:47:34 Datasaurusrex unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table Mar 20 20:47:34 Datasaurusrex unassigned.devices: Creating Unraid compatible mbr partition on disk '/dev/nvme0n1'. Mar 20 20:47:34 Datasaurusrex kernel: nvme0n1: p1 Mar 20 20:47:34 Datasaurusrex unassigned.devices: Create mbr partition table result: write mbr signature done Mar 20 20:47:36 Datasaurusrex unassigned.devices: Reloading disk '/dev/nvme0n1' partition table. Mar 20 20:47:36 Datasaurusrex kernel: nvme0n1: p1 Mar 20 20:47:36 Datasaurusrex unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table Mar 20 20:47:36 Datasaurusrex unassigned.devices: Formatting disk '/dev/nvme0n1' with 'btrfs' filesystem. Mar 20 20:47:36 Datasaurusrex unassigned.devices: Format drive command: /sbin/mkfs.btrfs -f '/dev/nvme0n1p1' 2>&1 Mar 20 20:47:38 Datasaurusrex kernel: BTRFS: device fsid 3eaa032f-8941-45fb-8d24-37c5ba01353f devid 1 transid 6 /dev/nvme0n1p1 scanned by mkfs.btrfs (16143) Mar 20 20:47:39 Datasaurusrex unassigned.devices: Format disk '/dev/nvme0n1' with 'zfs' filesystem: btrfs-progs v6.0.1 See http://btrfs.wiki.kernel.org for more information. Performing full device TRIM /dev/nvme0n1p1 (465.76GiB) ... NOTE: several default settings have changed in version 5.15, please make sure this does not affect your deployments: - DUP for metadata (-m dup) - enabled no-holes (-O no-holes) - enabled free-space-tree (-R free-space-tree) Label: (null) UUID: 3eaa032f-8941-45fb-8d24-37c5ba01353f Node size: 16384 Sector size: 4096 Filesystem size: 465.76GiB Block group profiles: Data: single 8.00MiB Metadata: DUP 1.00GiB System: DUP 8.00MiB SSD detected: yes Zoned device: no Incompat features: extref, skinny-metadata, no-holes Runtime features: free-space-tree Checksum: crc32c Number of devices: 1 Devices: ID SIZE PATH 1 465.76GiB /dev/nvme0n1p1 Mar 20 20:47:42 Datasaurusrex unassigned.devices: Reloading disk '/dev/nvme0n1' partition table. Mar 20 20:47:42 Datasaurusrex kernel: nvme0n1: p1 Mar 20 20:47:42 Datasaurusrex unassigned.devices: Reload partition table result: /dev/nvme0n1: re-reading partition table Mar 20 20:47:57 Datasaurusrex unassigned.devices: Mounting partition 'nvme0n1p1' at mountpoint '/mnt/disks/S3X4NB0K428321V'... Mar 20 20:47:57 Datasaurusrex unassigned.devices: Mount cmd: /sbin/mount -t 'vfat' -o rw,noatime,nodiratime,nodev,nosuid,iocharset=utf8,umask=000 '/dev/nvme0n1p1' '/mnt/disks/S3X4NB0K428321V' Mar 20 20:47:57 Datasaurusrex kernel: FAT-fs (nvme0n1p1): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! Mar 20 20:47:57 Datasaurusrex kernel: FAT-fs (nvme0n1p1): bogus number of reserved sectors Mar 20 20:47:57 Datasaurusrex kernel: FAT-fs (nvme0n1p1): Can't find a valid FAT filesystem Mar 20 20:48:00 Datasaurusrex unassigned.devices: Mount of 'nvme0n1p1' failed: 'mount: /mnt/disks/S3X4NB0K428321V: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. dmesg(1) may have more information after failed mount system call. ' Mar 20 20:48:00 Datasaurusrex unassigned.devices: Partition 'S3X4NB0K428321V' cannot be mounted.

The reason I said that was because in your initial post, you showed paths on the flash drive (/boot). Now that you moved them and made them executable I think you should be good. You need to enable mover logging on the main ‘Mover Settings’ tab and then you will see everything it does in the syslog. As a side note you really should check out the Trash Guides link that I placed above. His script is well vetted and supported by a large community and much more advanced. It uses the qBittorrent api to pause your torrents, run the mover, then resume your torrents. No shutting down or shopping any services and no before after scripting in the somewhat buggy mover tuning plugin.

EDIT: So I am working through something similar and I believe the issue you will find in the logs if you turn them on is that the script cannot be run because of permissions issues. My understanding is that recent updates to Unraid prevent scripts from being run on the flash drive without specifying a run command which as far as I can tell is not possible to do within the mover tuning plugin. See below. Therefore all I did to get around this was move the script from the flash drive to my cache drive and made in executable. Update the path in the mover tuning plugin and now it works well. ORIGINAL POST: Try turning on logging and see what’s in the syslog. This should let you know if and why the scripts are not being run. If you are using qbittorrent with any kind of automation, I would highly recommend you check out trash guides. https://trash-guides.info/Downloaders/qBittorrent/Tips/How-to-run-the-unRaid-mover-for-qBittorrent/#the-script

Does anyone have this working successfully with sonarr/radarr and completed download handling? I am having some troubles with the download location and how the categories in radarr/sonarr interact with transmission. It seems like transmission is messing up the download locations. I initially tried to use categories but I am getting double data/torrent/movies/movies and data/torrent/movies/tv when I just want data/torrent/movies and /data/torrent/tv. I noticed sonarr has the option the override the download path and radarr does not. This initially seemed like a good option but it seems only one of them has this functionality. Am I approaching this right. I think I am close to having this all done but the transmission arr automation is giving me a hard My initial config in transmission is to set the download location to /data/torrent and then have sonarr/radarr append the movies and tv folders with categories but they end up updating the download location in transmission settings and it gets confused. What am I missing?

Am I understanding the help notes correctly that if I have pre-post scripts that they will be run at every check regardless of whether the conditions are met to run the mover? Ie. If I have the schedule set to run every hour then my torrent docker would stop and start every hour (if that was my script) regardless of weather the mover runs?

I finally had a chance to get back to looking at this. That line is not present in the current unraid template. I am trying to install the Transmission-VPN docker and the /config path is not there... Also what is this tmedia downloads mapping?

I am wondering where the config files are located for the Transmission container? I don't see the /config variable that is referenced in the description anywhere in the template?

This solved it for me. Thank you!

I am wondering if anyone is using intel quicksync with the Shinobi docker? I see there is inclusion of a variable for passing through your nvidia gpu but cant find any documentation on using intels igpu. Is anyone doing this that can advise on how to get this working? I know that you can use the below on regular linux with docker for things like plex. Does the same appy for Shinobi? --device=/dev/dri:/dev/dri

Did you ever find a solution for this? I am having a similar issue.

I am also getting a similar error when shutting down/restarting my VM. Did anyone ever figure this out? I have to do a hard restart everytime this happens. Its starting to get frusterating. https://pastebin.com/NTW2wsbc

I am also having this issue when using fstab and also autofs (which I moved to trying to solve the fstab issue). I am wondering if there is a good solution. I am sharing via nfs movies, tv and some other videos locations from my unraid machine to another computer on my network. I get the following: plex@dionysus:/mnt/media$ ls ls: cannot access 'TvShows': Stale file handle Home-Movies Movies TvShows and then when enabling logging in autofs. I see the following in the logs: Apr 9 12:49:51 dionysus kernel: [684639.585302] fsid 0:73: expected fileid 0x901000025857ba7, got 0x27000011a31bce Apr 9 12:49:51 dionysus kernel: [684639.585797] NFS: server 192.168.86.2 error: fileid changed Apr 9 12:49:51 dionysus kernel: [684639.585797] fsid 0:73: expected fileid 0x901000025857ba7, got 0x27000011a31bce I am wondering if this is an issue with using a cache device for these locations? Could it be that this is caused by the files initially being on cache and then getting moved to the array?

Is there a way I can force it to use a different server?

I have been runnning this container for quite some time and it has worked great. I recently migrated to a new router (pfsense) and seem to now have an issue using a VPN. The container will not run using a VPN but will run fine without it. I am not sure if its an issue with the router but I am suspect. Anyway, I am looking for some advice to hopefully fix this. When I enable the VPN, I see this in the logs: 2020-04-02 18:33:26,263 DEBG 'start-script' stdout output: [info] Curl successful for https://www.privateinternetaccess.com/vpninfo/servers?version=82, response code 200 2020-04-02 18:33:26,356 DEBG 'start-script' stdout output: [warn] PIA endpoint 'ca-toronto.privateinternetaccess.com' is not in the list of endpoints that support port forwarding, DL/UL speeds maybe slow [info] Please consider switching to one of the endpoints shown below 2020-04-02 18:33:26,357 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- 2020-04-02 18:33:26,357 DEBG 'start-script' stdout output: [info] de-berlin.privateinternetaccess.com [info] de-frankfurt.privateinternetaccess.com [info] sweden.privateinternetaccess.com [info] swiss.privateinternetaccess.com [info] france.privateinternetaccess.com [info] czech.privateinternetaccess.com [info] spain.privateinternetaccess.com [info] ro.privateinternetaccess.com [info] israel.privateinternetaccess.com [info] Attempting to get dynamically assigned port... 2020-04-02 18:33:26,367 DEBG 'start-script' stdout output: [info] Attempting to curl http://209.222.18.222:2000/?client_id=*removed* 2020-04-02 18:33:26,375 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 2020-04-02 18:33:26,375 DEBG 'start-script' stdout output: [info] 12 retries left [info] Retrying in 10 secs... 2020-04-02 18:33:36,385 DEBG 'start-script' stdout output: [warn] Response code 000 from curl != 2xx [warn] Exit code 7 from curl != 0 [info] 11 retries left [info] Retrying in 10 secs... Any help is greatly appreciated!

Did you ever solve this? I am having the same issue.

I did not, but I can do this. Thank you!

I updated to iMacPro1,1 and now my VM freezes after logging in and reboots. Is there a way to fix the config.plist to revert it back so I can get it back working again and do some more testing?

Does this still include Flood?

Wow...just stumbled upon this thread trying to get my intel 660p nvme drive working. I was optimistic with all of the back and forth support from limetech on this but see that it has basically been abandoned. I guess I am returning my intel and forking over the cash for a Samsung...

Again, amazing work. Just wanted to report that when adding a new VM there a few unstyled sections. Can confirm this is not an issues on a created VM. Probs why it was missed.