Sickrage 20180228-5 not starting at install: raven problem

fgibaux commented 6 years ago

Setup

Package Name: Sickrage from #3138 Package Version: 20180228-5 Python version: python_rtd1296-6.1_2.7.14-18.spk from #3138

NAS Model: DS418 NAS Architecture: rtd1296 DSM version: DSM 6.1.6-15266 Update 1

Expected behavior

sickrage to start

Actual behavior

sickrage doesn't start; see package log

Steps to reproduce

1. install package with default options 2. a message says "launch manually the package to restore package" (approximately from my memory) 3. the log says there is no module raven 4. clicking on launch button try to start the package but fail

Package log

Sat May 12 18:05:36 WEST 2018
Starting sickrage command /volume1/@appstore/sickrage/env/bin/python /volume1/@appstore/sickrage/var/SickRage/SiCKRAGE.py --daemon --pidfile /volume1/@appstore/sickrage/var/sickrage.pid --config /volume1/@appstore/sickrage/var/config.ini --datadir /volume1/@appstore/sickrage/var/ 
Traceback (most recent call last):
  File "/volume1/@appstore/sickrage/var/SickRage/sickrage/__init__.py", line 219, in main
    from sickrage.core import Core
  File "/volume1/@appstore/sickrage/var/SickRage/sickrage/core/__init__.py", line 53, in <module>
    from sickrage.core.logger import Logger
  File "/volume1/@appstore/sickrage/var/SickRage/sickrage/core/logger.py", line 29, in <module>
    import raven
ImportError: No module named raven
Failed to import required libs, please run 'pip install --user -U -r /volume1/@appstore/sickrage/var/SickRage/requirements.txt' from console

for the context: I got it working a few month ago, then last month after apparently some changes in my config it wouldn't start complaining about an openssl problem. I think at that time I uninstalled it and reinstalled, was working until my change in the config. forgot about it for a while, and today, while investigating the issue, trying the uninstall/reinstall I get this raven error instead.

I did not try to run the pip command in the console as I'm not sure if it's safe to do so. should I run it in the sickrage env after a source bin/activate ?

ymartin59 commented 6 years ago

@Safihre Is it possible an internal Sickrage "auto-update" leads to a new version with different "requirements" that prevents built package to run it?

Safihre commented 6 years ago

That's probably what happend indeed would expected it to also auto-update dependencies..

In any case, during install we use the requirements.txt to install dependencies. So easiest is to just back up the Config file and reinstall the Sickrage package.

Safihre commented 6 years ago

Technically we could include a forced pip -R requirements.txt each time before starting sickrage?

BenjV commented 6 years ago

Just get rid of that stupid echelon version and use Sickbeard-Custom to install the real SickRage.

In the past he even added a bitcoin miner to his website and package. See his own posting. https://www.sickrage.ca/forums/forum/main-category/latest-news/36069-bitcoin-mining-has-been-added-to-both-the-site-and-app-to-help-support-running-costs

fgibaux commented 6 years ago

Hi, Thanks for your inputs.

Indeed in the installation steps, there is a prompt for which fork to use. Default value is master branch of https://git.sickrage.ca/sickrage/sickrage.git. @BenjV is that what you're referring to as the echelon version ? is https://github.com/SickRage/SickRage the real SickRage ?

Looking at the tags on both repo shows a lot of version since 20180228, I suppose the package auto-update to latest master at install ?

Safihre commented 6 years ago

Exactly. It fetches the latest master during the install (that's why it takes a while) and then installs the dependencies (another reason it takes long).

ymartin59 commented 6 years ago

@Safihre You already know I consider such "auto-update" feature a bad idea for users (may break for many reasons, cannot revert to an original tested version) and here is another situation which prevents package to be reliable: some "new" requirements may not be available as wheels because it requires compilation (what DSM is not ready for)...

fgibaux commented 6 years ago

Ok, Following @BenjV advice, I switched to Sickbeard-Custom package using git://github.com/SickRage/SickRage.git fork url. I'll see how it goes, but for now seems to do what I need. Thanks again for your help.

Dark2004 commented 6 years ago

Hello, for me it's not working with DSM 6.2-23731 even if it take the version 3138 and change the to it://github.com/SickRage/SickRage.git fork url package does not want to start

fgibaux commented 6 years ago

Hello @Dark2004, did you try with Sickbeard-Custom package (and not Sickrage package) ?

The Sickrage package does not accept the git://github.com/SickRage/SickRage.git fork url (it will says something like "cannot find sickbeard.py in the log ").

BenjV commented 6 years ago

I tried it myself and the current sickbeard-custom does not work with SickRage on my NAS. I shall try to find the problem.

In the past I have made a SickRage package myself that you can use. It installs an old version of SickRage but you can update it from within SickRage.

You can find it here. https://github.com/BenjV/SYNO-packages/raw/master/SickRage%20DSM%206%20noarch%20V1.0.spk

SynoCommunity / spksrc