Package Details: sabnzbd 4.3.3-1

Git Clone URL: https://aur.archlinux.org/sabnzbd.git (read-only, click to copy)
Package Base: sabnzbd
Description: A web-interface based binary newsgrabber with NZB file support
Upstream URL: http://www.sabnzbd.org
Keywords: network usenet
Licenses: GPL
Submitter: esh
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 270
Popularity: 0.61
First Submitted: 2007-11-09 16:21 (UTC)
Last Updated: 2024-08-21 15:57 (UTC)

Latest Comments

« First ‹ Previous 1 .. 35 36 37 38 39 40 41 42 43 44 45 .. 64 Next › Last »

Evilandi666 commented on 2012-10-06 23:10 (UTC)

Could you please add /usr/lib/tmpfiles.d/sabnzbd.conf and /etc/conf.d/sabnzbd_systemd to the backup section? Otherwise it is a bit annoying for systemd users who don't use the standard user. The update deleted half of my config..:( Thx!

stefanwilkens commented on 2012-10-03 11:45 (UTC)

I created a wiki article: https://wiki.archlinux.org/index.php/SABnzbd Please add, might help prevent some of these recurring questions :)

<deleted-account> commented on 2012-10-01 11:02 (UTC)

@archtaku: Ah, thank you! That was somewhat trivial... I hope this helps another poor sod overlooking the obvious :)

terminalmage commented on 2012-09-28 04:37 (UTC)

@poltak: are you running sabnzbd as a user other than the sabnzbd user? If so, it might be permissions issues on /run/sabnzbd that are preventing the pidfile from being created. You might need to chown/chmod the /run/sabnzbd directory to make it accessible.

<deleted-account> commented on 2012-09-28 03:20 (UTC)

Mine doesn't even create a PID file. I've made sure that it's specified to create it in /run/sabnzbd using the --pid argument in the .service file's ExecStart parameter. Just running "sabnzbd" as user works fine and I can access the web UI, although trying "sabnzbd --pid /run/sabnzbd" as same user does not create a PID file at given path, and also does not even start the program (because the PID file doesn't exist, it times out starting the URLGrabber). I've searched through my system for all present PID files while running sabnzdb, but none for this process. Of course, I want to be able to run it as a systemd daemon which requires the PID file. Anyone had similar issue with creation of PID file (from --pid arg)?

Revelation60 commented on 2012-09-26 07:32 (UTC)

That's what I said in my reply ;)

stefanwilkens commented on 2012-09-25 18:25 (UTC)

excuse the spam, my previous reply here has a simple answer: When starting sabnzbd with https enabled, the pidfile changes from sabnzbd-8080.pid to sabnzbd-9090.pid (or whatever you've set your normal / ssl ports to in sabnzbd.ini). The fix is to let systemd be aware of this though the service file: 1, edit /etc/systemd/system/sabnzbd.service to use sabnzbd-9090.pid 2. run "sudo systemctl --system reload"

Revelation60 commented on 2012-09-25 18:21 (UTC)

@stefanwilkens: did you change the port in the config file and in the sabnzbd.service file as well? If you haven't done the latter, systemd will look for the wrong pid file.

stefanwilkens commented on 2012-09-25 18:12 (UTC)

Another minor issue: When enabling https (through sabnzbd.ini), systemctl start sabnzbd.service does start sab with ssl support on port 9090, yet systemd doesn't seem to be aware that it actually started. Sab is available and working, but after some time (~30 seconds) systemd appears to run into a time-out and kills the service. This is evident in the status report: [stefan@lapsteef sabnzbd]$ sudo systemctl status sabnzbd.service sabnzbd.service - SABnzbd binary newsreader Loaded: loaded (/usr/lib/systemd/system/sabnzbd.service; disabled) Active: failed (Result: timeout) since Tue, 25 Sep 2012 20:03:02 +0200; 13s ago Process: 1800 ExecStart=/bin/sh/ -c python2 ${SABNZBD_DIR}/SABnzbd.py ${SABNZBD_ARGS} --pid /run/sabnzbd (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/sabnzbd.service Again, it does start successfully with ssl support. It's systemd that seems to be unaware of this and thus kills it.

Revelation60 commented on 2012-09-24 19:08 (UTC)

@archtaku, in the comment I mention that you can't use environment file variables for the PIDfile, nor for User and Group. The same is true for variables in variables in the environment file. It didn't work in previous versions of systemd, perhaps it works now. I'll check if it does. Anyhow, I don't like the aggressive and disrespectful tone of your comments. @stefanwilkens, I'll see if I can find the cause.