Jump to content
binhex

[Support] binhex - Sickbeard

43 posts in this topic Last Reply

Recommended Posts

Overview: Support for Docker image arch-sickbeard in the binhex repo.

Application: Sick Beard- http://sickbeard.com/

Docker Hub: https://hub.docker.com/r/binhex/arch-sickbeard/

GitHub: https://github.com/binhex/arch-sickbeard

 

If you appreciate my work, then please consider buying me a beer  :D

 

btn_donate_SM.gif

 

For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

Edited by binhex

Share this post


Link to post

Just updated to the latest Binhex Sickbeard and Sabnzbd and now neither will start.  Both had been working flawlessly since install...

 

Binhex Deluge also update, but it still seems to start OK...

 

Sickbeard Log file

 

016-02-21 19:56:41,032 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2016-02-21 19:56:41,032 DEBG 'sickbeard' stderr output:

File "/usr/lib/sickbeard/SickBeard.py", line 323, in main

sickbeard.initialize(consoleLogging=consoleLogging)

File "/usr/lib/sickbeard/sickbeard/__init__.py", line 681, in initialize

logger.sb_log_instance.initLogging(consoleLogging=consoleLogging)

File "/usr/lib/sickbeard/sickbeard/logger.py", line 99, in initLogging

self.cur_handler = self._config_handler()

File "/usr/lib/sickbeard/sickbeard/logger.py", line 111, in _config_handler

file_handler = logging.FileHandler(self.log_file_path, encoding='utf-8')

File "/usr/lib/python2.7/logging/__init__.py", line 905, in __init__

 

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

StreamHandler.__init__(self, self._open())

File "/usr/lib/python2.7/logging/__init__.py", line 937, in _open

 

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

stream = codecs.open(self.baseFilename, self.mode, self.encoding)

File "/usr/lib/python2.7/codecs.py", line 896, in open

 

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

file = __builtin__.open(filename, mode, buffering)

IOError:

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

[Errno 13] Permission denied: '/config/Logs/sickbeard.log'

 

2016-02-21 19:56:41,049 DEBG fd 8 closed, stopped monitoring (stderr)>

2016-02-21 19:56:41,049 DEBG fd 6 closed, stopped monitoring (stdout)>

2016-02-21 19:56:41,049 INFO exited: sickbeard (exit status 1; not expected)

2016-02-21 19:56:41,050 DEBG received SIGCLD indicating a child quit

2016-02-21 19:56:42,051 INFO gave up: sickbeard entered FATAL state, too many start retries too quickly

Share this post


Link to post

Just updated to the latest Binhex Sickbeard and Sabnzbd and now neither will start.  Both had been working flawlessly since install...

 

Binhex Deluge also update, but it still seems to start OK...

 

Sickbeard Log file

 

016-02-21 19:56:41,032 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2016-02-21 19:56:41,032 DEBG 'sickbeard' stderr output:

File "/usr/lib/sickbeard/SickBeard.py", line 323, in main

sickbeard.initialize(consoleLogging=consoleLogging)

File "/usr/lib/sickbeard/sickbeard/__init__.py", line 681, in initialize

logger.sb_log_instance.initLogging(consoleLogging=consoleLogging)

File "/usr/lib/sickbeard/sickbeard/logger.py", line 99, in initLogging

self.cur_handler = self._config_handler()

File "/usr/lib/sickbeard/sickbeard/logger.py", line 111, in _config_handler

file_handler = logging.FileHandler(self.log_file_path, encoding='utf-8')

File "/usr/lib/python2.7/logging/__init__.py", line 905, in __init__

 

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

StreamHandler.__init__(self, self._open())

File "/usr/lib/python2.7/logging/__init__.py", line 937, in _open

 

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

stream = codecs.open(self.baseFilename, self.mode, self.encoding)

File "/usr/lib/python2.7/codecs.py", line 896, in open

 

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

file = __builtin__.open(filename, mode, buffering)

IOError:

2016-02-21 19:56:41,033 DEBG 'sickbeard' stderr output:

[Errno 13] Permission denied: '/config/Logs/sickbeard.log'

 

2016-02-21 19:56:41,049 DEBG fd 8 closed, stopped monitoring (stderr)>

2016-02-21 19:56:41,049 DEBG fd 6 closed, stopped monitoring (stdout)>

2016-02-21 19:56:41,049 INFO exited: sickbeard (exit status 1; not expected)

2016-02-21 19:56:41,050 DEBG received SIGCLD indicating a child quit

2016-02-21 19:56:42,051 INFO gave up: sickbeard entered FATAL state, too many start retries too quickly

 

there was a permissions issue, can you stop both sickbeard and sabnzbd and delete perms.txt from both /config folders then upgrade the containers via unraid webui and start them both again, let me know how you get on.

Share this post


Link to post

there was a permissions issue, can you stop both sickbeard and sabnzbd and delete perms.txt from both /config folders then upgrade the containers via unraid webui and start them both again, let me know how you get on.

 

That did the trick and I'm back in business on both!  Thanks for the quick reply... as always, great work with your UnRaid Docker Apps!

 

-SW2

Share this post


Link to post

there was a permissions issue, can you stop both sickbeard and sabnzbd and delete perms.txt from both /config folders then upgrade the containers via unraid webui and start them both again, let me know how you get on.

 

That did the trick and I'm back in business on both!  Thanks for the quick reply... as always, great work with your UnRaid Docker Apps!

 

-SW2

glad its working again, thanks for letting me know.

Share this post


Link to post

Hate to be a bother but I'm getting the same issue with sickbeard. Since updating last night I can't even open the web ui. Have tried deleting the perm files for both sickbeard and sab

Share this post


Link to post

Same issue here.

 

I am completely new to dockers so I'm sure its me.

 

I installed Plex, and binhex's sab and sb dockers (thanks man).  I am having all sorts of issues I will eventually begin to address, but am just trying to log into each app so transfer over settings.  I can't connect to sickbeard at all.  Its running bridged.  I deleted the perms.txt file and restarted the docker, no effect.

 

Log:

 

2017-01-24 00:36:20,572 CRIT Set uid to user 0

2017-01-24 00:36:20,573 INFO Included extra file "/etc/supervisor/conf.d/sickbeard.conf" during parsing

2017-01-24 00:36:20,575 INFO supervisord started with pid 14

2017-01-24 00:36:21,580 INFO spawned: 'sickbeard' with pid 17

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

raise error

 

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:21,849 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317784848 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:21,849 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317784488 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:21,849 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:21,849 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:22,851 INFO spawned: 'sickbeard' with pid 23

2017-01-24 00:36:23,022 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:23,047 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:23,047 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317785136 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:23,047 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:23,047 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:23,022 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:23,047 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:23,047 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317785136 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:23,047 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:23,047 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:25,050 INFO spawned: 'sickbeard' with pid 29

2017-01-24 00:36:25,232 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:25,232 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:25,233 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:25,253 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:25,253 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317784488 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:25,253 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:25,253 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:25,050 INFO spawned: 'sickbeard' with pid 29

2017-01-24 00:36:25,232 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:25,232 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:25,233 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:25,253 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:25,253 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317784488 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:25,253 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:25,253 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:28,257 INFO spawned: 'sickbeard' with pid 35

2017-01-24 00:36:28,434 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

 

2017-01-24 00:36:28,435 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:28,435 DEBG 'sickbeard' stderr output:

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:28,456 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:28,456 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317785136 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:28,456 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:28,457 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:29,458 INFO gave up: sickbeard entered FATAL state, too many start retries too quickly

Share this post


Link to post

Same issue here.

 

I am completely new to dockers so I'm sure its me.

 

I installed Plex, and binhex's sab and sb dockers (thanks man).  I am having all sorts of issues I will eventually begin to address, but am just trying to log into each app so transfer over settings.  I can't connect to sickbeard at all.  Its running bridged.  I deleted the perms.txt file and restarted the docker, no effect.

 

Log:

 

2017-01-24 00:36:20,572 CRIT Set uid to user 0

2017-01-24 00:36:20,573 INFO Included extra file "/etc/supervisor/conf.d/sickbeard.conf" during parsing

2017-01-24 00:36:20,575 INFO supervisord started with pid 14

2017-01-24 00:36:21,580 INFO spawned: 'sickbeard' with pid 17

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

raise error

 

 

2017-01-24 00:36:21,828 DEBG 'sickbeard' stderr output:

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:21,849 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317784848 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:21,849 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317784488 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:21,849 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:21,849 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:22,851 INFO spawned: 'sickbeard' with pid 23

2017-01-24 00:36:23,022 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:23,047 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:23,047 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317785136 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:23,047 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:23,047 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:23,022 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:23,022 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:23,047 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:23,047 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317785136 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:23,047 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:23,047 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:25,050 INFO spawned: 'sickbeard' with pid 29

2017-01-24 00:36:25,232 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:25,232 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:25,233 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:25,253 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:25,253 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317784488 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:25,253 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:25,253 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:25,050 INFO spawned: 'sickbeard' with pid 29

2017-01-24 00:36:25,232 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:25,232 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

 

2017-01-24 00:36:25,233 DEBG 'sickbeard' stderr output:

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:25,253 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:25,253 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317784488 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:25,253 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:25,253 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:28,257 INFO spawned: 'sickbeard' with pid 35

2017-01-24 00:36:28,434 DEBG 'sickbeard' stderr output:

Traceback (most recent call last):

File "/usr/lib/sickbeard/SickBeard.py", line 403, in <module>

 

2017-01-24 00:36:28,435 DEBG 'sickbeard' stdout output:

Starting up Sick Beard 507

 

2017-01-24 00:36:28,435 DEBG 'sickbeard' stderr output:

main()

File "/usr/lib/sickbeard/SickBeard.py", line 320, in main

sickbeard.CFG = ConfigObj(sickbeard.CONFIG_FILE)

File "/usr/lib/sickbeard/lib/configobj.py", line 1219, in __init__

self._load(infile, configspec)

File "/usr/lib/sickbeard/lib/configobj.py", line 1302, in _load

raise error

 

lib.configobj.ConfigObjError: Parsing failed with several errors.

 

First error at line 209.

 

 

2017-01-24 00:36:28,456 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47714317846504 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stderr)>

2017-01-24 00:36:28,456 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47714317785136 for <Subprocess at 47714317784344 with name sickbeard in state STARTING> (stdout)>

2017-01-24 00:36:28,456 INFO exited: sickbeard (exit status 1; not expected)

2017-01-24 00:36:28,457 DEBG received SIGCLD indicating a child quit

2017-01-24 00:36:29,458 INFO gave up: sickbeard entered FATAL state, too many start retries too quickly

 

are you migrating your configuration over to this docker container?, if so its possible the version of sickbeard you were using is either a lot older or a lot newer than this version. to verify this is the cause of the problem just try with no files in the /config path (host side obviously), restart the docker container and see if it starts up ok.

 

btw not sure if you are aware but most poeple have moved away from sickbeard and onto either sickrage or sonarr now, sickbeard is getting a bit old, thus the lack of posts here.

Share this post


Link to post

Well, that was it.  I moved all three ".db" files, restarted the container, and its up.  However, my media collection is very large, and I was hoping not to have to spend hours manually re-adding each show.

Share this post


Link to post

And now SB can't search to find shows, appears it doesn't have network connectivity.

Share this post


Link to post

And now SB can't search to find shows, appears it doesn't have network connectivity.

 

if your host can connect to the internet then SB will also be able to do so, there is no fire walling or anything clever happening here, can you check that you can connect to tvdb etc from a machine on your lan?.

 

It is of course possible that tvdb etc have changed their API and SB is now out of date and thus cannot now search and find metadata, but i can assure you SB will have network connectivity. I feel your pain for adding in hundreds of shows etc, if your going to have to go through that pain i would really encourage you to take the time and evaluate switching to sonarr/sickrage, as both of these are being actively worked on, sickbeard is a dying project, sooner or later there will be a change on the indexers/metadata sites that then renders sickbeard useless, and with no development going on it wont be fixed, its your choice of course, but i know what i would do :-).

 

edit - i feel like i should also mention the new fork of sickrage named medusa, i didnt mention this as its a VERY new fork and thus stuff may not work yet, so for now i think sonarr or sickrage are your best bet, if your willing to have a small learning curve.

Share this post


Link to post

binhex THANK YOU for your help.

 

I am now using (learning) sickrage.  So far I am having major trouble adding shows (some are found, most are not, maybe its a tvdb issue), and a few shows have made it to Sab to download.  But now I am having what I believe are permissions issues trying to write to the share.  Again, content is stored on Server1, sab/sb are running on Server2, mounts are via cifs done in the go script.

Share this post


Link to post

binhex THANK YOU for your help.

 

I am now using (learning) sickrage.  So far I am having major trouble adding shows (some are found, most are not, maybe its a tvdb issue), and a few shows have made it to Sab to download.  But now I am having what I believe are permissions issues trying to write to the share.  Again, content is stored on Server1, sab/sb are running on Server2, mounts are via cifs done in the go script.

 

ok so sabnzbd running on Server2 (im assuming another docker container right?) is having issues writing to a share on Server1 right?,  if so you need to verify that user "nobody" group "users" has read, write, and possibly execute at a file permissions level, and that the share is set to allow user "nobody" group "users" (set to "public" to allow all users to connect).

 

Share this post


Link to post

drwxrwxrwx  1 nobody users 7000 Jan 24 01:45 movies/

drwxrwxrwx  1 nobody users  96 Jan 23 06:07 music/

drwxrwxrwx  1 nobody users 8408 Jan 25 03:53 tv_shows/

 

 

 

Confirmed.  The shares (in the GUI) are set to Private, with only two users having rear/write permissions (the 'nobody' user is of course not listed there).

 

 

Share this post


Link to post

drwxrwxrwx  1 nobody users 7000 Jan 24 01:45 movies/

drwxrwxrwx  1 nobody users  96 Jan 23 06:07 music/

drwxrwxrwx  1 nobody users 8408 Jan 25 03:53 tv_shows/

 

 

 

Confirmed.  The shares (in the GUI) are set to Private, with only two users having rear/write permissions (the 'nobody' user is of course not listed there).

 

the share permission looks to be the issue then, add in user nobody and/or group users and you should be set.

Share this post


Link to post

I'm sorry for the confusion, but where?  Add the 'nobody' user in the unraid GUI?  Did this and the user does not appear in the list of users under "User Access" for the share.

Share this post


Link to post
The shares (in the GUI) are set to Private, with only two users having rear/write permissions

 

wherever your seeing the two users listed, add in user nobody as your third user.

 

if user nobody isnt permitted then you have two options:-

 

1. ditch share permissions and use file based permissions only - this is the normal approach, most people dont bother having the cross matrix headache of share and file permissions, if you want to do this then set the share permissions to "public".

 

2. change the account that sabnzbdvpn runs as to match one of the two accounts with permissions, to do this issue the following command at unraid ssh command prompt:-

 

id <the username>

 

this wll output the UID and GID for the username, then change the PUID and GUID values in the unraid webui for this docker to match the outputted values, you will also then need to delete the file /config/perms.txt, then finally restart the docker, this will then allow the docker to run as another user, make sure you also change file based permissions too to match the account.

 

Share this post


Link to post

Thank you for the reply!

 

I am now running sickgear (if there is a separate thread for support, my apologies).

 

I have this in my /boot/config/go script:

 

mount -t cifs //192.168.0.4/movies /mnt/movies -o username=plex,password=PLEXUSERSPASSWORD

mount -t cifs //192.168.0.4/music /mnt/music -o username=plex,password=PLEXUSERSPASSWORD

mount -t cifs //192.168.0.4/tv_shows /mnt/tv_shows -o username=plex,password=PLEXUSERSPASSWORD

 

The "plex" user has the same username and password on both unraid servers.  I can successfully map from Server1 (content) to Server2 (dockers running).  I am running sickgear and sabnzbd as user "plex" as per your instructions.  However, when I try to add a show in sickgear, it specifically tells me it cannot create the directory.  I know this is a permissions issue, I just can't figure out out.

 

The "tv_shows" share on 192.168.0.4 (Server1) allows read/write for user "plex"

 

Share this post


Link to post

Thank you for the reply!

 

I am now running sickgear (if there is a separate thread for support, my apologies).

 

I have this in my /boot/config/go script:

 

mount -t cifs //192.168.0.4/movies /mnt/movies -o username=plex,password=PLEXUSERSPASSWORD

mount -t cifs //192.168.0.4/music /mnt/music -o username=plex,password=PLEXUSERSPASSWORD

mount -t cifs //192.168.0.4/tv_shows /mnt/tv_shows -o username=plex,password=PLEXUSERSPASSWORD

 

The "plex" user has the same username and password on both unraid servers.  I can successfully map from Server1 (content) to Server2 (dockers running).  I am running sickgear and sabnzbd as user "plex" as per your instructions.  However, when I try to add a show in sickgear, it specifically tells me it cannot create the directory.  I know this is a permissions issue, I just can't figure out out.

 

The "tv_shows" share on 192.168.0.4 (Server1) allows read/write for user "plex"

 

did you do this? :-

 

2. change the account that sabnzbdvpn runs as to match one of the two accounts with permissions, to do this issue the following command at unraid ssh command prompt:-

 

Code: [select]

id <the username>

 

this wll output the UID and GID for the username, then change the PUID and GUID values in the unraid webui for this docker to match the outputted values, you will also then need to delete the file /config/perms.txt, then finally restart the docker, this will then allow the docker to run as another user, make sure you also change file based permissions too to match the account.

 

also its SickRage not Sickgear lol

 

 

there is a support thread so if we can carry this on there that would be great:- http://lime-technology.com/forum/index.php?topic=45847.0

 

 

Share this post


Link to post

OK as there hasn't been a release for Sickbeard in months/years and there are much better alternatives now, i am looking to remove this docker, any serious objections to this?.

 

Better alternatives are:-

 

[support] Sickrage

[support] Medusa

[support] Sonarr

Share this post


Link to post
6 hours ago, binhex said:

OK as there hasn't been a release for Sickbeard in months/years and there are much better alternatives now, i am looking to remove this docker, any serious objections to this?.

 

Better alternatives are:-

 

[support] Sickrage

[support] Medusa

[support] Sonarr

Over a year since the last commit...

 

It can be deprecated instead.  Would stop new installs, but still allow existing users to reinstall if need be.

Share this post


Link to post
Over a year since the last commit...
 
It can be deprecated instead.  Would stop new installs, but still allow existing users to reinstall if need be.


I'm assuming the deprecation would be something you can only do for CA right?

Sent from my SM-G900F using Tapatalk

Share this post


Link to post

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now