We're trying out using Discord. Check the thread for the link. These forums will continue to operate as normal.

Sickrage won't start, ?After update to latest openflixr?

Longtime lurker, typically the issues I've had have been common and therefore answers were available in the forum. However, this one has me stumped. About a week ago, SR stopped responding, as did openflixr, maybe after a forced update of openflixr? A lot of things are fixed now, which is great!   However, I have two services that will not work. SR and Mopidy, both report "execution failed" in Monit. SR is an absolute priority for me and I've been fiddling with it for a few days to no avail. I'm hoping someone get me straightened out. Herre's what I have right now, hopefully there's a clue in there:

OPENFLIXR 2.5.1
openflixr@openflixr
              ,ââ¦â£â£â£â£â¦â¦,          -------------------
        ,ââ¦â£â£â¬â¬â£â                  OS: Ubuntu 16.04.5 LTS x86_64
                         ,ââ¦â£â£â¬â¬â£â Host: VirtualBox 1.2
                                        ÃKernel: 4.17.5-041705-generic
                                         Uptime: 1 day, 22 hours, 19 mins      ¬
â¬â¬â¬â¬â¬â¬â¬â¬â¬â£Ã¥â¦â,          ,ââ¦âPackages: 1316 (dpkg)
â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â£Ã¥â¦â¦ââ¦Shell: bash 4.3.48 ¬â¬â¬
â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬âTerminal: /dev/pts/0
â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬ÎCPU: Intel i5-2500K (2) @ 3.292GHz
â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬ÎGPU: VirtualBox Graphics Adapter
â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬ÎMemory: 3095MiB / 3944MiB
â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬ÎCPU Usage: 7% â¬â¬â¬
ââ¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬Î Disk (/): 44G / 95G (49%)
`                                        Local IP: xxx.xx.xx.xxx
      'ââ£â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬â¬Î   ââ¦â£Public IP: xxx.xx.xx.xxx
  
openflixr@openflixr:~$ systemctl status sickrage
â sickrage.service - LSB: starts instance of SickRage
   Loaded: loaded (/etc/init.d/sickrage; bad; vendor preset: enabled)
   Active: active (exited) since Tue 2018-10-23 12:39:08 CDT; 1 day 22h ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 0
   Memory: 0B
      CPU: 0
Oct 25 10:37:57 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:40:59 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:44:01 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:47:03 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:50:06 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:53:25 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:56:28 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 10:59:30 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 11:02:32 openflixr systemd[1]: Started LSB: starts instance of SickRage.
Oct 25 11:03:14 openflixr systemd[1]: Started LSB: starts instance of SickRage.
openflixr@openflixr:~$ systemctl status sickrage.service
â sickrage.service - LSB: starts instance of SickRage
   Loaded: loaded (/etc/init.d/sickrage; bad; vendor preset: enabled)
   Active: active (exited) since Tue 2018-10-23 12:39:08 CDT; 1 day 22h ago
     Docs: man:systemd-sysv-generator(8)
    Tasks: 0
   Memory: 0B
      CPU: 0
openflixr@openflixr:~$ sudo journalctl -xe
Oct 25 11:15:15 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:15:15 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetHi
Oct 25 11:15:45 openflixr mono[24651]: [Warn] Sabnzbd: Couldn't get download queue. Error respon
Oct 25 11:15:45 openflixr mono[24651]: [Error] Sabnzbd: Error response received from SABnzbd: AP
Oct 25 11:15:45 openflixr mono[24651]: [v0.2.0.1120] NzbDrone.Core.Download.Clients.DownloadClie
Oct 25 11:15:45 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:15:45 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:15:45 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:15:45 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetHi
Oct 25 11:16:15 openflixr mono[24651]: [Warn] Sabnzbd: Couldn't get download queue. Error respon
Oct 25 11:16:15 openflixr mono[24651]: [Error] Sabnzbd: Error response received from SABnzbd: AP
Oct 25 11:16:15 openflixr mono[24651]: [v0.2.0.1120] NzbDrone.Core.Download.Clients.DownloadClie
Oct 25 11:16:15 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:16:15 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:16:15 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.SabnzbdProxy.
Oct 25 11:16:15 openflixr mono[24651]:   at NzbDrone.Core.Download.Clients.Sabnzbd.Sabnzbd.GetHi
Oct 25 11:16:18 openflixr sudo[15202]: openflixr : TTY=pts/0 ; PWD=/home/openflixr ; USER=root ;
Oct 25 11:16:18 openflixr sudo[15202]: pam_unix(sudo:session): session opened for user root by o
Oct 25 11:16:18 openflixr sudo[15202]: pam_unix(sudo:session): session closed for user root
Oct 25 11:16:26 openflixr sudo[15239]: openflixr : TTY=pts/0 ; PWD=/home/openflixr ; USER=root ;
Oct 25 11:16:26 openflixr sudo[15239]: pam_unix(sudo:session): session opened for user root by o
Oct 25 11:16:26 openflixr sudo[15239]: pam_unix(sudo:session): session closed for user root
Oct 25 11:16:31 openflixr sudo[15256]: openflixr : TTY=pts/0 ; PWD=/home/openflixr ; USER=root ;
lines 1632-1654/1654 (END)
Thanks for looking!

Comments

  • Forgot to mention, The system was completely locked up and I had to do kill the VM process on the host machine. That's when this problem seems to have started.
    • journalctl -u sickrage:

    Oct 23 12:39:04 openflixr systemd[1]: Starting LSB: starts instance of SickRage...
    Oct 23 12:39:04 openflixr sickrage[1428]: Starting SickRage
    Oct 23 12:39:07 openflixr sickrage[1428]: Traceback (most recent call last):
    Oct 23 12:39:07 openflixr sickrage[1428]:   File "/opt/sickrage/sickrage/__init__.py", line 219, in main
    Oct 23 12:39:07 openflixr sickrage[1428]:     from sickrage.core import Core
    Oct 23 12:39:07 openflixr sickrage[1428]:   File "/opt/sickrage/sickrage/core/__init__.py", line 35, in <module>
    Oct 23 12:39:07 openflixr sickrage[1428]:     from apscheduler.schedulers.tornado import TornadoScheduler
    Oct 23 12:39:07 openflixr sickrage[1428]: ImportError: No module named apscheduler.schedulers.tornado
    Oct 23 12:39:07 openflixr sickrage[1428]: Failed to import required libs, please run 'pip install --user -U -r /opt/sickrage/requirements.txt' from console
    Oct 23 12:39:08 openflixr systemd[1]: Started LSB: starts instance of SickRage.
    Oct 23 12:39:39 openflixr systemd[1]: Started LSB: starts instance of SickRage.
    Oct 23 12:40:51 openflixr systemd[1]: Started LSB: starts instance of SickRage.
    Oct 23 12:44:55 openflixr systemd[1]: Started LSB: starts instance of SickRage.
    • ps -ef | grep -i sick:
    openflixr@openflixr:~$ ps -ef | grep -i sick
    openfli+ 13048 12995  0 18:24 pts/0    00:00:00 grep --color=auto -i sick

    • netstat -antp | grep :8081
    openflixr@openflixr:~$ netstat -antp | grep :8081
    (Not all processes could be identified, non-owned process info
     will not be shown, you would have to be root to see it all.)
    openflixr@openflixr:~$ sudo netstat -antp | grep :8081
    [sudo] password for openflixr:
    openflixr@openflixr:~$

  • edited October 2018
    Hiya

    I don't run either mopidy or sickrage but I think the clue is in that journal -u output:
      File "/opt/sickrage/sickrage/core/__init__.py", line 35, in <module>
       from apscheduler.schedulers.tornado import TornadoScheduler
    ImportError: No module named apscheduler.schedulers.tornado
    Failed to import required libs, please run 'pip install --user -U -r /opt/sickrage/requirements.txt' from console
    I had similar when I updated pi-hole; it broke some dependant libraries.

    First, I reckon turn off Monit's monitoring of sickrage and mopidy for now so that they start only when you want to try, rather than every few minutes.  That'll likely make logs easier to read, and will definitely help avoid false negatives where it's actually started but you then try manually and get errors (coz there's two instances running).

    Second, become root (sudo su -) then try that suggestion from the log:
    openflixr@openflixr:~$ sudo su -
    [sudo] password for openflixr:
    root@openflixr:~# pip install --user -U -r /opt/sickrage/requirements.txt
    Collecting APScheduler==3.5.0 (from -r /opt/sickrage/requirements.txt (line 1))
      Downloading https://files.pythonhosted.org/packages/19/d9/ca8322005bcd84c38e38cfaf2d5bd6fb66c14b4e977e973c6bb5ac5b98c7/APScheduler-3.5.0-py2.py3-none-any.whl (60kB)
        100% |████████████████████████████████| 61kB 2.2MB/s
    You might find you have to attempt start of sickrage, then read the logs, then repair something, and repeat a few times as the various different errors are exposed and then work through each.

    I note mine gave an error but sickrage still launches if I run it manually, so you may find that you don't need to fix every error to get it working:
      Downloading https://files.pythonhosted.org/packages/26/c1/2d2e5996c7488bdc2d3dcd14de5ace6e8f8f334b4896e932a21d5572cdfc/hachoir-core-1.3.3.tar.gz (91kB)
        100% |████████████████████████████████| 92kB 6.2MB/s
        Complete output from command python setup.py egg_info:
        Traceback (most recent call last):
          File "<string>", line 1, in <module>
          File "/tmp/pip-install-2cscr62o/hachoir-core/setup.py", line 41
            print "Sorry, you need Python 2.4 or greater to run (install) Hachoir!"
                                                                                  ^
        SyntaxError: invalid syntax
        ----------------------------------------
    Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-2cscr62o/hachoir-core/

    You should probably also force an update of openflixr as it does a couple of specific hard-reset type "fixes" in case things have gone badly.  Just run 'sudo updateopenflixr' and keep an eye on what happens - you might need to run it a couple of times even.

    Once this is all done and there's still issues, then you might need to force reinstallation of a couple of python dependency libraries - hopefully the logs should indicate which ones.  Check my post about fixing pi-hole for the syntax, I'll grab the link in a minute.
    Edit: http://www.openflixr.com/forum/discussion/comment/2033/#Comment_2033

    Good luck
  • edited October 2018
    Echel0n has succeeded in hijacking the redirection system of github, 
    as a result of which the https://github.com/SickRage/SickRage now links to its github.
    His software is worthless and does not want to run on Synology.
    
    The real github can now be found here: https://github.com/SickChill/SickChill/issues
    
    Everyone is advised not to update anymore because 
    then you are suddenly stuck with the software from Echel0n, 
    who does not want to run.
    To solve the problem, you must first adjust the config.ini from Sickrage.
    You can find it here.
    
    git_remote_url = https://github.com/SickRage/SickRage.git
    must be: https://github.com/SickChill/SickChill.git
    
    
    
    If you have already updated and SickRage does not want to run anymore, 
    you will have to reinstall SickRage with the sickbeard custom package 
    from the SynoCommunity.
    Then take this repro git: //github.com/SickChill/SickChill.git
    
    Good luck
  • @GillyMoreno  : Thx for the heads up. I went down the same route, even did the pip install, ofcourse to no avail. Also the pip install ended with a strange error :

    Collecting hachoir_core==1.3.3 (from -r /opt/sickrage/requirements.txt (line 9))
      Downloading https://files.pythonhosted.org/packages/26/c1/2d2e5996c7488bdc2d3dcd14de5ace6e8f8f334b4896e932a21d5572cdfc/hachoir-core-1.3.3.tar.gz (91kB)
        Complete output from command python setup.py egg_info:
        Traceback (most recent call last):
          File "<string>", line 1, in <module>
          File "/tmp/pip-install-kf9tpm7b/hachoir-core/setup.py", line 41
            print "Sorry, you need Python 2.4 or greater to run (install) Hachoir!"
                                                                                  ^
        SyntaxError: invalid syntax
        
        ----------------------------------------
    Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-kf9tpm7b/hachoir-core/

    Python 2.4 or greater ?? But now I must assume it has to do with OS incompatibility. Is there a write-up on how to reinstall the "SynoCommunity" version of SickRage, Or even better, are there any plans to release an OpenFlixr V2.5.x with the new SickChill, maybe an updated Monit  (the current Monit is not able to start/stop/disable monitoring, gives authentication errors)? I tried the suggested fix, but didn't have any luck.

  • If you have already updated and SickRage does not want to run anymore, 
    you will have to reinstall SickRage with the sickbeard custom package 
    from the SynoCommunity.
    Then take this repro git: //github.com/SickChill/SickChill.git
    
    Good luck
    I'm having the feeling I'm running behind... Installing Syno-apps on Ubuntu ? So how does this work?
  • It doesn't - the specifics there relate to Synology apps however the general thing (the repo being hijacked) will apply to every sickrage install.  As to whether the sickchill repo is suitable for a standard Ubuntu platform like ours - no idea.
  • What I have done are the next steps

    go to the folder /opt
    user@openflixr:~# cd /opt

    Backup your chace.db & config.ini to random location

    Delete the sickrage folder
    user@openflixr:/opt# sudo rm -rf /sickrage

    Download SickChill/SickRage
    user@openflixr:/opt# sudo git clone https://github.com/SickChill/SickChill.git /opt/sickrage

    Gives the Sickrage folder the correct rights
    sudo chown username:username -R /opt/sickrage

    place your backup back.

    Now we are going to see if SickRage / SickChill can be started.
    user@openflixr:/opt# python /opt/sickrage/SickBeard.py -d

    I am not an expert in ubuntu but this has worked for me to get sickrage back on track.
    Do not miss out that someone can help with starting SickRage / SickChill automatically.

    I hope you were helped with this solution
    Thank you!

  • Thank you both for your comments and help! I tried each step you suggested jeremywho, to no avail. I found a few minutes today to tackle this again and I see GillyMoreno's post on SickChill. It seems all is working as intended Gilly? I have always been a bit confused on the branches of SR once Echel0n and others parted ways, I know it wasn't amicable. Can you shed any light on SC and who is behind it?

    -Thanks again
  • What's the best way to get sickchill to auto start? symlink? Chronjob? Thanks to jeremywho, and GillyMoreno for getting me this far.
  • There's a default set of startup files in the repo that you're supposed to install/link as appropriate for your system.  The original sickrage one was an init.d file and I've kept that same idea on mine. Technically we should be updating init.d files to systemd files instead, but the result is the same.
Sign In or Register to comment.