mooky

Members
  • Content Count

    24
  • Joined

  • Last visited

Community Reputation

3 Neutral

About mooky

  • Rank
    Newbie
  1. Just discovered this myself, unRAID 6.9.2 as well. One core, pegged to 100%, htop showing the offending process to be wsdd. Attempting to fix/bypass, but like DanW said, it may not be unRAID's bug, but if there is a more recent package that fixes it, it is your responsibility to test and merge it into unRAID to prevent a race condition inside your product. My CPU had hundreds of hours of time on that one thread until I noticed it just gobbling power and generating heat for no reason. Seems rather wasteful if you ask me.
  2. @dlandon, So the "scripts file" automatically fires always when that particular disk is plugged in, or is there a list of disk events I can use to trigger stuff in this file? Ideally I'd like to have an rclone sync start on plugin of the disk, and then further trigger once a day until I unplug it and offsite it. I'm going to be doing a rotation of 2 different disks so I can finally make good on legitimately accomplishing a proper 3-2-1 backup strategy.
  3. So it's probably been explained, but searching through 232 pages isn't exactly fun, so I'll ask: When I go into "settings" for a partition, I see the mount point (WD-2TB), and share toggle, then below I see: Script File: /boot/config/plugins/unassigned.devices/WD-2TB.sh RUN IN BACKGROUND (toggle off/on) User Script: (undefined) Script Content: Now I see the WD-2TB.sh script is 0 bytes, and empty. What is the point of it? and how does it differ from "User Script" ? I want to have an rclone sync command do a backup to the USB
  4. Hey @binhex, I get the following errors when i run qbittorrentvpn. If I stop the docker, and remove the "perms.txt" file, then relaunch the image, the error goes away for a little while, but then it returns like herpes. Any help to point me in the right direction. I'm running the docker as UID=3501, GID=100, so although the user isn't the standard 99:100 that unraid expects, they are part of the same group, and the permissions look to be fine with a cursory look. Nobody is 99:100 dockoper is 3501:100 When I started up docker: -rwxrwxr-x 1 nobody users 192 Apr 12
  5. TexasUnraid, with a tightening of the ip_tables for leakage, you now have to do one of two things as outlines on this page, Q26 https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md That should fix connecting to your bittorrent client.
  6. Tell unraid to spin disks down in settings, and then use the "dynamix cache dirs" unraid application. I find this the simplest solution to not have problems between your download client and radarr/sonarr/etc. EDIT: You can also use "split levels" in your unraid share to designate and help steer where things go, as well as included and excluded disks.
  7. Keep it simple. Here's my docker setup: version: '3.7' services: qbittorrentvpn: image: binhex/arch-qbittorrentvpn container_name: qbitvpn volumes: - /mnt/citadel-library:/data - /container-data/qbitvpn:/config environment: - PUID=99 - PGID=100 - TZ=America/Chicago - VPN_ENABLED=yes - VPN_USER=p####### - VPN_PASS=abc123def456 - VPN_PROV=pia - VPN_CLIENT=openvpn - STRICT_PORT_FORWARD=no - ENABLE_PRIVOXY=yes - LAN_NETWORK=192.168.1.0/24 - WEBUI_PORT=25514 - UMASK=000 ca
  8. Subsequent to my own previous post, I have rolled back my Alpine Linux version and everything works again. It seems there may be an internal problem with a recent version of iptables routing inside docker itself. That would explain the weird behaviour where it would sometimes start and throw errors in some of my docker images with the above errors I already noted, but others would launch, but their UI's would still be unreachable though their web interfaces, even though they were running. It was really weird behaviour. I don't know if its Alpine specific, or a larger docker problem
  9. okay, I know no one here is an expert necessarily in a particular Linux distribution, in this case, Alpine Linux, but I'm coming up short on google-fu trying to get arch-qbittorrentvpn (and other related docker images) working I had a docker-compose that launched correctly and worked on Alpine 3.12 (after installing all the docker related stuff I needed to make it work) I upgraded my Alpine to 3.13, and now, its broken. I even went as far as doing a fresh install in another with a base install of Alpine 3.13.1 to see if the upgrade borked something, and I can repor
  10. Are you able to bring up the webUI ? If so, the default is as I stated. There are 2 settings in the conf file: WebUI\Password_PBKDF2=<HASHED PASSWORD HERE> WebUI\Username=mooky But those are added once you log in through the GUI, and go into options to change it. What did you define as your WEBUI_PORT? Here's my docker-compose yaml file that fires my instance of the docker: services: qbittorrentvpn: image: binhex/arch-qbittorrentvpn container_name: qbitvpn volumes: - /mnt/myfiles:/data - /persiststorage/qbitvpn:/config
  11. The openVPN portion doesn't have any defaults, you need to have an already paid-for VPN service you subscribe to. The default login/password for qbittorrent however is: login: admin password: adminadmin Change that the first chance you get.
  12. It's ready AFAIK, even people on reddit say that even though its not official that for the most part, barring some edge case weirdness of your particular setup that its good to go for at least a while now. Backup your whole persistent data for radarr dir: tar -zcvf radarr.gz /yourpathto/radarr/ then in my case, in my docker-compose, i simply change the image it pulls image: linuxserver/radarr:nightly Badda-bing, badda-boom, that's it. Worst comes to worst, you blow up the persistent data directory, because some of it will be updated to v3
  13. Just an FYI to everyone if it's not here already. I've tested the most recent version of radarr 3.0.0.4071 - aka ":nightly" (there probably is newer but on Saturday that was the version) and bittorrent 4.3.x aka ":latest" and the problems with importing are fixed. This does NOT apply to radarr 0.2 which apparently will not be fixed for qbittorrent 4.3.x You must stick with qbittorrent 4.2.5 if you are still on radarr 0.2 I assume, but haven't checked that this is also fixed on sonarr since they were both experiencing it and probably pulling the same code fix.
  14. Everything for me seems to work A-OK, except this error as the docker launches, which doesn't seem to affect the launch of rtorrent, rutorrent, openvpn, or privoxy: rtorrent | 2020-10-25 16:48:05,276 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 139659360098528 for <Subprocess at 139659360097856 with name pyrocore-script in state RUNNING> (stdout)> rtorrent | 2020-10-25 16:48:05,276 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 139659360219776 for <Subprocess at 139659360097856 with name pyrocore-script in state RUNNING> (stderr