Sickbeard install help

[maz1324]

I am running into an issue when trying to install sickbeard on a Pogoplug v2. It appears that a ssl certificate issue is preventing the files from being downloaded. I have spent a lot of time the last two days reading these forums and searching google in attempt to figure this out. Linux is new to me and I don't understand everything I was reading about the topic.

I would appreciate it if someone could point me in the right direction.

Below is the output from running yaourt -AS sickbeard

$this->bbcode_second_pass_code('', '==> Downloading sickbeard PKGBUILD from AUR...
x sickbeard.install
x PKGBUILD
x sickbeard.conf.d
x Changelog
x sickbeard.sh
x sickbeard.ini
x sickbeard.rc.d

Comment by: collide on Sat, 17 Mar 2012 01:36:49 +0000
I am sorry, I realise my mistake, I did change the entry in /etc/conf.d/sickbeard to set the user to my user, and when I had permission issues I changed it to root, i didnt realise that the package created the sickbeard user. everything is working, I thank you for your assistance. :)

Comment by: regder on Fri, 23 Mar 2012 21:55:45 +0000
I'm trying to install Sickbeard on my Pogoplug and keep on getting an error. Can someone please guide me past it?

I've copied what happens to here, http://pastebin.com/6gVq3UvW

Thanks!

Comment by: brando56894 on Sat, 14 Apr 2012 17:33:10 +0000
Won't restart because updater.py is missing, also gives version check error since it's version nonea when the current is master. Install sickbeard-git and everything will be fixed.

Comment by: nicoulaj on Sun, 22 Apr 2012 20:37:13 +0000
@brando56894: This is not preventing the daemon from starting. Removing the builtin auto-update feature is the only way to enforce package integrity and stability.
@regder: your issue is not direclty related to this package, it seems to be an issue with yaourt/curl. Try searching Arch forums for this error.

Comment by: ice9 on Wed, 25 Apr 2012 18:16:48 +0000
It would be good if /etc/sickbeard, /var/log/sickbeard, and /var/lib/sickbeard already exist during installation that the installer should NOT change the ownership. I had set things up for a user other than sickbeard, but when I installed alpha494, it went and changed the ownership of those directories back to sickbeard and I had to change them again.

Comment by: kylef on Sun, 29 Apr 2012 19:54:41 +0000
This package shouldn't store the config.ini in /etc/sickbeard. Sickbeard itself can modify this file, so it should be in /var/lib/sickbeard to follow FHS. See http://www.pathname.com/fhs/pub/fhs-2.3.html#ETCHOSTSPECIFICSYSTEMCONFIGURATION 'A configuration file is a local file used to control the operation of a program; it must be STATIC and cannot be an executable binary'

First Submitted: Sat, 12 Jun 2010 03:09:08 +0000
sickbeard alpha494-1
( Unsupported package: Potentially dangerous ! )
==> Edit PKGBUILD ? [Y/n] ("A" to abort)
==> ------------------------------------
==> n

==> sickbeard dependencies:
- python2-cheetah (already installed)


==> Edit sickbeard.install ? [Y/n] ("A" to abort)
==> ---------------------------------------------
==> n

==> Continue building sickbeard ? [Y/n]
==> -----------------------------------
==>
==> Building and installing package
==> WARNING: Building package as root is dangerous.
Please run yaourt as a non-privileged user.
==> Making package: sickbeard alpha494-1 (Wed Dec 31 18:37:21 CST 1969)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving Sources...
-> Downloading sickbeard-alpha494.tar.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0curl: (60) SSL certificate problem, verify that the CA cert is OK. Details:
error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
bundle file isn't adequate, you can specify an alternate file
using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
the bundle, the certificate verification probably failed due to a
problem with the certificate (it might be expired, or the name might
not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
the -k (or --insecure) option.
==> ERROR: Failure while downloading sickbeard-alpha494.tar.gz
Aborting...
==> ERROR: Makepkg was unable to build sickbeard.
==> Restart building sickbeard ? [y/N]
==> ----------------------------------
==>
')

[Snerler]

I installed typing in sickbeard-git instead of sickbeard.

[maz1324]

That worked. Thanks!

[schn4rk]

Might as well post here rather than start a new topic...

I had been using the sickbeard alpha package, but after doing a full system upgrade I found the web interface was broken. Figured I'd switch to sickbeard-git as that's now been taken up by a new maintainer.

I copied my sickbeard.db, config.ini and autoProcessTV.py files somewhere safe because it wasn't going to be a straight upgrade of the same package. Then I removed my sickbeard install.

Now, when I try to install sickbeard-git, yaourt gets to the point where it's compressing the package, and then just hangs. The whole system hangs, in fact. I get the feeling the CPU is pinned, but I've never had that problem before.

Does anyone have any suggestions? Even some pointers on how to properly diagnose the problem would be great

EDIT: Get the feeling there might be something wrong with sickbeard-git at the moment so I've reinstalled the other version. Interestingly I was still having errors with the web interface but deleting the cache directory fixed this, as indicated in this thread: http://sickbeard.com/forums/viewtopic.php?f=4&t=4501

[Snerler]

This might a pretty noob question but when I try to update sickbeard-git from the web interface I get this error:

"Unable to find your git executable - either delete your .git folder and run from source OR set git_path in your config.ini to enable updates"

In the example it shows: git_path=/opt/bin/git, but I don't have anything there. I used "type git" command and it gave me this path: /usr/bin/git but that still gives me the same error.

What is the path to the git executable that I should use?

[WarheadsSE]

/usr/bin/git needs set for git_path in the config.ini

[Snerler]

I shut down sickbeard, set git_path=/usr/bin/git, and started sickbeard back up and it still gives me the same message.

[cosmicWy]

you're going to want to install git

# pacman -S git

then type:

# type git

and use the path it gives. then add that directory to the config.ini for sickbeard. i was able to get it to work and sickbeard stays up to date with the git repository!

[bolingj]

I am receiving the same error even after putting in the correct directory. Could it be a permissions error?

[obeyaron]

bolingj did u get it fixed? i'm having a similar issue.