Sickbeard Install Issue and Startup Issue

180 views
Skip to first unread message

Jason Stockley

unread,
Jul 12, 2014, 4:15:04 PM7/12/14
to al...@googlegroups.com
When trying to install sickbeard and run it, Im having problems.

1.
1st on the install Im receiving the error below:

nstalling sickbeard (2012-12-14-1) to /Alt-F...
Configuring davfs2
addgroup: gid '202' in use
adduser: unknown group davfs2
postinst script returned status 1
ERROR: davfs2.postinst returned 1
Configuring sickbeard
Resolving github.com... 192.30.252.130
Connecting to github.com|192.30.252.130|:443... connected.
HTTP request sent, awaiting response... 302 Found

2.
Then when trying to start sickbeard Im getting the error:

I'm more than happy to provide any logs to anyone that can help, however you may have to guide me into finding these.

I have tried removing sickbeard and installing it again, but still get both errors.

Thanks
J

João Cardoso

unread,
Jul 12, 2014, 6:52:03 PM7/12/14
to al...@googlegroups.com


On Saturday, July 12, 2014 9:15:04 PM UTC+1, Jason Stockley wrote:
When trying to install sickbeard and run it, Im having problems.

I can partially reproduce the issue, with a different error.

First I installed and started SickBeard from my current build, in my local network, without any issue.

Then, as you had obviously an error, it could be the a release error, so I remove all packages and re-installed sickbeard from sourceforge. And I got a different error:

Starting SickBeard.py: Traceback (most recent call last):
  File "/opt/SickBeard/SickBeard.py", line 403, in <module>
    main()
  File "/opt/SickBeard/SickBeard.py", line 323, in main
    sickbeard.initialize(consoleLogging=consoleLogging)
  File "/opt/SickBeard/sickbeard/__init__.py", line 695, in initialize
    tmp_provider.set_config(cur_metadata_config)
  File "/opt/SickBeard/sickbeard/metadata/generic.py", line 113, in set_config
    self.season_posters = config_list[6]
IndexError: list index out of range
Fail.
 
This is going to take time to uncover, and I can't look at it before next Wednesday.

In your case the issue seems to be related to sqlite, can you try to use other package that also needs sqlite, such as mediatomb, minidlna, sabnzbd (which also uses python)...

Your error also says "File not found", so are sqlite and sqlite-libs correctly installed?

The output of 'ls -l /usr/lib/libsqlite3.*' should be:

lrwxrwxrwx    1 root     root            19 Jul 12 23:17 /usr/lib/libsqlite3.so -> libsqlite3.so.0.8.6
lrwxrwxrwx    1 root     root            19 Jul 12 23:17 /usr/lib/libsqlite3.so.0 -> libsqlite3.so.0.8.6
-rwxr-xr-x    1 root     root        657140 Jun 24 14:27 /usr/lib/libsqlite3.so.0.8.6

and the output of  'ldd /usr/bin/sqlite3' should be:

        libsqlite3.so.0 => /usr/lib/libsqlite3.so.0 (0xb6e82000)
        libreadline.so.6 => /usr/lib/libreadline.so.6 (0xb6e44000)
        libncurses.so.5 => /usr/lib/libncurses.so.5 (0xb6e06000)
        libdl.so.0 => /lib/libdl.so.0 (0xb6dfc000)
        libpthread.so.0 => /lib/libpthread.so.0 (0xb6de3000)
        libc.so.0 => /lib/libc.so.0 (0xb6d82000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xb6d6f000)
        ld-uClibc.so.0 => /lib/ld-uClibc.so.0 (0xb6f2b000)

If it is not, stop all processes, uninstall sqlite and sqlite-libs and reinstall them.
Meanwhile you have to wait. But see bellow.


1.
1st on the install Im receiving the error below:

nstalling sickbeard (2012-12-14-1) to /Alt-F...
Configuring davfs2
addgroup: gid '202' in use
adduser: unknown group davfs2
postinst script returned status 1
ERROR: davfs2.postinst returned 1

davfs2 is not required for sickbeard. It should be an unfinished install of some other package.
davfs2 install script tries to create a davfs2 user/group, and that fails, as the '202' group seems to already exists. Did you create it?
Try solving this first.
 
Configuring sickbeard
Resolving github.com... 192.30.252.130
Connecting to github.com|192.30.252.130|:443... connected.
HTTP request sent, awaiting response... 302 Found

2.
Then when trying to start sickbeard Im getting the error:

I'm more than happy to provide any logs to anyone that can help, however you may have to guide me into finding these.

I have tried removing sickbeard and installing it again, but still get both errors.

It must be another packages. Sickbeard depends on:

bzip2 1.0.6
cheetah 2.4.4-1
db 4.8.30-3
expat 2.0.1-4
gdbm 1.8.3-4
gettext 0.16.1-1
git 1.7.7-2
groff 1.21-1
libcurl 7.22.0-2
ncurses 5.9
perl 5.16.0-3
pyopenssl 0.11-1
python 2.7.2-3
readline 6.2
sickbeard 2012-12-14-1
sqlite 3080200
sqlite-libs 3080200

Any of these can cause the issue (but sqlite-libs is the most probable one)


Thanks
J

Jason Stockley

unread,
Jul 12, 2014, 7:36:23 PM7/12/14
to al...@googlegroups.com
Thank you for the super speedy response, Ill try all you suggested and report back :-)

Thanks again.

Jason Stockley

unread,
Jul 12, 2014, 11:29:12 PM7/12/14
to
OK I've got a it further, but still havent managed to get it working yet.

So I removed sickbeard from ALT F, 

I then deleted the files in: /var/lib/sickbeard


and the config file

I then deleted the group causing the earlier error during install of sickbeard.

davfs2 install script tries to create a davfs2 user/group, and that fails, as the '202' group seems to already exists. Did you create it?
Try solving this first.


I then forced a install of :libsqlite3 using:

   cd /tmp
   ipkg -force-depends remove libsqlite3
   ipkg install sqlite-libs_3080200_arm.ipk
   rm  sqlite-libs_3080200_arm.ipk

Log:

[root@NAS]#    ipkg -force-depends remove libsqlite3
No packages removed.
Nothing to be done
Successfully terminated.
/sqlite-libs_3080200_arm.ipk
Resolving sourceforge.net... 216.34.181.60
Connecting to sourceforge.net|216.34.181.60|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Connecting to sourceforge.net|216.34.181.60|:80... connected.
HTTP request sent, awaiting response... 302 Found
HTTP request sent, awaiting response... 302 Found
HTTP request sent, awaiting response... 302 Found
Resolving skylink.dl.sourceforge.net... 109.230.212.53
Connecting to skylink.dl.sourceforge.net|109.230.212.53|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 364702 (356K) [application/octet-stream]
Saving to: 'sqlite-libs_3080200_arm.ipk'

100%[======================================>] 364,702      560KB/s   in 0.6s

2014-07-13 04:13:48 (560 KB/s) - 'sqlite-libs_3080200_arm.ipk' saved [364702/364702]

[root@NAS]#    ipkg install sqlite-libs_3080200_arm.ipk
Installing sqlite-libs (3080200) to /Alt-F...
Configuring sqlite-libs
Successfully terminated.
[root@NAS]#    rm  sqlite-libs_3080200_arm.ipk

And then finally re-installed sickbeard.

The errors from earlier have now gone :-) so doing this has sorted out the earlier issues.

But now im getting the same error as you.


Ive looked through the sickbeard db, and cant see any issues there but all looks ok :


So my thoughts are the issue could be in the sickbeard package itself? 

Ive tried to include as much info as possible but Im new to all this, so i may have missed something.

Cheers
J

João Cardoso

unread,
Jul 16, 2014, 5:52:11 PM7/16/14
to al...@googlegroups.com


On Sunday, July 13, 2014 4:29:12 AM UTC+1, Jason Stockley wrote:
OK I've got a it further, but still havent managed to get it working yet.

So I removed sickbeard from ALT F, 

I then deleted the files in: /var/lib/sickbeard

From the screen shots I understand that you defined someting like a Volume_1 Samba share , which exposes the Alt-F folder.
That, as the README.txt file says:

DON'T ADD, REMOVE OR MODIFY ANY FILE IN THIS DIRECTORY
OR ANY OF ITS SUB-DIRECTORIES, OR THE SYSTEM MIGHT HANG!

Even if you don't deliberately change anything, you don't know what does Samba/Windoew under the table.
I strongly advise you against that setup. Instead, define shares for the folders that matters.

(...)


I then deleted the group causing the earlier error during install of sickbeard.

davfs2 install script tries to create a davfs2 user/group, and that fails, as the '202' group seems to already exists. Did you create it?
Try solving this first.


I then forced a install of :libsqlite3 using:

   cd /tmp
   ipkg -force-depends remove libsqlite3
   wget http://sourceforge.net/projects/alt-f/files/pkgs/unstable/sqlite-libs_3080200_arm.ipk
   ipkg install sqlite-libs_3080200_arm.ipk
   rm  sqlite-libs_3080200_arm.ipk

You could as well do (as indicated in another thread)
ipkg -force-reinstall install sqlite-libs

And you don't need to download the ipkg files, 'ipkg install pkg-name' will download, install the package and remove the downloads
(...)

And then finally re-installed sickbeard.

The errors from earlier have now gone :-) so doing this has sorted out the earlier issues.

But now im getting the same error as you.

Ive looked through the sickbeard db, and cant see any issues there but all looks ok :

(...)


So my thoughts are the issue could be in the sickbeard package itself? 

I also tought of that. But that wouldn't explain why my last local pkgs build runs sickbeard OK.
I also though in downloading one of the sickbeard's author builds (https://github.com/midgetspy/Sick-Beard/releases) and install it instead of "master", eg, build 505 https://github.com/midgetspy/Sick-Beard/archive/build-505.tar.gz

Can you try that?
I'm pretty busy enjoying my holidays :-)


Ive tried to include as much info as possible but Im new to all this, so i may have missed something.

Thanks.
 

Cheers
J

Jason Stockley

unread,
Jul 19, 2014, 5:01:49 PM7/19/14
to al...@googlegroups.com
I would have a go at :


I also tought of that. But that wouldn't explain why my last local pkgs build runs sickbeard OK.
I also though in downloading one of the sickbeard's author builds (https://github.com/midgetspy/Sick-Beard/releases) and install it instead of "master", eg, build 505 https://github.com/midgetspy/Sick-Beard/archive/build-505.tar.gz

Can you try that?

But I've not build any packages yet, so will have to read up on how to do this.
Thanks 

João Cardoso

unread,
Jul 19, 2014, 6:30:11 PM7/19/14
to


On Saturday, July 19, 2014 10:01:49 PM UTC+1, Jason Stockley wrote:
I would have a go at :


I also tought of that. But that wouldn't explain why my last local pkgs build runs sickbeard OK.
I also though in downloading one of the sickbeard's author builds (https://github.com/midgetspy/Sick-Beard/releases) and install it instead of "master", eg, build 505 https://github.com/midgetspy/Sick-Beard/archive/build-505.tar.gz

Can you try that?

But I've not build any packages yet, so will have to read up on how to do this.

The sickbeard package is a "meta-package", it don't need to be built, all it has are a couple of scripts, one of them downloads the source python code in the proper place, /opt

In this case, with Sickbeard already installed and *not running*, you only have to:

-rename the current /opt/Sickbeard folder to something else,
-download the build-505.tar.gz
-extract it to /opt run 'tar -C /opt -xzf /path/to/build.tar.gz'
-rename the extracted build-505.tar.gz folder to Sickbeard
-run 'rcsickbeard status' to change the  necessary ownership of /opt/Sickbeard, create user/group if needed, etc.
-use the webui to configure and start it

Really simple.

There are other meta-packages that do the same, Couchpotato2, e.g.

 

João Cardoso

unread,
Jul 19, 2014, 8:18:14 PM7/19/14
to al...@googlegroups.com


On Saturday, July 19, 2014 11:30:11 PM UTC+1, João Cardoso wrote:


On Saturday, July 19, 2014 10:01:49 PM UTC+1, Jason Stockley wrote:
I would have a go at :


I also tought of that. But that wouldn't explain why my last local pkgs build runs sickbeard OK.
I also though in downloading one of the sickbeard's author builds (https://github.com/midgetspy/Sick-Beard/releases) and install it instead of "master", eg, build 505 https://github.com/midgetspy/Sick-Beard/archive/build-505.tar.gz

Can you try that?

But I've not build any packages yet, so will have to read up on how to do this.
The sickbeard package is a "meta-package", it don't need to be built, all it has are a couple of scripts, one of them downloads the source python code in the proper place, /opt

In this case, with Sickbeard already installed and *not running*, you only have to:

-rename the current /opt/Sickbeard folder to something else,
-download the build-505.tar.gz
-extract it to /opt run 'tar -C /opt -xzf /path/to/build.tar.gz'
-rename the extracted build-505.tar.gz folder to Sickbeard
-run 'rcsickbeard status' to change the  necessary ownership of /opt/Sickbeard, create user/group if needed, etc.
-use the webui to configure and start it

Really simple.

There are other meta-packages that do the same, Couchpotato2, e.g.

Forget the above, I found the culprit: the package distributed configuration file is not adequate to the current sickbeard version.

-Copy the attached sickbeard.conf to /etc/sickbeard/, overriding the original
-execute 'rcsickbeard status'
-configure and start it from the webUI

If it still gives the error, start uninstalling sickbeard, then repeat the above procedure. It worked for me.

sickbeard.conf

Jason Stockley

unread,
Jul 19, 2014, 10:24:59 PM7/19/14
to al...@googlegroups.com
Yes.. Thats Sorted it.

Thanks so much :-) 

Jason
Reply all
Reply to author
Forward
0 new messages