Sickrage Stopped working for no aparent reason

sickrage

#1

Hi, my sickrage installation is not working probably since 2 days ago. This is very extrange, it was working flawlessly until the weekend.
When I try to access the webserver it is displayed this msg

Service Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.

When I run this command: systemctl status [email protected] this is what I get

[email protected] - SickRage
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Mon 2017-04-03 19:12:16 UTC; 4h 51min ago
Process: 5827 ExecStart=/usr/bin/python /home/%I/.sickrage/SickBeard.py -q --daemon --nolaunch --datadir=/home/%I/.sickrage (code=exited, status=1/FAILURE)

Apr 03 19:12:16 SERVERNAME python[5827]: resp = self.send(prep, **send_kwargs)
Apr 03 19:12:16 SERVERNAME python[5827]: File “/home/USERNAME/.sickrage/lib/requests/sessions.py”, line 572, in send
Apr 03 19:12:16 SERVERNAME python[5827]: adapter = self.get_adapter(url=request.url)
Apr 03 19:12:16 SERVERNAME python[5827]: File “/home/USERNAME/.sickrage/lib/requests/sessions.py”, line 646, in get_adapter
Apr 03 19:12:16 SERVERNAME python[5827]: raise InvalidSchema(“No connection adapters were found for ‘%s’” % url)
Apr 03 19:12:16 SERVERNAME python[5827]: requests.exceptions.InvalidSchema: No connection adapters were found for 'scgi://SERVERNAME:57327/'
Apr 03 19:12:16 SERVERNAME systemd[1]: [email protected]: Control process exited, code=exited status=1
Apr 03 19:12:16 SERVERNAME systemd[1]: Failed to start SickRage.
Apr 03 19:12:16 SERVERNAME systemd[1]: [email protected]: Unit entered failed state.
Apr 03 19:12:16 SERVERNAME systemd[1]: [email protected]: Failed with result ‘exit-code’.

Tried with restarting/disabling the service and updating quickbox through the webpanel with no luck
regards


#2

There is already a thread with this issue on the forums. There was an issue it would seem with an update that was released by SickRage. You can fix this by doing a manual git pull followed by restarting the service. Here’s the post and solution explained.