SABnzbd Forums

Hi all,
I have spent a good few hours trying to resolve this issue and ran out of ideas. Hope someone here can provide a solution or point me in the right direction.

In short: I upgraded to Ubuntu 18.04 from 16.04. Sabnzbd was not starting, so I went ahead and uninstalled it /reinstalled it.

last entries of sabnzbd.log below:

2018-11-12 23:43:38,241::INFO::[_cplogging:219] [12/Nov/2018:23:43:38] ENGINE Bus STOPPING
2018-11-12 23:43:38,241::INFO::[_cplogging:219] [12/Nov/2018:23:43:38] ENGINE HTTP Server Non
2018-11-12 23:43:38,257::INFO::[_cplogging:219] [12/Nov/2018:23:43:38] ENGINE HTTP Server che
2018-11-12 23:43:38,259::INFO::[_cplogging:219] [12/Nov/2018:23:43:38] ENGINE Bus STOPPED
2018-11-12 23:43:38,259::INFO::[_cplogging:219] [12/Nov/2018:23:43:38] ENGINE Bus EXITING
2018-11-12 23:43:38,260::INFO::[_cplogging:219] [12/Nov/2018:23:43:38] ENGINE Bus EXITED
2018-11-14 18:29:29,255::ERROR::[__init__:988] Loading /home/miguel/.sabnzbd/admin/Rating.sab
2018-11-14 18:29:29,970::INFO::[_cplogging:219] [14/Nov/2018:18:29:29] ENGINE Bus STARTING
2018-11-14 18:29:30,352::INFO::[_cplogging:219] [14/Nov/2018:18:29:30] ENGINE Serving on http
2018-11-14 18:29:30,355::INFO::[_cplogging:219] [14/Nov/2018:18:29:30] ENGINE Bus STARTED
2018-11-14 20:03:24,335::INFO::[_cplogging:219] [14/Nov/2018:20:03:24] ENGINE Bus STARTING
2018-11-14 20:03:24,956::INFO::[_cplogging:219] [14/Nov/2018:20:03:24] ENGINE Serving on http
2018-11-14 20:03:24,964::INFO::[_cplogging:219] [14/Nov/2018:20:03:24] ENGINE Bus STARTED
2018-11-14 20:03:36,340::ERROR::[nzbstuff:1534] Error importing <NzbFile: filename=95ce01b40b
2018-11-17 11:07:24,860::WARNING::[interface:329] Try our new skin Glitter! Fres
2018-11-17 12:39:02,192::WARNING::[__init__:182] Signal 15 caught, saving and ex
2018-11-17 12:39:07,293::INFO::[_cplogging:219] [17/Nov/2018:12:39:07] ENGINE Bu
2018-11-17 12:39:07,526::INFO::[_cplogging:219] [17/Nov/2018:12:39:07] ENGINE Se
2018-11-17 12:39:07,528::INFO::[_cplogging:219] [17/Nov/2018:12:39:07] ENGINE Bu
2018-11-17 14:22:54,082::WARNING::[__init__:182] Signal 15 caught, saving and ex
2018-11-17 14:22:57,409::INFO::[_cplogging:219] [17/Nov/2018:14:22:57] ENGINE Bu
2018-11-17 14:22:57,636::INFO::[_cplogging:219] [17/Nov/2018:14:22:57] ENGINE Se
2018-11-17 14:22:57,638::INFO::[_cplogging:219] [17/Nov/2018:14:22:57] ENGINE Bu
2018-11-17 14:45:13,888::WARNING::[__init__:182] Signal 15 caught, saving and ex
2018-11-17 16:22:39,112::INFO::[_cplogging:219] [17/Nov/2018:16:22:39] ENGINE Bu
2018-11-17 16:22:39,372::INFO::[_cplogging:219] [17/Nov/2018:16:22:39] ENGINE Se
2018-11-17 16:22:39,374::INFO::[_cplogging:219] [17/Nov/2018:16:22:39] ENGINE Bu
2018-11-17 16:24:33,469::WARNING::[__init__:182] Signal 2 caught, saving and exi
2018-11-17 16:30:35,805::INFO::[_cplogging:219] [17/Nov/2018:16:30:35] ENGINE Bu
2018-11-17 16:30:36,077::INFO::[_cplogging:219] [17/Nov/2018:16:30:36] ENGINE Se
2018-11-17 16:30:36,080::INFO::[_cplogging:219] [17/Nov/2018:16:30:36] ENGINE Bu
2018-11-17 16:31:38,366::WARNING::[__init__:182] Signal 2 caught, saving and exi
2018-11-17 16:39:59,778::INFO::[_cplogging:219] [17/Nov/2018:16:39:59] ENGINE Bu
2018-11-17 16:40:00,043::INFO::[_cplogging:219] [17/Nov/2018:16:40:00] ENGINE Se
2018-11-17 16:40:00,045::INFO::[_cplogging:219] [17/Nov/2018:16:40:00] ENGINE Bu
2018-11-17 16:45:59,424::WARNING::[__init__:182] Signal 2 caught, saving and exi

It sounds like you are closing the terminal window in which you are starting SABnzbd?
Signal 2 is a kill-command that is used when you Ctrl+C it.

Have you tried a full re-install? Are you using the PPA?

I am getting these same errors, even when starting SABnzbd via Systemd (systemctl) on Centos. This is a new behaviour and I haven't updated SAB any time recently...

Could this be a system policy that's unhappy with Sab resources?
I'm not very experienced in Linux world.

safihre wrote: ↑December 13th, 2018, 2:10 amCould this be a system policy that's unhappy with Sab resources?

That would either just leave sab to deal with its limited resources, or result in a kill signal (9) from the oom killer. Not an interrupt (2) or a regular term signal (15).

The latter would be what sab receives when someone tries to terminate the program in a nice way, e.g. by stopping its service. At least on Ubuntu, there have been no changes whatsoever in that department. It still comes with the same old init.d script, that these days ends up being used by systemd in "compatibility mode".