Project

General

Profile

Bug #1852

SickRAGE fails to start

Added by phreaq over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Apps
Target version:
-
Start date:
10/07/2015
Due date:
% Done:

0%


Description

my sickrage service stopped for some reason today, and won't restart

running systemctl status sickrage.service gives the following results:

---
sickrage.service - LSB: starts SickRage
Loaded: loaded (/etc/rc.d/init.d/sickrage)
Active: failed (Result: exit-code) since Wed 2015-10-07 12:50:12 CDT; 14s ago
Process: 7046 ExecStop=/etc/rc.d/init.d/sickrage stop (code=exited, status=0/SUCCESS)
Process: 7215 ExecStart=/etc/rc.d/init.d/sickrage start (code=exited, status=1/FAILURE)

Oct 07 12:50:12 localhost.localdomain sickrage7215: from sickbeard import logger, classes
Oct 07 12:50:12 localhost.localdomain sickrage7215: File "/var/hda/web-apps/sickrage/html/sickbeard/logger.py", line 277
Oct 07 12:50:12 localhost.localdomain sickrage7215: if title_Error.rsplit(' :: ')[-1] in report.title or
Oct 07 12:50:12 localhost.localdomain sickrage7215: ^
Oct 07 12:50:12 localhost.localdomain sickrage7215: SyntaxError: invalid syntax
Oct 07 12:50:12 localhost.localdomain runuser7217: pam_unix(runuser:session): session closed for user apache
Oct 07 12:50:12 localhost.localdomain sickrage7215: [FAILED]
Oct 07 12:50:12 localhost.localdomain systemd1: sickrage.service: control process exited, code=exited status=1
Oct 07 12:50:12 localhost.localdomain systemd1: Failed to start LSB: starts SickRage.
Oct 07 12:50:12 localhost.localdomain systemd1: Unit sickrage.service entered failed state.
---

I believe my setup allows for auto-updates, and I believe an update occurred today, and perhaps failed (?)

here is the URL from running fpaste --sysinfo

http://paste.fedoraproject.org/276055/42023144

History

#1 Updated by bigfoot65 over 3 years ago

  • Status changed from New to Assigned
  • Assignee set to bigfoot65

If there was an update today from the vendor, that could likely be the issue. I will test locally and see if I can replicate. Also keep in mind this is Amahi 7, so support for apps is very limited as Amahi 8 is the latest stable Amahi version.

Since these updates are not tested by Amahi, we cannot do much to help correct them. Recommend you also check with the vendor for a bug fix and or report the issue to them as well.

Once I complete my local testing, I will update this bug with proposed actions.

#2 Updated by cpg over 3 years ago

  • Project changed from platform to apps

#3 Updated by bigfoot65 over 3 years ago

Updated to latest stable version, 4.1.0.2. Upon install and accessing app, it wants to update it. Once complete, the app does not appear to correctly work. There are menus and buttons missing.

Would anticipate the software author has added code to the git repo that likely breaks the app.

#4 Updated by phreaq over 3 years ago

I resolved my initial issue by uninstalling/reinstalling, however the issue occurred again. After reinstalling, SR goes to upgrade, and never restarts

@[root@localhost ~]# service sickrage status
sickrage.service - LSB: starts SickRage
Loaded: loaded (/etc/rc.d/init.d/sickrage)
Active: failed (Result: exit-code) since Sat 2015-12-05 10:48:02 CST; 1h 51min ago
Process: 18920 ExecStop=/etc/rc.d/init.d/sickrage stop (code=exited, status=0/SUCCESS)
Process: 18926 ExecStart=/etc/rc.d/init.d/sickrage start (code=exited, status=1/FAILURE)

Dec 05 10:48:02 localhost.localdomain sickrage18926: sickbeard.initialize(consoleLogging=self.consoleLogging)
Dec 05 10:48:02 localhost.localdomain sickrage18926: File "/var/hda/web-apps/sickrage/html/sickbeard/__init__.py", line 1366, in initialize
Dec 05 10:48:02 localhost.localdomain sickrage18926: migrator.migrate_config()
Dec 05 10:48:02 localhost.localdomain sickrage18926: File "/var/hda/web-apps/sickrage/html/sickbeard/config.py", line 651, in migrate_config
Dec 05 10:48:02 localhost.localdomain sickrage18926: logging.log(u"Backing up config before upgrade")
Dec 05 10:48:02 localhost.localdomain sickrage18926: TypeError: log() takes at least 2 arguments (1 given)
Dec 05 10:48:02 localhost.localdomain runuser18928: pam_unix(runuser:session): session closed for user apache
Dec 05 10:48:02 localhost.localdomain systemd1: sickrage.service: control process exited, code=exited status=1
Dec 05 10:48:02 localhost.localdomain systemd1: Failed to start LSB: starts SickRage.
Dec 05 10:48:02 localhost.localdomain systemd1: Unit sickrage.service entered failed state.
[root@localhost ~]#
@

and

http://paste.fedoraproject.org/297756/40799144

#5 Updated by bigfoot65 over 3 years ago

Based on the error message, there's indication that the git update is what broke things. Whatever code change was made in their repo is the issue.

Recommend you check out there forums and bug tracker for this problem. Since this appears to have nothing to do with Amahi or the OS, I would look to the vendor for resolution.

Safest thing would be to use SickBeard since it's stable and likely will work better in the long run.

#6 Updated by bigfoot65 over 3 years ago

  • Status changed from Assigned to Feedback
  • Assignee changed from bigfoot65 to phreaq

#7 Updated by phreaq over 3 years ago

It seems other are having issues too (https://sickrage.tv/forums/forum/help-support/general-support/31003-sickrage-won-t-start-after-update).

One user said a manual git pull fixed his issue. can I do that in amahi?

#8 Updated by bigfoot65 over 3 years ago

You should be able to do so. Please understand our support is limited with BETA apps, especially when you deviate from the Amahi default install.

#9 Updated by bigfoot65 over 3 years ago

  • Category set to Apps

#10 Updated by phreaq over 3 years ago

I believe my own ignorance will prevent me from doing it manually.

#11 Updated by phreaq over 3 years ago

were you able to replicate the problem in Amahi 7 on your side?

#12 Updated by bigfoot65 over 3 years ago

No as our policy is to only update apps for the latest stable release, which is Amahi 8. Sorry but we don't have the resources to work on Amahi versions in maintenance status.

Recommend you upgrade to Amahi 8.

#13 Updated by phreaq over 3 years ago

so your recommendation to resolve a problematic app is to do a full server OS upgrade, and reinstall all other apps? not sure that makes much sense.

(fwiw, it seems sickbeard wont update itself either)

#14 Updated by bigfoot65 over 3 years ago

Not quite. My point is this app was never LIVE and still in testing. The same situation applies to it in Amahi 8. I honestly think the app is broken due to upstream updates from the vendor as it's not working quite right in Amahi 8.

There are always risks when depending on an app that is not stable. We don't recommend using BETA apps in a production environment for just this reason

Sick Beard does not update as I believe development on it has ceased. Last I checked there had been no changes in several months. I use Sick Beard myself and have no issues.

It's possible it may resolve on it's own when more updates are committed by the author. Sorry I cannot be of much help but not sure what the issue is with this app. Hopefully a future update will fix the problem.

#15 Updated by bigfoot65 over 3 years ago

BTW, We made an update to the Amahi 8 version that appears to work well. To help you out, the same update was applied to the Amahi 7 version.

Please give it a try and let us know if it fixes your problem. We made an exception to policy, so please understand this is a one time deal for Amahi 7.

#16 Updated by phreaq over 3 years ago

The new build (4.1.0.2) install on 7, but then results in a 503 Service Unavailable error when you try and access it.

#17 Updated by bigfoot65 over 3 years ago

Try doing:

systemctl status sickrage

Post the results. Not sure what the issue could be as it works fine on Amahi 8.

#18 Updated by phreaq over 3 years ago

we may have found something...

@[root@localhost ~]# systemctl status sickrage
sickrage.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)

Dec 07 19:34:53 localhost.localdomain systemd1: Stopped LSB: starts SickRage.
Dec 07 19:35:00 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 07 19:37:01 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 07 19:37:05 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 07 20:03:49 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 07 20:03:54 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 08 17:04:57 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 08 17:05:02 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 08 17:19:06 localhost.localdomain systemd1: Stopped sickrage.service.
Dec 08 17:19:11 localhost.localdomain systemd1: Stopped sickrage.service.
[root@localhost ~]#
@

If I take a look in the webapps folder the .sickrage folder is missing

[root@localhost sickrage]# ls
html logs
[root@localhost sickrage]#

#19 Updated by phreaq over 3 years ago

Here's the latest from my app installer log

======= app install begin 2015-12-09 08:15:49 -0600 ==========
Installing app id 0udwc1pno0 under /var/hda/platform/html/script/.. ENV=production
file /var/hda/tmp/amahi-download-cache/47cba6578cc0d407f1b601c925472e1d60f77c83 picked up from cache.
Your HDA services have been restarted.
Your HDA services have been restarted.
sed: can't read ./html/init.fedora: No such file or directory
Installing sickrage service
install: cannot stat ‘../html/init.fedora’: No such file or directory
Installing Amahi specific settings in sysconfig
Reloading systemctl daemon
Enabling sickrage service
error reading information on service sickrage: No such file or directory
Starting sickrage service
Redirecting to /bin/systemctl start sickrage.service
Failed to issue method call: Unit sickrage.service failed to load: No such file or directory. See system logs and 'systemctl status sickrage.service' for details.
sed: can't read ../.sickrage/config.ini: No such file or directory
Reloading sickrage service
Redirecting to /bin/systemctl force-reload sickrage.service
Failed to issue method call: Unit sickrage.service failed to load: No such file or directory. See system logs and 'systemctl status sickrage.service' for details.
Done!
App: SiCKRAGE installed ======= app install end 2015-12-09 08:15:59 -0600 ==========

#20 Updated by bigfoot65 over 3 years ago

Try uninstalling the app, then reinstall. Made some changes that should correct the errors.

BTW, the .sickrage folder will not show unless you do:

ls -al

I did not test this on Amahi 7, so expected some errors. They should be hopefully cleared up now.

If it works, please close the bug. Also just a reminder, this was a one time exception to policy. Once it's fixed for you, we won't be making any more updates to this app for Amahi 7.

#21 Updated by phreaq over 3 years ago

  • Status changed from Feedback to Resolved

the new changes worked!!!

you're awesome, thanks!!!

now someone other than your mom thinks your special, thanks again!!!!

#22 Updated by bigfoot65 over 3 years ago

  • Status changed from Resolved to Closed

Also available in: Atom