32 minutes ago, trurl said:

Might even get a clue where those numbers come from just by Computing the User Shares.

 

this the problem?

 

solved it, or should i you guys did

 

thank you

how would i go about submitting a docker creation request?

After an update to the Sab docker this morning, It appears that there is an error keeping it from starting up. I've tried removing the container completely, and re-creating it, but it still ends with the same error as posted below. Is anyone else running into this? My sab docker was working just fine before going to bed. 

2019-02-27 08:52:31,667::ERROR::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x150cfe541b90>>
Traceback (most recent call last):
  File "/usr/share/sabnzbdplus/cherrypy/process/wspbus.py", line 207, in publish
    output.append(listener(*args, **kwargs))
  File "/usr/share/sabnzbdplus/cherrypy/_cpserver.py", line 167, in start
    self.httpserver, self.bind_addr = self.httpserver_from_self()
  File "/usr/share/sabnzbdplus/cherrypy/_cpserver.py", line 158, in httpserver_from_self
    httpserver = _cpwsgi_server.CPWSGIServer(self)
  File "/usr/share/sabnzbdplus/cherrypy/_cpwsgi_server.py", line 64, in __init__
    self.server_adapter.ssl_certificate_chain)
  File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/ssl_builtin.py", line 56, in __init__
    self.context.load_cert_chain(certificate, private_key)
SSLError: [SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2779)

2019-02-27 08:52:31,769::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Serving on http://0.0.0.0:8080
2019-02-27 08:52:31,770::ERROR::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Shutting down due to error in start listener:
Traceback (most recent call last):
  File "/usr/share/sabnzbdplus/cherrypy/process/wspbus.py", line 245, in start
    self.publish('start')
  File "/usr/share/sabnzbdplus/cherrypy/process/wspbus.py", line 225, in publish
    raise exc
ChannelFailures: SSLError(336245134, u'[SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2779)')

2019-02-27 08:52:31,770::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus STOPPING
2019-02-27 08:52:31,773::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) shut down
2019-02-27 08:52:31,773::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE HTTP Server None already shut down
2019-02-27 08:52:31,774::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus STOPPED
2019-02-27 08:52:31,774::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus EXITING
2019-02-27 08:52:31,774::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus EXITED

 

4 hours ago, bb12489 said:

After an update to the Sab docker this morning, It appears that there is an error keeping it from starting up. I've tried removing the container completely, and re-creating it, but it still ends with the same error as posted below. Is anyone else running into this? My sab docker was working just fine before going to bed. 

2019-02-27 08:52:31,667::ERROR::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Error in 'start' listener <bound method Server.start of <cherrypy._cpserver.Server object at 0x150cfe541b90>>
Traceback (most recent call last):
  File "/usr/share/sabnzbdplus/cherrypy/process/wspbus.py", line 207, in publish
    output.append(listener(*args, **kwargs))
  File "/usr/share/sabnzbdplus/cherrypy/_cpserver.py", line 167, in start
    self.httpserver, self.bind_addr = self.httpserver_from_self()
  File "/usr/share/sabnzbdplus/cherrypy/_cpserver.py", line 158, in httpserver_from_self
    httpserver = _cpwsgi_server.CPWSGIServer(self)
  File "/usr/share/sabnzbdplus/cherrypy/_cpwsgi_server.py", line 64, in __init__
    self.server_adapter.ssl_certificate_chain)
  File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/ssl_builtin.py", line 56, in __init__
    self.context.load_cert_chain(certificate, private_key)
SSLError: [SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2779)

2019-02-27 08:52:31,769::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Serving on http://0.0.0.0:8080
2019-02-27 08:52:31,770::ERROR::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Shutting down due to error in start listener:
Traceback (most recent call last):
  File "/usr/share/sabnzbdplus/cherrypy/process/wspbus.py", line 245, in start
    self.publish('start')
  File "/usr/share/sabnzbdplus/cherrypy/process/wspbus.py", line 225, in publish
    raise exc
ChannelFailures: SSLError(336245134, u'[SSL: CA_MD_TOO_WEAK] ca md too weak (_ssl.c:2779)')

2019-02-27 08:52:31,770::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus STOPPING
2019-02-27 08:52:31,773::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('0.0.0.0', 8080)) shut down
2019-02-27 08:52:31,773::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE HTTP Server None already shut down
2019-02-27 08:52:31,774::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus STOPPED
2019-02-27 08:52:31,774::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus EXITING
2019-02-27 08:52:31,774::INFO::[_cplogging:219] [27/Feb/2019:08:52:31] ENGINE Bus EXITED

 

I'm seeing the same thing as well.  Found this when searching around:

 

https://forums.sabnzbd.org/viewtopic.php?t=23364

 

Started up normally after doing the following:

 

1.  Connected to the docker (my container name was "sabnzbd")

How to connect to a running Docker container?

There is a docker exec command that can be used to connect to a container that is already running.

Use docker ps to get the name of the existing container.

Use the command docker exec -it <container name> /bin/bash to get a bash shell in the container.

 

2.  cd /config/admin

 

3.  mv server.cert server.cert.old (or delete it, but I was trying to play it safe)

 

4.  mv server.key server.key.old (or delete it, but again playing it safe)

 

I did an ls-al then and saw that the server.cert was immediately recreated but not the server.key

I checked SAB and it was then running normally

Edited February 27, 20197 yr by jcouch93
Added steps when I tried to fix

3 hours ago, jcouch93 said:

I'm seeing the same thing as well.  Found this when searching around:

 

https://forums.sabnzbd.org/viewtopic.php?t=23364

 

I haven't tried it yet.  Hoping someone comes up with a solution here.

This helped! I deleted the server and cert files from my appdata/sabnzbd/admin/ directory. Started up normally. 

 

Thanks!

Just had the same problem, and deleting the server.key/server.cert in `appdata/sabnzbd/admin` worked for me too 👍 

Lifesaver, worked for me also !

On 2/27/2019 at 1:49 PM, JustinAiken said:

Just had the same problem, and deleting the server.key/server.cert in `appdata/sabnzbd/admin` worked for me too 👍 

Same, thank you jcouch93

I'm having trouble I'm hoping someone can help me with. I had everything set up and working well, then all of a sudden within the last couple of weeks nothing seems to be downloading and the speed shows as 0 KB/s. If I reset the docker it will usually start at a very low speed, around 10 KB/s, then slows down until it eventually stops. I've read through this whole topic and searched the internet and haven't found any help. I've changed VPN servers, and deleted and reinstalled the docker, neither of which worked. My other dockers don't have any trouble connecting through the same VPN and testing the speed at Speedtest.net through the VPN results in consistant speeds around 100 Mbps. Any help would be greatly appreciated. Thanks!

8 minutes ago, rsendi said:

hoping someone can help me

https://forums.unraid.net/topic/57181-real-docker-faq/#comment-564345

 

My apologizes I missed that. 

 

Here is my run command:

 

 

This is the log taken from the Docker tab in Unraid: log.txt

 

And this is the log from SABnzbd itself: sabnzbd.log

 

I noticed as I was saving these logs to submit them here the failure to connect errors, those are new and they hadn't shown up in the logs previously.

On 2/23/2019 at 8:41 PM, steve1977 said:

Sabnzbd docker seems to work, but shows "Cannot create backup file for /config/sabnzbd.ini.bak" everytime I start/restart the docker. Any thoughts?

 

I am still facing the issue and it even seems to increase in frequency. It now seems to show up all the time. Any thoughts?

 

2019-04-04 20:55:22,638::INFO::[config:848] Traceback:
Traceback (most recent call last):
File "/usr/share/sabnzbdplus/sabnzbd/config.py", line 844, in save_config
shutil.copymode(filename, bakname)
File "/usr/lib/python2.7/shutil.py", line 105, in copymode
os.chmod(dst, mode)
OSError: [Errno 1] Operation not permitted: '/config/sabnzbd.ini.bak'
2019-04-04 20:55:55,690::ERROR::[config:847] Cannot create backup file for /config/sabnzbd.ini.bak

Edited April 4, 20197 yr by steve1977

2 hours ago, steve1977 said:

 

I am still facing the issue and it even seems to increase in frequency. It now seems to show up all the time. Any thoughts?

 

2019-04-04 20:55:22,638::INFO::[config:848] Traceback:
Traceback (most recent call last):
File "/usr/share/sabnzbdplus/sabnzbd/config.py", line 844, in save_config
shutil.copymode(filename, bakname)
File "/usr/lib/python2.7/shutil.py", line 105, in copymode
os.chmod(dst, mode)
OSError: [Errno 1] Operation not permitted: '/config/sabnzbd.ini.bak'
2019-04-04 20:55:55,690::ERROR::[config:847] Cannot create backup file for /config/sabnzbd.ini.bak

Can you run ls -la inside the appdata folder and in the parent folder of the appdata folder of sabnzb? 

8 hours ago, saarg said:

Can you run ls -la inside the appdata folder and in the parent folder of the appdata folder of sabnzb? 

Not sure which one is the appdata folder? I ran the command in my sabnzbd docker folder. Please see below:

 

root@Tower:/mnt/disks/nvme/Docker/sabnzbd# ls -la
total 24
drwxrwxrwx 7 nobody users  121 Feb 24 10:12 ./
drwxrwxrwx 8 root   root   123 Mar 31 07:58 ../
drwxrwxrwx 6 nobody users   64 Mar 31 09:35 Complete/
drwxrwxrwx 4 nobody users  126 Apr  5 07:20 Incomplete/
drwxrwxrwx 3 root   root   144 Apr  5 07:20 admin/
drwxrwxrwx 2 root   root   130 Apr  3 08:57 logs/
-rw-rw-rw- 1 root   root  8441 Feb 23 18:27 sabnzbd.ini
-rw-rw-rw- 1 root   root  8441 Apr  5 07:58 sabnzbd.ini.bak
drwxrwxrwx 4 root   root    30 Feb 23 18:27 wanted/
 

7 hours ago, steve1977 said:

Not sure which one is the appdata folder? I ran the command in my sabnzbd docker folder. Please see below:

 

root@Tower:/mnt/disks/nvme/Docker/sabnzbd# ls -la
total 24
drwxrwxrwx 7 nobody users  121 Feb 24 10:12 ./
drwxrwxrwx 8 root   root   123 Mar 31 07:58 ../
drwxrwxrwx 6 nobody users   64 Mar 31 09:35 Complete/
drwxrwxrwx 4 nobody users  126 Apr  5 07:20 Incomplete/
drwxrwxrwx 3 root   root   144 Apr  5 07:20 admin/
drwxrwxrwx 2 root   root   130 Apr  3 08:57 logs/
-rw-rw-rw- 1 root   root  8441 Feb 23 18:27 sabnzbd.ini
-rw-rw-rw- 1 root   root  8441 Apr  5 07:58 sabnzbd.ini.bak
drwxrwxrwx 4 root   root    30 Feb 23 18:27 wanted/
 

That said enough for me. 

You have permission errors. The files should not be owned by root, but by nobody:users. 

I remember you have had permission issues before also, so wondering what you are doing? 

 

Best thing is to just start with a new fresh appdata folder. 

Thanks. Let me reset the permissions first. What’s the command?

I ran chmod -R 777. Still a permission issue, but different result of ls -la:

 

-rwxrwxrwx 1 root   root  8441 Feb 23 18:27 sabnzbd.ini*
-rwxrwxrwx 1 root   root  8441 Apr  5 17:05 sabnzbd.ini.bak*
 

1 hour ago, steve1977 said:

I ran chmod -R 777. Still a permission issue, but different result of ls -la:

 

-rwxrwxrwx 1 root   root  8441 Feb 23 18:27 sabnzbd.ini*
-rwxrwxrwx 1 root   root  8441 Apr  5 17:05 sabnzbd.ini.bak*
 

Still root. Look at chown and chgrp.

 

Even better: 

Quote

Best thing is to just start with a new fresh appdata folder. 

 

Edited April 5, 20197 yr by Rick Gillyon

16 minutes ago, Rick Gillyon said:

Still root. Look at chown and chgrp.

Can you say a few more words what to do with these two commands?

Any thoughts on above?

If a new appdate is the only way, how would I go ahead with it without losing all dockers / settings?

1 hour ago, steve1977 said:

Any thoughts on above?

If a new appdate is the only way, how would I go ahead with it without losing all dockers / settings?

I'm talking about only the appdata folder for this container. 

 

Have you read through the docker FAQ to get a better understanding about how dockers work on unraid? 

I've been noticing that this sabnzbd container might not be following the CPU Pinning Docker rules exactly. CPU usage on CPU 3 goes to 5-6% during downloads and back down to 0% when done. All of my other dockers are pinned to 0,4. All my VM's are pinned to 1,5,2,6,3,7 but they are all shutdown. Seems to only happen with sabnzbd is actively downloading something. Anyone else experience anything like this?

 

 

 

 

2 hours ago, remati said:

I've been noticing that this sabnzbd container might not be following the CPU Pinning Docker rules exactly. CPU usage on CPU 3 goes to 5-6% during downloads and back down to 0% when done. All of my other dockers are pinned to 0,4. All my VM's are pinned to 1,5,2,6,3,7 but they are all shutdown. Seems to only happen with sabnzbd is actively downloading something. Anyone else experience anything like this?

 

 

 

 

Easiest way to tell what's going on (ie: if it's actually Sab) is to install cAdvisor.  (In this case, cAd is easy to see the results than netdata)