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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 64 Next › Last »

async commented on 2020-08-10 03:42 (UTC) (edited on 2020-08-10 03:45 (UTC) by async)

I really don't mean to sound ungrateful, I appeciate all of the hard work fryfrog has put in here, but this package seems to constantly break and is configured in a super opinionated way that is very different from how others use the application. I just spent the last two hours trying to get it to work after the recent updates, and I'm still stuck on:

Unrecoverable error in the server. Traceback (most recent call last): File "/opt/sabnzbd/cherrypy/_cpwsgi.py", line 189, in trap File "/opt/sabnzbd/cherrypy/_cpwsgi.py", line 105, in call File "/opt/sabnzbd/cherrypy/_cpwsgi.py", line 438, in tail File "/opt/sabnzbd/cherrypy/_cpwsgi.py", line 244, in init File "/opt/sabnzbd/cherrypy/_cpwsgi.py", line 323, in run File "/opt/sabnzbd/cherrypy/_cptree.py", line 134, in get_serving File "/opt/sabnzbd/cherrypy/process/wspbus.py", line 225, in publish ChannelFailures: OperationalError('unable to open database file',)

Would anyone be willing to create a more neutral and stable package?

fryfrog commented on 2020-08-09 16:54 (UTC)

@francoism90: I've rebooted a bunch of times (been running 3.0.0 since alpha w/ basically this PKGBUILD), it never fixes via sysusers.

@tixetsal: Yeah, having folder/config not in /opt would just be totally ignored. But you could by hand put the things in the right place and it'd be fine.

francoism90 commented on 2020-08-09 16:31 (UTC) (edited on 2020-08-09 16:31 (UTC) by francoism90)

@fryfrog Yeah, you cannot do this when running. I don't know if the user is updated on reboot.

You could adding a simple stop command, but I should just warn people if possible. Thanks for the upgrade btw. :)

tixetsal commented on 2020-08-09 16:22 (UTC)

FYI, I was one of the folks who reported losing history and moving things manually, but in answer to your question: I DID have my oldnzbs folder in a non-standard location. I just ran the latest upgrade, and all my history was retained and everything worked well!

fryfrog commented on 2020-08-09 15:36 (UTC)

Mine was still set to /opt/sabnzbd, so I got to test it. You can't change it while running, so I think most will get the error and be told to do it themselves after stopping.

francoism90 commented on 2020-08-09 08:44 (UTC)

$ cat /etc/passwd | grep sab
sabnzbd:x:977:977:SABnzbd user:/opt/sabnzbd:/sbin/nologin

I think you indeed need to run usermod as well.

fryfrog commented on 2020-08-09 06:01 (UTC)

@mhicklen: Can you confirm the user's homedir isn't getting changed? The package is using sabnzbd.sysusers, so I'd think that would override?

fryfrog commented on 2020-08-09 06:00 (UTC)

@francoism90: That is a good idea, I switched to cp to get the folders to /var/lib/sabnzbd and then just added .saved to the files/folders left in /opt. That way they can't accidentally overwrite the new files in /var/lib/sabnzbd and anything running from /opt/sabnzbd will stop working still.

francoism90 commented on 2020-08-09 05:02 (UTC)

I would suggest to use cp instead of moving the config files to the new location and/or maybe just copy everything as SAB should convert does if I'm not mistaking.

sysfs commented on 2020-08-08 23:06 (UTC)

@fryfrog I ran into some issues.

I think we'll need a usermod to update the homedir for the user.

I think we'll also need a way of ensuring that things get moved or copied over proper. I lost all my settings, and my custom postprocessing scripts weren't brought over, either.

I'm having trouble with the new version now -- I've blown it completely away from the disk and reinstalled and I can't get it to start up, even when dropping into a shell for the user. The python script doesn't output anything. Will continue to tinker.