Can't stop sabnzbdplus process

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
skycrzr
Newbie
Newbie
Posts: 4
Joined: September 8th, 2017, 9:57 am

Can't stop sabnzbdplus process

Post by skycrzr »

I am having a couple of issues. My sab server keeps wanting to run on my servers old static IP, 192.168.0.250. I previously was able to change the IP in the .ini to the new static IP (192.168.1.250) and got it up and running great for a few months. For some reason, yesterday it decided to revert back to the old static IP. (Note that I understand that you need to stop the service to make changes to the .ini, which I did.)

So I need to edit the ini to be 0.0.0.0 to end the IP issues, but now I can't stop the sabnzbdplus service, and therefore everytime I make changes to the ini, they are reverted.

I've tried

Code: Select all

sudo service sabnzbdplus stop

Code: Select all

sudo /etc/init.d/sabnzbdplus stop
Both of which give me no errors when running. Yet still this process is running:

Code: Select all

sabnzbd  31668 53.5  0.2 130252 42432 ?        Rs   11:23   0:01 /usr/bin/python -OO /usr/bin/sabnzbdplus -s 192.168.0.250 --browser 0 &
So I try this:

Code: Select all

sudo kill -9 31668
This runs successfully but a new process with a new PID is started.

I also tried editing /etc/default/sabnzbdplus to include 0.0.0.0 as the host IP and restart sab. This has no effect.

Here is my current service status when stopped:

Code: Select all

● sabnzbdplus.service - LSB: SABnzbd+ binary newsgrabber
   Loaded: loaded (/etc/init.d/sabnzbdplus; bad; vendor preset: enabled)
   Active: inactive (dead) since Mon 2021-01-25 10:59:56 CST; 27min ago
     Docs: man:systemd-sysv-generator(8)

Jan 25 10:57:08 hostname systemd[1]: Starting LSB: SABnzbd+ binary newsgrabber...
Jan 25 10:57:08 hostname sabnzbdplus[13233]:  * Starting SABnzbd+ binary newsgrabber
Jan 25 10:57:12 hostname sabnzbdplus[13233]:    ...done.
Jan 25 10:57:12 hostname systemd[1]: Started LSB: SABnzbd+ binary newsgrabber.
Jan 25 10:59:56 hostname systemd[1]: Stopping LSB: SABnzbd+ binary newsgrabber...
Jan 25 10:59:56 hostname sabnzbdplus[14313]:  * SABnzbd+ binary newsgrabber: not running
Jan 25 10:59:56 hostname systemd[1]: Stopped LSB: SABnzbd+ binary newsgrabber.
Jan 25 11:05:54 hostname systemd[1]: Stopped LSB: SABnzbd+ binary newsgrabber.
Jan 25 11:16:20 hostname systemd[1]: Stopped LSB: SABnzbd+ binary newsgrabber.
Jan 25 11:27:14 hostname systemd[1]: Stopped LSB: SABnzbd+ binary newsgrabber.
Occasionally I will get the following when trying to stop the service:

Code: Select all

Job for sabnzbdplus.service failed because the control process exited with error code. See "systemctl status sabnzbdplus.service" and "journalctl -xe" for details.
Here is the output of systemctl status sabnzbdplus.service:

Code: Select all

● sabnzbdplus.service - LSB: SABnzbd+ binary newsgrabber
   Loaded: loaded (/etc/init.d/sabnzbdplus; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2021-01-25 11:28:06 CST; 30s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1092 ExecStart=/etc/init.d/sabnzbdplus start (code=exited, status=143)

Jan 25 11:28:05 hostname systemd[1]: Starting LSB: SABnzbd+ binary newsgrabber...
Jan 25 11:28:05 hostname sabnzbdplus[1092]:  * Starting SABnzbd+ binary newsgrabber
Jan 25 11:28:06 hostname sabnzbdplus[1092]: Terminated
Jan 25 11:28:06 hostname sabnzbdplus[1092]:    ...fail!
Jan 25 11:28:06 hostname systemd[1]: sabnzbdplus.service: Control process exited, code=exited status=143
Jan 25 11:28:06 hostname systemd[1]: Failed to start LSB: SABnzbd+ binary newsgrabber.
Jan 25 11:28:06 hostname systemd[1]: sabnzbdplus.service: Unit entered failed state.
Jan 25 11:28:06 hostname systemd[1]: sabnzbdplus.service: Failed with result 'exit-code'.
Here is the output of journalctl -xe:

Code: Select all

Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,618::INFO::[scheduler:197] Setting schedule for midnight BPS reset
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,618::INFO::[__init__:349] All processes started
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,619::INFO::[sabnzbdplus:286] Web dir is /usr/share/sabnzbdplus/interfaces/Plush
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,619::INFO::[sabnzbdplus:286] Web dir is /usr/share/sabnzbdplus/interfaces/Config
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,626::INFO::[config:853] Writing settings to INI file /home/sabnzbd/.sabnzbd/sabnzbd.ini
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,655::INFO::[sabnzbdplus:397] SABYenc module (v3.3.6)... found!
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,655::INFO::[sabnzbdplus:414] Cryptography module (v2.0.3)... found!
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,656::INFO::[sabnzbdplus:419] par2 binary... found (/usr/bin/par2)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,656::INFO::[sabnzbdplus:429] UNRAR binary... found (/usr/bin/unrar)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,656::INFO::[sabnzbdplus:437] UNRAR binary version 5.30
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,656::INFO::[sabnzbdplus:442] unzip binary... found (/usr/bin/unzip)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,656::INFO::[sabnzbdplus:447] 7za binary... found (/usr/bin/7za)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,657::INFO::[sabnzbdplus:453] nice binary... found (/usr/bin/nice)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,657::INFO::[sabnzbdplus:457] ionice binary... found (/usr/bin/ionice)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,659::INFO::[sabnzbdplus:1385] Starting web-interface on 192.168.0.250:8085
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,659::INFO::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE Bus STARTING
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,822::ERROR::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE Error in HTTP server: shutting down
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: Traceback (most recent call last):
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]:   File "/usr/share/sabnzbdplus/cherrypy/process/servers.py", line 207, in _start_http_thread
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]:     self.httpserver.start()
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]:   File "/usr/share/sabnzbdplus/cherrypy/wsgiserver/__init__.py", line 2012, in start
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]:     raise socket.error(msg)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: error: No socket could be created -- (('192.168.0.250', 8085): [Errno 99] Cannot assign requested address)
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,822::INFO::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE Bus STOPPING
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,823::INFO::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE HTTP Server cherrypy._cpwsgi_server.CPWSGIServer(('192.16
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,823::INFO::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE Bus STOPPED
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,823::INFO::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE Bus EXITING
Jan 25 11:32:08 hostname SABnzbd Usenet Client[2686]: 2021-01-25 11:32:08,824::INFO::[_cplogging:219] [25/Jan/2021:11:32:08] ENGINE Bus EXITED
Jan 25 11:32:08 hostname systemd[1]: sabnzbd.service: Main process exited, code=exited, status=70/n/a
Jan 25 11:32:08 hostname systemd[1]: sabnzbd.service: Control process exited, code=exited status=1
Jan 25 11:32:08 hostname systemd[1]: sabnzbd.service: Unit entered failed state.
Jan 25 11:32:08 hostname systemd[1]: sabnzbd.service: Failed with result 'exit-code'.
Jan 25 11:32:09 hostname systemd[1]: sabnzbd.service: Service hold-off time over, scheduling restart.
Jan 25 11:32:09 hostname systemd[1]: Stopped SABnzbd Usenet Client.
-- Subject: Unit sabnzbd.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sabnzbd.service has finished shutting down.
Jan 25 11:32:09 hostname systemd[1]: Started SABnzbd Usenet Client.
-- Subject: Unit sabnzbd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sabnzbd.service has finished starting up.
--
-- The start-up result is done.
It's as if there is a additional rogue process or instance of sab running somewhere? It might be good to note that I also connect and disconnect to a VPN service from time to time, but im not sure how this might have an effect on the sabnzbd service, if any. It doesn't make sense where the old 192.168.0.250 static came from. I ensured my /etc/hosts is also correctly configured with the new static in case the script is checking there.

Thanks in advance for any help, it is much apprecaited.

User avatar
jcfp
Release Testers
Release Testers
Posts: 890
Joined: February 7th, 2008, 12:45 pm

Re: Can't stop sabnzbdplus process

Post by jcfp »

skycrzr wrote:
January 25th, 2021, 1:04 pm
Both of which give me no errors when running. Yet still this process is running:

Code: Select all

sabnzbd  31668 53.5  0.2 130252 42432 ?        Rs   11:23   0:01 /usr/bin/python -OO /usr/bin/sabnzbdplus -s 192.168.0.250 --browser 0 &
The lack of the --daemon option as well as the & at the end (a method for backgrounding a process in a unix terminal) are telltale signs that this process is not started from /etc/init.d/sabnzbdplus. You have some other method on your system that's starting sabnzbd, probably a broken native systemd service you added yourself. Get rid of that, get rid of your problem...

Post Reply