TheDragon Posted November 8, 2016 Share Posted November 8, 2016 docker exec bash I used this command to get to a command line for this container. I was hoping to run a traceroute, however it just returns command not found. Is there a way I can get traceroute to install inside this container? Quote Link to comment
saarg Posted November 8, 2016 Share Posted November 8, 2016 docker exec bash I used this command to get to a command line for this container. I was hoping to run a traceroute, however it just returns command not found. Is there a way I can get traceroute to install inside this container? You need the container you want to exec into also. Like below. docker exec -it sabnzbd bash Quote Link to comment
TheDragon Posted November 8, 2016 Share Posted November 8, 2016 docker exec bash I used this command to get to a command line for this container. I was hoping to run a traceroute, however it just returns command not found. Is there a way I can get traceroute to install inside this container? You need the container you want to exec into also. Like below. docker exec -it sabnzbd bash Thanks for the reply, I'm getting to a bash prompt now but if I try and use ping or traceroute I get command not found. Is there a way I can install them? I tried to use apt-get install but doesn't seem to like that either! ? Quote Link to comment
CHBMB Posted November 8, 2016 Share Posted November 8, 2016 docker exec bash I used this command to get to a command line for this container. I was hoping to run a traceroute, however it just returns command not found. Is there a way I can get traceroute to install inside this container? You need the container you want to exec into also. Like below. docker exec -it sabnzbd bash Thanks for the reply, I'm getting to a bash prompt now but if I try and use ping or traceroute I get command not found. Is there a way I can install them? I tried to use apt-get install but doesn't seem to like that either! ? Ping should work as should traceroute Might want to post what you're seeing in the terminal. Quote Link to comment
saarg Posted November 8, 2016 Share Posted November 8, 2016 docker exec bash I used this command to get to a command line for this container. I was hoping to run a traceroute, however it just returns command not found. Is there a way I can get traceroute to install inside this container? You need the container you want to exec into also. Like below. docker exec -it sabnzbd bash Thanks for the reply, I'm getting to a bash prompt now but if I try and use ping or traceroute I get command not found. Is there a way I can install them? I tried to use apt-get install but doesn't seem to like that either! ? apt-get update && apt-get install inetutils-traceroute inetutils-ping This should install the packages needed. Quote Link to comment
CHBMB Posted November 8, 2016 Share Posted November 8, 2016 docker exec bash I used this command to get to a command line for this container. I was hoping to run a traceroute, however it just returns command not found. Is there a way I can get traceroute to install inside this container? You need the container you want to exec into also. Like below. docker exec -it sabnzbd bash Thanks for the reply, I'm getting to a bash prompt now but if I try and use ping or traceroute I get command not found. Is there a way I can install them? I tried to use apt-get install but doesn't seem to like that either! ? apt-get update && apt-get install inetutils-traceroute inetutils-ping This should install the packages needed. Forgot this was Xenial.... errr, yeah that'll work. lol Quote Link to comment
grover Posted November 25, 2016 Share Posted November 25, 2016 I've just installed this Docker, but all I get if I go to the WebUI is the spinning cog. config all totally standard. dirs as below: /incomplete-downloads <-> /mnt/user/Usenet/incomplete /config <-> /mnt/user/appdata/sabnzbd /downloads <-> /mnt/user/Usenet/complete Last few lines of the logs look like this: 2016-11-25 15:26:12,314::INFO::[sabnzbdplus:1347] SSL potentially supported protocols ['SSLv23', 'TLSv1', 'TLSv1_1', 'TLSv1_2'] 2016-11-25 15:26:12,315::INFO::[sabnzbdplus:1348] SSL actually supported protocols ['v23', 't12', 't11', 't1'] 2016-11-25 15:26:12,319::INFO::[sabnzbdplus:1495] Starting web-interface on 0.0.0.0:8080 2016-11-25 15:26:12,325::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Bus STARTING 2016-11-25 15:26:12,330::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Started monitor thread '_TimeoutMonitor'. 2016-11-25 15:26:12,533::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Serving on http://0.0.0.0:8080 2016-11-25 15:26:12,535::INFO::[_cplogging:217] [25/Nov/2016:15:26:12] ENGINE Bus STARTED 2016-11-25 15:26:12,538::INFO::[panic:269] Launching browser with http://127.0.0.1:8080/sabnzbd 2016-11-25 15:26:12,539::INFO::[sabnzbdplus:1567] Starting sabnzbdplus-1.1.1 2016-11-25 15:26:12,545::INFO::[dirscanner:318] Dirscanner starting up 2016-11-25 15:26:12,547::INFO::[urlgrabber:71] URLGrabber starting up Any thoughts? I've tried removing and reinstalling a couple of time, no change. Quote Link to comment
Squid Posted November 25, 2016 Share Posted November 25, 2016 I've just installed this Docker, but all I get if I go to the WebUI is the spinning cog. config all totally standard. This is what lsio et al are going to need from you http://lime-technology.com/forum/index.php?topic=40937.msg481150#msg481150 Quote Link to comment
grover Posted November 25, 2016 Share Posted November 25, 2016 Cheers Squid. Docker run command below: [b]Command:[/b] root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="sabnzbd" --net="bridge" -e TZ="Europe/London" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 9090:9090/tcp -v "/mnt/user/Usenet/":"/downloads":rw -v "/mnt/user/Usenet/incomplete/":"/incomplete-downloads":rw -v "/mnt/user/appdata/sabnzbd":"/config":rw linuxserver/sabnzbd f2098efe1b32822c054bd315f9ea460454441ea5faf60e5bdad3c70199197513 The command finished successfully! Quote Link to comment
davisnub Posted November 27, 2016 Share Posted November 27, 2016 is multicore enabled by default? noticed it was grayed out in my config and was reading on how to enable it. thank you! Quote Link to comment
CHBMB Posted November 27, 2016 Share Posted November 27, 2016 is multicore enabled by default? noticed it was grayed out in my config and was reading on how to enable it. thank you! You tried searching in this thread? Quote Link to comment
davisnub Posted November 27, 2016 Share Posted November 27, 2016 is multicore enabled by default? noticed it was grayed out in my config and was reading on how to enable it. thank you! You tried searching in this thread? thanks for the help! i tried looking for the option to search within a thread but could only find the option to search within a forum Quote Link to comment
CHBMB Posted November 27, 2016 Share Posted November 27, 2016 is multicore enabled by default? noticed it was grayed out in my config and was reading on how to enable it. thank you! You tried searching in this thread? thanks for the help! i tried looking for the option to search within a thread but could only find the option to search within a forum Take a look at this helpful guide from trurl. Quote Link to comment
Inimical Posted November 30, 2016 Share Posted November 30, 2016 Every couple of months SAB stops responding - trying to restart it hangs unraid, only option seems to be a restart of the server. Anyone else experience anything like this? Quote Link to comment
CHBMB Posted November 30, 2016 Share Posted November 30, 2016 Every couple of months SAB stops responding - trying to restart it hangs unraid, only option seems to be a restart of the server. Anyone else experience anything like this? Restart of the server or restart of the container? Quote Link to comment
Inimical Posted November 30, 2016 Share Posted November 30, 2016 Every couple of months SAB stops responding - trying to restart it hangs unraid, only option seems to be a restart of the server. Anyone else experience anything like this? Restart of the server or restart of the container? Restart the server - restarting the container is what causes the server to hang. Quote Link to comment
CHBMB Posted November 30, 2016 Share Posted November 30, 2016 Every couple of months SAB stops responding - trying to restart it hangs unraid, only option seems to be a restart of the server. Anyone else experience anything like this? Restart of the server or restart of the container? Restart the server - restarting the container is what causes the server to hang. Something so infrequent, and without logs, impossible to say. May not even be a problem with the container, might be an issue on the host or docker service itself. Quote Link to comment
gravymaker Posted December 9, 2016 Share Posted December 9, 2016 Is sudo missing from the latest base image? I use sudo in some scripts and after upgrading to the latest container release, I get "sudo: command not found" Quote Link to comment
CHBMB Posted December 9, 2016 Share Posted December 9, 2016 Is sudo missing from the latest base image? I use sudo in some scripts and after upgrading to the latest container release, I get "sudo: command not found" Don't think it's needed. No code has been changed in the sabnzbd docker for about two months. root@server:~# docker exec -it sabnzbd bash root@1117e7d9ae93:/# id uid=0(root) gid=0(root) groups=0(root) root@1117e7d9ae93:/# Quote Link to comment
gravymaker Posted December 10, 2016 Share Posted December 10, 2016 Interesting... the python script I'm running is a post-processing script to mount an ISO after downloading. For months, I was using this command to mount and it worked ok: subprocess.call(['/usr/bin/sudo', '/bin/mount', '-t', 'iso9660', '-o', 'loop', isoPath, tempdir]) To get sudo to work I had to copy a "sudoers" file into the container whenever SABNZBD was restarted, but this worked ok. After I applied the last sabnzbd update, I started getting the "sudo not found" error. So I removed the "sudo" part of the command and tried this: subprocess.call(['/bin/mount', '-t', 'iso9660', '-o', 'loop', isoPath, tempdir]) Now when the post-processing script runs, I see the following error in the SABNZBD log: mount: only root can use "--options" option I'm not exactly sure which account SABNZBD uses when it executes the post-processing scripts? Does it run with root privileges? Thanks - appreciate your thoughts! Quote Link to comment
sparklyballs Posted December 10, 2016 Share Posted December 10, 2016 Interesting... the python script I'm running is a post-processing script to mount an ISO after downloading. For months, I was using this command to mount and it worked ok: subprocess.call(['/usr/bin/sudo', '/bin/mount', '-t', 'iso9660', '-o', 'loop', isoPath, tempdir]) To get sudo to work I had to copy a "sudoers" file into the container whenever SABNZBD was restarted, but this worked ok. After I applied the last sabnzbd update, I started getting the "sudo not found" error. So I removed the "sudo" part of the command and tried this: subprocess.call(['/bin/mount', '-t', 'iso9660', '-o', 'loop', isoPath, tempdir]) Now when the post-processing script runs, I see the following error in the SABNZBD log: mount: only root can use "--options" option I'm not exactly sure which account SABNZBD uses when it executes the post-processing scripts? Does it run with root privileges? Thanks - appreciate your thoughts! sudo is not in the ubuntu:16.04 docker image which is the root base for our baseimage used in this docker image. sabnzbd runs as abc, a user created in our baseimage to be non root-privileged, so giving it root privileges would defeat the object. Quote Link to comment
gravymaker Posted December 11, 2016 Share Posted December 11, 2016 Thanks for confirming. I'll create a workaround. Quote Link to comment
dikkiedirk Posted December 22, 2016 Share Posted December 22, 2016 My watched folder doesn't seem to work like it used to be. I have several subfolders inside for different categories but when I put a nzb there it doesn't get loaded at all, like it used to. When I put a nzb in the root-folder, i.e. nzb, it only gets loaded after restarting sabnzbd. Is this a bug in sabnzbd 1.1.1 that is loaded now or is something else going on? Can I fix it myself or is there a work-around that doesn't involve a restart? Quote Link to comment
dikkiedirk Posted January 8, 2017 Share Posted January 8, 2017 SABNZB docker wont load any nzb from the watched folder anymore. I added 36 nzbs to SABNZB yesterday evening but the 37th wasn't added. the log shows many dirscanner crashes like pictured beneath. 2017-01-08 14:37:43,288::DEBUG::[__init__:1206] Test IPv6: Cannot reach IPv6 test host. Disabling IPv6 2017-01-08 14:37:43,288::DEBUG::[downloader:382] External IPv6 test result: False 2017-01-08 14:37:43,343::DEBUG::[downloader:398] SSL verification test: True Exception in thread Thread-9: Traceback (most recent call last): File "/usr/lib/python2.7/threading.py", line 801, in __bootstrap_inner self.run() File "/usr/share/sabnzbdplus/sabnzbd/dirscanner.py", line 328, in run self.scan() File "/usr/share/sabnzbdplus/sabnzbd/dirscanner.py", line 414, in scan run_dir(dirscan_dir, None) File "/usr/share/sabnzbdplus/sabnzbd/dirscanner.py", line 343, in run_dir if os.path.isdir(path) or path in self.ignored or filename[0] == '.': File "/usr/lib/python2.7/genericpath.py", line 49, in isdir st = os.stat(s) UnicodeEncodeError: 'ascii' codec can't encode character u'\xe8' in position 51: ordinal not in range(128) 2017-01-08 14:38:16,289::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:38:16,289::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:38:49,324::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:38:49,324::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:39:22,355::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:39:22,356::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:39:55,390::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:39:55,391::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:40:28,424::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:40:28,425::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:41:01,456::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:41:01,457::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:41:34,491::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:41:34,491::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:42:07,525::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:42:07,525::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:42:40,557::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:42:40,558::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:43:13,591::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:43:13,591::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:43:46,624::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:43:46,625::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:44:19,659::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:44:19,659::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:44:19,659::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:44:19,659::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:44:52,693::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:44:52,693::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab 2017-01-08 14:45:25,727::INFO::[__init__:1096] Restarting crashed dirscanner 2017-01-08 14:45:25,728::INFO::[__init__:994] Loading data for watched_data2.sab from /config/admin/watched_data2.sab Can the docker.img be full or is something corrupt? Can I somehow check this and clear this image? Or do I need to delete the image and rebuild my dockers? Can I keep my current configs? Off course I am only guessing, I can be on the wrong track. Quote Link to comment
Squid Posted January 8, 2017 Share Posted January 8, 2017 Can the docker.img be full or is something corrupt? Can I somehow check this and clear this image? Settings - Docker - Hit Advanced View Or do I need to delete the image and rebuild my dockers? Can I keep my current configs? Off course I am only guessing, I can be on the wrong track. You can try and delete the container (and image) by stopping Sab on the docker tab then deleting it. (And then re-adding it via the Apps Tab (Previous Apps). No adjustment of the template will be needed and everything will be back to normal after it re-downloads. Failing that, you're probably going to have to delete the appdata for Sab as it has gotten messed up (probably Sab's fault). Do the same steps as above, and then delete the appdata folder for sab, then reinstall it via the Previous Apps section. You won't need to touch the template, but you will have to setup all the settings within Sab's UI again. (Or switch to nzbGet -> better, lower footprint, and doesn't use Python which is a continuing problem for Sab) Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.