Amahi Forums

Posted: **Mon Apr 13, 2015 6:23 am**

Ensure the ownership permissions for .sickrage are set to apache:users. Then restart the service.

If it fails, please provide the output of:

Code: Select all

systemctl restart sickrage

Posted: **Mon Apr 13, 2015 7:08 am**

Bigfoot, I believe I killed it.
Re-install, reconfigure for SAB and torrent, load shows and working again.
Also manual backup of the settings...............

Posted: **Mon Apr 13, 2015 8:02 am**

LOL

All is well now I presume.

Posted: **Mon Apr 13, 2015 9:07 am**

I am having issues getting the service to start.

Here;s what I did after an uninstall, reboot, install of SickRage:

Code: Select all

cd /var/hda/web-apps/sickrage
systemctl stop sickrage
rm -rf .sickrage
cp -R /mnt/samba/Newsgroups/SickRage_Backup/sickrage/.sickrage .sickrage
chown -R apache:users /var/hda/web-apps/sickrage/.sickrage
chmod -R 777 /var/hda/web-apps/sickrage/.sickrage
systemctl start sickrage

Job for sickrage.service failed. See 'systemctl status sickrage.service' and 'journalctl -xn' for details.

*I created a manual backup of my .sickbeard folder before, hence the different path.

any thoughts?

Posted: **Mon Apr 13, 2015 9:26 am**

Did you check ownership of the .sickrage file?

Also check the output of:

Code: Select all

systemctl status sickrage.service

Posted: **Mon Apr 13, 2015 9:52 am**

The owner is 'apache [48]'

I checked the code, and got the following:

Code: Select all

[root@localhost ~]# systemctl status sickrage.service
sickrage.service - LSB: starts SickRage
   Loaded: loaded (/etc/rc.d/init.d/sickrage)
   Active: failed (Result: exit-code) since Mon 2015-04-13 11:40:24 CDT; 5s ago
  Process: 5647 ExecStop=/etc/rc.d/init.d/sickrage stop (code=exited, status=0/SUCCESS)
  Process: 11159 ExecStart=/etc/rc.d/init.d/sickrage start (code=exited, status=1/FAILURE)

Apr 13 11:40:20 localhost.localdomain runuser[11161]: pam_unix(runuser:session): session opened for user apache by (uid=0)
Apr 13 11:40:24 localhost.localdomain sickrage[11159]: Starting sickbeard: Your config version (7) has been incremented past what this version of SickRage supports (6).
Apr 13 11:40:24 localhost.localdomain sickrage[11159]: If you have used other forks or a newer version of SickRage, your config file may be unusable due to their modifications.
Apr 13 11:40:24 localhost.localdomain runuser[11161]: pam_unix(runuser:session): session closed for user apache
Apr 13 11:40:24 localhost.localdomain systemd[1]: sickrage.service: control process exited, code=exited status=1
Apr 13 11:40:24 localhost.localdomain systemd[1]: Failed to start LSB: starts SickRage.
Apr 13 11:40:24 localhost.localdomain systemd[1]: Unit sickrage.service entered failed state.

it looks like my backup is a new version, so, I then did an uninstall/reinstall, but did the initial update, and the service now starts...

but I now get a 503 error

Posted: **Mon Apr 13, 2015 10:00 am**

here's the final results of the code you posted

Code: Select all

[root@localhost sickrage]# systemctl status sickrage.service
sickrage.service - LSB: starts SickRage
   Loaded: loaded (/etc/rc.d/init.d/sickrage)
   Active: active (running) since Mon 2015-04-13 11:55:29 CDT; 3min 58s ago
  Process: 13571 ExecStop=/etc/rc.d/init.d/sickrage stop (code=exited, status=0/SUCCESS)
  Process: 13603 ExecStart=/etc/rc.d/init.d/sickrage start (code=exited, status=0/SUCCESS)
   CGroup: name=systemd:/system/sickrage.service
           ââ13662 python /var/hda/web-apps/sickrage/html/SickBeard.py --daemon --nolaunch --pidfile=/var/run/sickrage/sickrage.pid --datadir=/var/hda/web-apps/sickrage/.sickrage

Apr 13 11:55:24 localhost.localdomain runuser[13605]: pam_unix(runuser:session): session opened for user apache by (uid=0)
Apr 13 11:55:29 localhost.localdomain runuser[13605]: pam_unix(runuser:session): session closed for user apache
Apr 13 11:55:29 localhost.localdomain sickrage[13603]: Starting sickbeard: [  OK  ]
Apr 13 11:55:29 localhost.localdomain systemd[1]: Started LSB: starts SickRage.

Posted: **Mon Apr 13, 2015 10:42 am**

Ok so the service is running now. The web UI should work based on port 8082.

Posted: **Mon Apr 13, 2015 11:36 am**

http://192.168.1.10:8082/ says the website is unavailable

http://sickrage. <my name>/ says 503 service unavailable

Posted: **Mon Apr 13, 2015 12:27 pm**

hmm, seems a full shutdown vs a restart did the trick, its up and running

Amahi Forums

CLOSED: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start

Re: Sickrage does not start