Project

General

Profile

Bug #1297

Sabnzbdplus - server fails to start

Added by strangename over 7 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
02/10/2014
Due date:
% Done:

0%


Description

Attempting to install Sabnzbd+ on Amahi v7. Server fails to start either manually or automatically.

Amahi installer log shows the following:

[CODE]======= app install begin @ 2014-02-09 22:43:19 +0000 ==========
Installing app id l87u14kg9n under /var/hda/platform/html ENV=production
file /var/hda/tmp/amahi-download-cache/6b15e7b86e6d1e9aa910b2af9d7a00f08749cb96 picked up from cache.
Your HDA services have been restarted.
Your HDA services have been restarted.
Configuring Amahi settings
Installing sabnzbd.service
Reloading systemctl daemon
Enabling sabnzbd.service
Starting sabnzbd.service
Job for sabnzbd.service failed. See 'systemctl status sabnzbd.service' and 'journalctl -xn' for details.
/var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/validations.rb:56:in `save!': Validation failed: Identifier has already been taken (ActiveRecord::RecordInvalid)
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/attribute_methods/dirty.rb:33:in `save!'
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/transactions.rb:264:in `block in save!'
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/transactions.rb:313:in `block in with_transaction_returnin g_status'
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/connection_adapters/abstract/database_statements.rb:192:in `transaction'
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/transactions.rb:208:in `transaction'
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/transactions.rb:311:in `with_transaction_returning_status'
from /var/hda/platform/html/vendor/bundle/ruby/gems/activerecord-3.2.14/lib/active_record/transactions.rb:264:in `save!'
from /var/hda/platform/html/app/models/app.rb:244:in `install_bg'
from /var/hda/platform/html/script/install-app:99:in `install_or_uninstall'
from /var/hda/platform/html/script/install-app:120:in `main'
from /var/hda/platform/html/script/install-app:132:in `<main>'[\CODE]

The service report is as follows:

[CODE]sabnzbd.service - SABnzbd Plus server
Loaded: loaded (/usr/lib/systemd/system/sabnzbd.service; enabled)
Active: failed (Result: exit-code) since Sun 2014-02-09 22:45:15 GMT; 1min 54s ago
Process: 26590 ExecStart=/var/hda/web-apps/sabnzbdplus/html/SABnzbd.py --browser 0 --daemon --pid /var/run/sabnzbd/ --config-file /var/hda/web-apps/sabnzbdplus/html/sabn zbd.ini (code=exited, status=2)
Process: 26588 ExecStartPre=/usr/bin/chown -R apache:users /var/run/sabnzbd/ (code=exited, status=0/SUCCESS)
Process: 26586 ExecStartPre=/usr/bin/mkdir -p /var/run/sabnzbd/ (code=exited, status=0/SUCCESS)

Feb 09 22:45:15 localhost.localdomain systemd1: Starting SABnzbd Plus server...
Feb 09 22:45:15 localhost.localdomain systemd1: sabnzbd.service: control process exited, code=exited status=2
Feb 09 22:45:15 localhost.localdomain systemd1: Failed to start SABnzbd Plus server.
Feb 09 22:45:15 localhost.localdomain systemd1: Unit sabnzbd.service entered failed state.[\CODE]

History

#1 Updated by bigfoot65 over 7 years ago

  • Assignee set to bigfoot65

I am not seeing anything wrong with the app. I have been unable to duplicate the issue you are having with install.

#2 Updated by bigfoot65 over 7 years ago

From Strangename:

I did that check and there was a duplicate folder.

I deleted the duplicate and then the original and tried to reinstall again.

I am getting an error on the creation of sabnzbd.ini - for some reason it is exiting with a status of 2 which is normally a fatal error.

So where should I look to manually clear out the install for sabnzbd+ ?

Looking like there are some things not being deleted on the uninstall.

#3 Updated by bigfoot65 over 7 years ago

Check /var/hda/files/newsgroups for the sabnzbd.ini file. If it's there, remove it. Might consider reboot before trying to reinstall. Also ensure there is no /var/hda/web-apps/sabnzbd folders present.

Not sure what is going on with you install, but never should have been able to install the app twice.

Did you try to install more than once when it initially failed? If so, recommend not doing that. What happens is it gets caught in a state of installing sometimes when it says it failed. The dashboard will indicate failure, but when you check installed apps it will show up.

This is something that is still being looked at for potential update.

#4 Updated by bigfoot65 over 7 years ago

From Strangename:
Thanks for the info Bigfoot.

I always uninstall before trying to reinstall to try and keep things as clean as possible - at least that was my intention.

I looked in to /var/hda/files/newsgroups and there was no sabnzbd.ini

Similarly no sabnzbd folders/files in web-apps dir - however I uninstalled the app went back and checked the newsgroups dir and low and behold a new sabnzbd.ini file had been written!

So now I'm really confused as this is somewhat backwards!

I did reboot the system and now have lost HDA access - can SSH in and use Samba - there is a problem with the server which I am going to have to deal with and probably start with a complete reinstall.

Thanks for your help on this.

#5 Updated by bigfoot65 over 7 years ago

The reason you see the .ini file after uninstall is the app backs it up there. This is to preserve settings when you upgrade via the uninstall and reinstall.

As for not being able to access the dashboard, it sounds like the web server may be down. As root user, do:

systemctl status httpd.service

If that is the case, then recommend you check /etc/httpd/conf.d for any stray .conf files such as from the failed SABnzbd Plus installs and remove them. Then try retarting the web server, substituting restart for status in the above command.

#6 Updated by strangename over 7 years ago

Thanks for the latest info. Checked the conf.d dir and found a rogue conf file which I deleted, rebooted and now Apache has started as it should.

I did try another reinstall which failed with the usual message in the App store. A copy of the log is here:

http://ur1.ca/gm8bc -> http://paste.fedoraproject.org/76667/39223410

Since the above failure have left it alone.

#7 Updated by bigfoot65 over 7 years ago

  • Status changed from New to Feedback
  • Assignee changed from bigfoot65 to strangename

Any new updates? Unable to repeat the behavior.

#8 Updated by bigfoot65 over 7 years ago

  • Status changed from Feedback to Closed
  • Assignee deleted (strangename)

No response indicated resolved.

Also available in: Atom