Jorgen

Members
  • Posts

    226
  • Joined

  • Last visited

Everything posted by Jorgen

  1. Where are you getting that error message? Mac OS finder when browsing the TM share? Or from Time Machine itself? Can you browse the same directory from the unraid console? If it’s the latter, attach diagnostics to the next post and someone may be able to tell what’s going on Sent from my iPhone using Tapatalk
  2. That’s perfectly normal when using the network of another docker, like delugevpn in your case. The web ui button under the docker will simply not be there. Nothing wrong with your config. Use a bookmark in your browser instead, or remember the ip and port number to use. Sent from my iPhone using Tapatalk
  3. Got another hang. Strangely, this command does not work outside the docker (from within the movies subfolder inside the "inter" directory of nzbget appdata) # unrar x -y -p- -o+ *.rar UNRAR 5.80 freeware Copyright (c) 1993-2019 Alexander Roshal Extracting from 22397053c75341bca318684f2bb5b77f.part01.rar Extracting from 22397053c75341bca318684f2bb5b77f.part02.rar ... Extracting from 22397053c75341bca318684f2bb5b77f.part63.rar No files to extract While this works without problems: # unrar x -y -p- -o+ 22397053c75341bca318684f2bb5b77f.part01.rar UNRAR 5.80 freeware Copyright (c) 1993-2019 Alexander Roshal Extracting from 22397053c75341bca318684f2bb5b77f.part01.rar Extracting 22397053c75341bca318684f2bb5b77f.mkv 1% Extracting from 22397053c75341bca318684f2bb5b77f.part02.rar ... 22397053c75341bca318684f2bb5b77f.mkv 3% ... Extracting from 22397053c75341bca318684f2bb5b77f.part63.rar ... 22397053c75341bca318684f2bb5b77f.mkv OK All OK Either way, I don't think it's the command that is wrong, and the archive unpacks correctly so it's not a corrupted file. The container unrar version is slightly older (5.60 beta 3 freeware) but I don't think that would be it either? So I guess we're back to "don't know what's going on here".
  4. @binhex I've been seeing more than usual of the unrar hanging lately, so I thought I'd try to get to the bottom of it again. Unfortunatly, I wasn't able to. But just in case it gives you any new ideas, here's what I found. When a file is stuck in unpacking, the docker console shows an unrar process running for a few seconds, then re-spawning with a new PID. This never ends. During this statem, Sys load in TOP is consistently high (4+) and so is CPU usage for both nzbget and unrar. If I kill the main nzbget process, it restart itself and spawns a new unrar process that finishes quickly. This is consistent with the docker restart workaround. I didn't test running the exact same unrar command outside of the docker, but will next time the unpacking hangs. It seems SAB had a similar issue when using Direct Unpack, https://forums.sabnzbd.org/viewtopic.php?p=117607#p117607 It quickly got above my skill level, but I don't think they got to the bottom of it either, if it is the same underlying problem... sh-5.1# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2368 700 ? Ss 16:17 0:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh root 6 0.0 0.1 31668 25776 ? S 16:17 0:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n nobody 56 0.0 0.0 7336 3736 ? S 16:17 0:00 /bin/bash /home/nobody/start.sh root 57 0.0 0.0 7336 3532 ? S 16:17 0:00 /bin/bash /usr/local/bin/shutdown.sh nzbget root 59 0.0 0.0 5356 692 ? S 16:17 0:00 sleep infinity nobody 61 87.2 0.4 4137240 69104 ? Sl 16:17 17:31 /usr/local/bin/nzbget/nzbget --option UnrarCmd=/usr/bin/unrar -c /config/nzbget.conf -s root 996 0.0 0.0 7600 4392 pts/0 Ss 16:23 0:00 sh nobody 1248 11.2 0.0 10976 5212 ? Rs 16:37 0:00 /usr/bin/unrar x -y -p- -o+ *.rar /downloads/nzbget/tv/Marcella.S01E06.720p.HDTV.x264/_unpack/ root 1251 0.0 0.0 10240 3308 pts/0 R+ 16:37 0:00 ps aux sh-5.1# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2368 700 ? Ss 16:17 0:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh root 6 0.0 0.1 31668 25588 ? S 16:17 0:01 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n nobody 56 0.0 0.0 7336 3732 ? S 16:17 0:00 /bin/bash /home/nobody/start.sh root 57 0.0 0.0 7336 3532 ? S 16:17 0:00 /bin/bash /usr/local/bin/shutdown.sh nzbget root 59 0.0 0.0 5356 692 ? S 16:17 0:00 sleep infinity nobody 61 94.0 0.6 4137240 108424 ? Sl 16:17 39:20 /usr/local/bin/nzbget/nzbget --option UnrarCmd=/usr/bin/unrar -c /config/nzbget.conf -s root 996 0.0 0.0 7600 4392 pts/0 Ss 16:23 0:00 sh nobody 1630 1.0 0.0 9944 4056 ? Ss 16:59 0:00 /usr/bin/unrar x -y -p- -o+ *.rar /downloads/nzbget/tv/Marcella.S01E06.720p.HDTV.x264/_unpack/ root 1632 0.0 0.0 10240 3384 pts/0 R+ 16:59 0:00 ps aux sh-5.1# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2368 700 ? Ss 16:17 0:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh root 6 0.0 0.1 31668 25588 ? S 16:17 0:01 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n nobody 56 0.0 0.0 7336 3732 ? S 16:17 0:00 /bin/bash /home/nobody/start.sh root 57 0.0 0.0 7336 3532 ? S 16:17 0:00 /bin/bash /usr/local/bin/shutdown.sh nzbget root 59 0.0 0.0 5356 692 ? S 16:17 0:00 sleep infinity nobody 61 94.1 0.6 4137240 108424 ? Sl 16:17 39:34 /usr/local/bin/nzbget/nzbget --option UnrarCmd=/usr/bin/unrar -c /config/nzbget.conf -s root 996 0.0 0.0 7600 4392 pts/0 Ss 16:23 0:00 sh nobody 1633 55.5 0.0 10976 5172 ? Rs 16:59 0:03 /usr/bin/unrar x -y -p- -o+ *.rar /downloads/nzbget/tv/Marcella.S01E06.720p.HDTV.x264/_unpack/ root 1638 0.0 0.0 10240 3484 pts/0 R+ 16:59 0:00 ps aux sh-5.1# kill -9 61 sh-5.1# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2368 700 ? Ss 16:17 0:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh root 6 0.0 0.1 31668 25592 ? S 16:17 0:01 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n root 57 0.0 0.0 7336 3532 ? S 16:17 0:00 /bin/bash /usr/local/bin/shutdown.sh nzbget root 59 0.0 0.0 5356 692 ? S 16:17 0:00 sleep infinity root 996 0.0 0.0 7600 4392 pts/0 Ss 16:23 0:00 sh nobody 1719 0.5 0.0 7336 3780 ? S 17:04 0:00 /bin/bash /home/nobody/start.sh nobody 1722 21.2 0.1 3278280 20192 ? Sl 17:04 0:00 /usr/local/bin/nzbget/nzbget --option UnrarCmd=/usr/bin/unrar -c /config/nzbget.conf -s nobody 1771 68.2 0.0 10956 5260 ? Rs 17:04 0:02 /usr/bin/unrar x -y -p- -o+ *.rar /downloads/nzbget/tv/Marcella.S01E06.720p.HDTV.x264/_unpack/ root 1777 0.0 0.0 10240 3464 pts/0 R+ 17:04 0:00 ps aux sh-5.1# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.0 0.0 2368 700 ? Ss 16:17 0:00 /usr/bin/tini -g -- /bin/bash /usr/local/bin/init.sh root 6 0.0 0.1 31668 25592 ? S 16:17 0:01 /usr/bin/python /usr/bin/supervisord -c /etc/supervisor.conf -n root 57 0.0 0.0 7336 3532 ? S 16:17 0:00 /bin/bash /usr/local/bin/shutdown.sh nzbget root 59 0.0 0.0 5356 692 ? S 16:17 0:00 sleep infinity root 996 0.0 0.0 7600 4392 pts/0 Ss 16:23 0:00 sh nobody 1719 0.0 0.0 7336 3780 ? S 17:04 0:00 /bin/bash /home/nobody/start.sh nobody 1722 23.2 0.3 4102664 49804 ? Sl 17:04 0:05 /usr/local/bin/nzbget/nzbget --option UnrarCmd=/usr/bin/unrar -c /config/nzbget.conf -s root 1880 0.0 0.0 10240 3308 pts/0 R+ 17:04 0:00 ps aux
  5. I’ve moved over to the unraid built-in Wireguard solution with great success: https://forums.unraid.net/topic/84226-wireguard-quickstart/ Sent from my iPhone using Tapatalk
  6. Are you talking about the same situation as Twinkie above, where you need to access Sab vpn while your client is connected via wireguard from outside your home network? Or are you talking about setting up Sab vpn to use wireguard to connect to mullvad? If it’s the latter, you’ll need to post the question in the support thread for the Sab vpn docker you’re using. Sent from my iPhone using Tapatalk
  7. If you are using one of Binhex’s VPN containers, a hardening of iptables was introduced a few months ago to prevent up leakage. You will need to add and configure additional container settings, please refer to the support thread for the specific docker you’re using. Sent from my iPhone using Tapatalk
  8. I think you need to add the wireguard tunnel IP range to the Lan Network variable in the Sab VPN docker. Just add it after your normal home LAN range, separated by a comma. Edit: if you’re using the defaults for wireguard, the IP range to add to Sab is 10.253.0.0/24
  9. This is a long-standing problem that no one has been able to find the root cause of. The common workaround is to use User Scripts to restart the container on a schedule every night. There should be details on how to do this somewhere in this thread. Sent from my iPhone using Tapatalk
  10. Sorry I won’t be able to help, my unRAID server is in storage for a month due to house renovations so I would just be guessing at things to try. Did you already try just copying the wg config file from appdata on one of the Binhex VPN dockers? Sent from my iPhone using Tapatalk
  11. Hmm that doesn’t seem right. PIA themselves have published scripts to use with wireguard outside their app: https://www.privateinternetaccess.com/helpdesk/kb/articles/manual-connection-and-port-forwarding-scripts Sent from my iPhone using Tapatalk
  12. I don’t have a solution for you, but many of us are using wireguard and PIA in binhex’s excellent VPN enabled containers. Maybe you could look into the script he’s using to get the required settings? Or even set up a container and copy the wg config file? Sent from my iPhone using Tapatalk
  13. It’s static. Can’t remember what the default one is, but you can change it to whichever supported endpoint you wish and it should persist from that point. Sent from my iPhone using Tapatalk
  14. That’s how it works when binding the network. Sent from my iPhone using Tapatalk
  15. From a few posts up. But you’re probably better off in the long run to try to get sonarr v3 working with the seed box. Sent from my iPhone using Tapatalk
  16. [mention]strykn [/mention] [mention]nowhere99 [/mention] did you see the pinned post at the top of this thread and followed the instructions? Edit: Sorry! The post is pinned to the delugeVPN thread, see here: https://forums.unraid.net/topic/44109-support-binhex-delugevpn/?do=findComment&comment=951973
  17. Yes, using tar from the command line. Here’s an example: https://www.linux.org/threads/list-tar-contents-only-first-level-then-subdirectory-extract.10491/ Sent from my iPhone using Tapatalk
  18. Sounds like your routing Sonarr et al through the DelugeVPN container network? In that case, you should NOT use the proxy settings in Sonarr. It's one or the other, not both. You should also add the SABnzbd ports to VPN_OUTPUT_PORTS environment variable. Because Sonarr running INSIDE the DelugeVPN container network, needs to be allowed to talk OUT to the SAB ports running outside the DelugeVPN network. This is explained in Q27 here https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md Of course, if you are not routing the apps through the DelugeVPN network this is not applicable.
  19. Sonarr is supposed to remove the torrent from Deluge after it reaches the defined ratio, but I never got that to work either. AutoRemovePlus plugin is the way to go in my opinion. The most likely reason the egg isn't accepted for you is that the Python version in this container was recently updated to 3.9. If you have the 3.8 egg in the plugin folder already, simple rename it to 3.9 (see below) and restart the container: AutoRemovePlus-2.0.0-py3.9.egg If you don't have it, download the 3.8 version from here: https://forum.deluge-torrent.org/viewtopic.php?f=9&t=55733 Put the egg into the plugin folder, rename it to 3.9 and restart container.
  20. Thanks, hardcoding "/watch" made it work again, of course. Just for my understanding though, am I misinterpreting the table on the hooks page? I'm using post_watch_folder_processing.sh
  21. Hi Djoss, I've been running this container for a looooong time without any problems, using the automatic watch folder workflow and a post_watch_folder_processing script to stop the container after processing if the watch folder is empty. Sometime during the last few months (maybe longer) the script has stopped working as intended, with this in the log: [autovideoconverter] Conversion ended successfully. [autovideoconverter] Removed /watch/moviename.mkv'. [autovideoconverter] Watch folder '/watch' processing terminated. [autovideoconverter] Executing post watch folder processing hook... post-watch folder processing: Watch folder = /watch/BDMV watch folder not empty, won't shut down [autovideoconverter] Post watch folder processing hook exited with 0 [autovideoconverter] Change detected in watch folder '/watch'. [autovideoconverter] Processing watch folder '/watch'... [autovideoconverter] Watch folder '/watch' processing terminated. Here's the script: #!/bin/sh # # This is an example of a post watch folder processing hook. This script is # always invoked with /bin/sh (shebang ignored). # # The argument of the script is the path to the watch folder. # WATCH_FOLDER=$1 echo "post-watch folder processing: Watch folder = $WATCH_FOLDER" if [ -d "/$WATCH_FOLDER" ] && [ -z "$(ls -A "$WATCH_FOLDER")" ] then echo "watch folder empty, shutting down" killall -sigterm ghb else echo "watch folder not empty, won't shut down" fi I don't understand where /watch/BDMV is coming from? Are you able to shed some light on this for me, please? Has the argument value changed recently? Is Handbrake adding a temporary BDMV folder during processing? Or have I added another watch folder somehow without realising? In the container settings, the watch folder is set to /mnt/user/Media/Handbrake_hotfolder/watch/ Thanks in advance Jorgen Edit: I only have one watch folder defined in the container settings, and no optical drives passed through. Full run command: root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='HandBrake' --net='bridge' -e TZ="Australia/Sydney" -e HOST_OS="Unraid" -e 'AUTOMATED_CONVERSION_PRESET'='My Presets/Mathias_MKV_720p30_v2' -e 'AUTOMATED_CONVERSION_FORMAT'='mkv' -e 'AUTOMATED_CONVERSION_KEEP_SOURCE'='0' -e 'AUTOMATED_CONVERSION_OUTPUT_SUBDIR'='' -e 'AUTOMATED_CONVERSION_OUTPUT_DIR'='/output' -e 'AUTOMATED_CONVERSION_NON_VIDEO_FILE_ACTION'='ignore' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'APP_NICENESS'='15' -e 'UMASK'='000' -e 'X11VNC_EXTRA_OPTS'='' -e 'AUTOMATED_CONVERSION_SOURCE_STABLE_TIME'='5' -e 'AUTOMATED_CONVERSION_SOURCE_MIN_DURATION'='10' -e 'SECURE_CONNECTION'='0' -e 'AUTOMATED_CONVERSION_CHECK_INTERVAL'='5' -e 'AUTOMATED_CONVERSION_MAX_WATCH_FOLDERS'='5' -e 'AUTOMATED_CONVERSION_NO_GUI_PROGRESS'='0' -e 'AUTOMATED_CONVERSION_NON_VIDEO_FILE_EXTENSIONS'='jpg jpeg bmp png gif txt nfo' -e 'AUTOMATED_CONVERSION_HANDBRAKE_CUSTOM_ARGS'='' -e 'AUTOMATED_CONVERSION_INSTALL_PKGS'='' -e 'AUTOMATED_CONVERSION_VIDEO_FILE_EXTENSIONS'='' -e 'AUTOMATED_CONVERSION_OVERWRITE_OUTPUT'='0' -p '7803:5800/tcp' -p '7903:5900/tcp' -v '/mnt/user/Media':'/storage':'ro' -v '/mnt/user0/Media/Handbrake_hotfolder/output/':'/output':'rw' -v '/mnt/user/Media/Handbrake_hotfolder/watch/':'/watch':'rw' -v '/mnt/cache/appdata/HandBrake':'/config':'rw' --device='/dev/dri' --cap-add=SYS_NICE --log-opt max-size=50m --log-opt max-file=1 'jlesage/handbrake'
  22. ok, there was a bug in the container updates yesterday in regards to wireguard. Try forcing an update now and see if it fixes it, binhex pushed a fix a few hours ago.
  23. In Jackett proxy config you should use the 172.17.x.x IP of the DelugeVPN container. I think this also assumes that both Jackett and DelugeVPN containers are using the same docker network, which is bridge by default:
  24. No terminal command required, it's shown on the docker page in unraid: One thing to keep in mind if you go down this route (pun intended) is that the docker IP is dynamcially assigned and could change on restart of containers or the unraid server. If things always start in the same order it probably won't, but just be aware of it if things suddenly stops working again.
  25. Ah, interesting. Could you share a screenshot of the Jacket proxy settings? Is that a 172.x.x.x IP?