Page 1 of 1
sabnzbdplus won't run anymore
Posted: January 13th, 2018, 5:37 pm
by SparkyRih
When I try to run:
it returns:
Code: Select all
[....] Starting sabnzbdplus (via systemctl): sabnzbdplus.serviceJob for sabnzbdplus.service failed because the control process exited with error code. See "systemctl status sabnzbdplus.service" and "journalctl -xe" for details.
failed!
When I run:
Code: Select all
systemctl status sabnzbdplus.service
It returns:
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 Sat 2018-01-13 23:23:32 CET; 3min 8s ago
Docs: man:systemd-sysv-generator(8)
Process: 2973 ExecStart=/etc/init.d/sabnzbdplus start (code=exited, status=2)
Jan 13 23:23:30 schattorie-web systemd[1]: Starting LSB: SABnzbd+ binary newsgrabber...
Jan 13 23:23:30 schattorie-web sabnzbdplus[2973]: * Starting SABnzbd+ binary newsgrabber
Jan 13 23:23:32 schattorie-web sabnzbdplus[2973]: ...fail!
Jan 13 23:23:32 schattorie-web systemd[1]: sabnzbdplus.service: Control process exited, code=exited status=2
Jan 13 23:23:32 schattorie-web systemd[1]: Failed to start LSB: SABnzbd+ binary newsgrabber.
Jan 13 23:23:32 schattorie-web systemd[1]: sabnzbdplus.service: Unit entered failed state.
Jan 13 23:23:32 schattorie-web systemd[1]: sabnzbdplus.service: Failed with result 'exit-code'.
When I try to run the sabnzbdplus deamon manually it appears to "hang" at the line: SSL verification test: True
My /etc/default/sabnzbdplus has all the parameters empty, except for the USER= which contains the user which I'm logged on as...
I've tried removing/installing/updating, tried different users in that config file, tried pointing it to the sabnzbd.ini... I have no clue on why the deaon suddenly stopped working after a couple of years of running :S
Any help?
Re: sabnzbdplus won't run anymore
Posted: January 14th, 2018, 4:03 am
by sander
When I try to run the sabnzbdplus deamon manually it appears to "hang" at the line: SSL verification test: True
I think that is not a hang; I think SAB is running. Did you try to access SAB with your webbrowser?
Re: sabnzbdplus won't run anymore
Posted: January 14th, 2018, 6:40 am
by SparkyRih
sander wrote: ↑January 14th, 2018, 4:03 am
When I try to run the sabnzbdplus deamon manually it appears to "hang" at the line: SSL verification test: True
I think that is not a hang; I think SAB is running. Did you try to access SAB with your webbrowser?
Yes, I tried, but it isn't accessible via the browser...
Re: sabnzbdplus won't run anymore
Posted: January 14th, 2018, 12:42 pm
by sander
OK, do this:
start sabnzbdplus from the CLI, and wait until it 'hangs'.
then type
Code: Select all
netstat -apon | grep -i listen | grep -vi listening
post the output here
Re: sabnzbdplus won't run anymore
Posted: January 14th, 2018, 1:18 pm
by SparkyRih
Thanks for your reply... sabnzbdplus should be on port 8080, which is in the list, but what is "node"......
Code: Select all
root@schattorie-web:/home/marc# netstat -apon | grep -i listen | grep -vi listening
tcp 0 0 0.0.0.0:8282 0.0.0.0:* LISTEN 1889/python off (0.00/0/0)
tcp 0 0 0.0.0.0:5050 0.0.0.0:* LISTEN 1653/python off (0.00/0/0)
tcp 0 0 0.0.0.0:7995 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 3496/nginx.conf off (0.00/0/0)
tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 1659/smbd off (0.00/0/0)
tcp 0 0 0.0.0.0:7071 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 127.0.0.1:10015 0.0.0.0:* LISTEN 2811/utserver off (0.00/0/0)
tcp 0 0 0.0.0.0:7072 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 127.0.0.1:23232 0.0.0.0:* LISTEN 3521/perl off (0.00/0/0)
tcp 0 0 0.0.0.0:7073 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 127.0.0.1:23233 0.0.0.0:* LISTEN 3523/perl off (0.00/0/0)
tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN 3496/nginx.conf off (0.00/0/0)
tcp 0 0 0.0.0.0:6881 0.0.0.0:* LISTEN 2811/utserver off (0.00/0/0)
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN 3496/nginx.conf off (0.00/0/0)
tcp 0 0 127.0.0.1:7171 0.0.0.0:* LISTEN 1191/java off (0.00/0/0)
tcp 0 0 192.168.0.15:389 0.0.0.0:* LISTEN 1159/slapd off (0.00/0/0)
tcp 0 0 0.0.0.0:5222 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:7110 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:7143 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 127.0.0.1:10663 0.0.0.0:* LISTEN 5722/zmlogger: zmrr off (0.00/0/0)
tcp 0 0 127.0.0.1:10024 0.0.0.0:* LISTEN 3582/amavisd (maste off (0.00/0/0)
tcp 0 0 0.0.0.0:25672 0.0.0.0:* LISTEN 1373/beam.smp off (0.00/0/0)
tcp 0 0 127.0.0.1:10025 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 127.0.0.1:10026 0.0.0.0:* LISTEN 3582/amavisd (maste off (0.00/0/0)
tcp 0 0 127.0.0.1:7306 0.0.0.0:* LISTEN 3084/mysqld off (0.00/0/0)
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 1255/mysqld off (0.00/0/0)
tcp 0 0 127.0.0.1:10027 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 0.0.0.0:11211 0.0.0.0:* LISTEN 3477/memcached off (0.00/0/0)
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 1659/smbd off (0.00/0/0)
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 1249/redis-server 1 off (0.00/0/0)
tcp 0 0 127.0.0.1:10028 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 127.0.0.1:10029 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 127.0.0.1:10030 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 127.0.0.1:3310 0.0.0.0:* LISTEN 3874/clamd off (0.00/0/0)
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN 3496/nginx.conf off (0.00/0/0)
tcp 0 0 0.0.0.0:8111 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN 3496/nginx.conf off (0.00/0/0)
tcp 0 0 127.0.0.1:10032 0.0.0.0:* LISTEN 3582/amavisd (maste off (0.00/0/0)
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 1697/perl off (0.00/0/0)
tcp 0 0 0.0.0.0:7025 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:465 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp 0 0 127.0.0.1:8465 0.0.0.0:* LISTEN 3903/opendkim off (0.00/0/0)
tcp 0 0 0.0.0.0:8081 0.0.0.0:* LISTEN 1724/python off (0.00/0/0)
tcp 0 0 0.0.0.0:4369 0.0.0.0:* LISTEN 1264/epmd off (0.00/0/0)
tcp 0 0 0.0.0.0:5269 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 2720/unbound off (0.00/0/0)
tcp 0 0 0.0.0.0:8181 0.0.0.0:* LISTEN 2811/utserver off (0.00/0/0)
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 1006/sshd off (0.00/0/0)
tcp 0 0 0.0.0.0:888 0.0.0.0:* LISTEN 1329/nginx -g daemo off (0.00/0/0)
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN 1267/postgres off (0.00/0/0)
tcp 0 0 0.0.0.0:7993 0.0.0.0:* LISTEN 10133/java off (0.00/0/0)
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 4260/master off (0.00/0/0)
tcp6 0 0 :::445 :::* LISTEN 1659/smbd off (0.00/0/0)
tcp6 0 0 :::8126 :::* LISTEN 1583/config.js off (0.00/0/0)
tcp6 0 0 :::8000 :::* LISTEN 1586/node off (0.00/0/0)
tcp6 0 0 :::6881 :::* LISTEN 2811/utserver off (0.00/0/0)
tcp6 0 0 :::7780 :::* LISTEN 3977/httpd off (0.00/0/0)
tcp6 0 0 :::9412 :::* LISTEN 1372/java off (0.00/0/0)
tcp6 0 0 ::1:10024 :::* LISTEN 3582/amavisd (maste off (0.00/0/0)
tcp6 0 0 :::4040 :::* LISTEN 1372/java off (0.00/0/0)
tcp6 0 0 :::5672 :::* LISTEN 1373/beam.smp off (0.00/0/0)
tcp6 0 0 ::1:10026 :::* LISTEN 3582/amavisd (maste off (0.00/0/0)
tcp6 0 0 :::11211 :::* LISTEN 3477/memcached off (0.00/0/0)
tcp6 0 0 :::139 :::* LISTEN 1659/smbd off (0.00/0/0)
tcp6 0 0 ::1:3310 :::* LISTEN 3874/clamd off (0.00/0/0)
tcp6 0 0 192.168.0.15:45615 :::* LISTEN 1372/java off (0.00/0/0)
tcp6 0 0 ::1:10032 :::* LISTEN 3582/amavisd (maste off (0.00/0/0)
tcp6 0 0 :::33648 :::* LISTEN 1372/java off (0.00/0/0)
tcp6 0 0 :::8080 :::* LISTEN 1584/node off (0.00/0/0)
tcp6 0 0 :::80 :::* LISTEN 1506/apache2 off (0.00/0/0)
tcp6 0 0 :::4369 :::* LISTEN 1264/epmd off (0.00/0/0)
tcp6 0 0 :::8181 :::* LISTEN 2811/utserver off (0.00/0/0)
tcp6 0 0 :::22 :::* LISTEN 1006/sshd off (0.00/0/0)
tcp6 0 0 :::888 :::* LISTEN 1329/nginx -g daemo off (0.00/0/0)
tcp6 0 0 ::1:5432 :::* LISTEN 1267/postgres off (0.00/0/0)
Re: sabnzbdplus won't run anymore
Posted: January 14th, 2018, 1:33 pm
by sander
'node' is probably nodejs (a javascript engine).
If you kill it, and check port 8080 is unused, can you start sabnzbd as a daemon?
Re: sabnzbdplus won't run anymore
Posted: January 14th, 2018, 1:47 pm
by SparkyRih
The process just keeps coming back with a different PID when I kill it...
Edit: Where does sabnzbd store it's configuration? If I change the port it might be fine... I do have a file in /home/marc/.sabnzbd/sabnzbd.ini, but that doesn't seem to be the one?
Edit 2: It was the correct file anyway, I didn't look properly... I changed the port, no it runs fine again!
Thanks for you help!
Re: sabnzbdplus won't run anymore
Posted: January 15th, 2018, 5:25 pm
by sander
@jcfp ... if you're reading this: could the service log why it failed, for example "port 8080 in use"?
Re: sabnzbdplus won't run anymore
Posted: January 16th, 2018, 3:22 pm
by jcfp
Console output for these commands is "managed" by systemd
these days, the actual init script doesn't attempt to obscure or divert error messages.
The regular program log file should still have had this info in any case.
Re: sabnzbdplus won't run anymore
Posted: January 16th, 2018, 5:11 pm
by sander
jcfp wrote: ↑January 16th, 2018, 3:22 pm
The regular program log file should still have had this info in any case.
... you mean sabnzbd.log?
If so, @SparkyRih ... can you check your sabnzbd.log?
Re: sabnzbdplus won't run anymore
Posted: July 26th, 2022, 10:44 am
by Tf2n7vhFYATz
had the same problem, looked in the sabnzbd.ini and saw that I had updated the listen IP to 0.0.0.0. notice the extra "." at the end...removed the extra "." restarted the service and everything worked great....would be better to have extra error message to point us in the right direction in the future IMHO.
Re: sabnzbdplus won't run anymore
Posted: July 26th, 2022, 4:02 pm
by sander
Tf2n7vhFYATz wrote: ↑July 26th, 2022, 10:44 am
had the same problem, looked in the sabnzbd.ini and saw that I had updated the listen IP to 0.0.0.0. notice the extra "." at the end...removed the extra "." restarted the service and everything worked great....would be better to have extra error message to point us in the right direction in the future IMHO.
Ah, that's a bug. In the GUI, you can fill that out, and it's accepted. And then SAB won't start. Not good.
And SAB even says:
Open a Terminal window and type the line (example):
/home/sander/git/sabnzbd/SABnzbd.py --server 0.0.0.0.:8081
... with the trailing dot.
And stdout says:
Fatal error:
Unable to bind to port 8080 on 0.0.0.0.. Some other software uses the port or SABnzbd is already running.
... which is false info too.