Support Forum

That's gnome devs deciding tray icons are a thing of the past, thinking desktop notifications can serve as a complete replacement. I even added an xapp implementation of the sab tray icon, so it should work on most desktop environments. If you ever figure out a way to get it to show up on gnome, do ...

sander wrote: ↑

February 18th, 2021, 8:43 am

What kind of stripped down OS is this?

Probably using some alternative c standard lib without memory management stuff (dietlibc or similar, as typically found in embedded systems). Checking at startup like puzzled proposed should be an easy fix.

@sander iirc par2 can handle subdirs these days, at least its changelog seems to suggest so. The substitution of the directory separator with a plus sign is probably sab's doing: there's some function in filesystem.py doing that, might be related to sanitizing input or safeguarding against directory...

astr0b0y wrote: ↑

February 15th, 2021, 12:04 am

Looks like it’s an ISP issue for me.

Probably, as everyone complaining about speed in this thread (and not hiding behind a vpn) appears to be from the same country and on the same isp.

Looks like you installed a broken systemd service of some kind in /etc/systemd/system/sabnzbdplus.service. Packages (from both ppa and official ubuntu repos) still only ship an init.d script which works fine. Use that if you can; you will have to remove the native systemd service file first though o...

The basics work, explanation texts still need a refresher though. Found an inconsistency in the current unwanted extension handling too, so I'm going to write some tests for that stuff before making a PR. Using Whitelist mode without a carefully curated list of extensions could be frustrating, but t...

If it's added as an advanced option then the user can be expected to figure this out themselves. It would be good if anyone has any ideas about how to make it easier, though. Could make it a variation of the current unwanted extension feature. Basically, add a simple boolean option to make that lis...

And no i dont want to open NAS to the world. An often overlooked but simple and effective way: many indexers offer a 'shopping cart' for nzb files that they make available as an rss feed. Configure sab to read the cart rss feed; then access the indexer from anywhere and simply add stuff to the cart...

Both of which give me no errors when running. Yet still this process is running: 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 proc...

Code for an autoresume function is currently being worked on; until then, resuming requires an explicit action. That action can be a human pressing a button, but also easily be scripted using the api, documentation here.

Stop using outdated ubuntu versions, base your vm on the latest ubuntu long term support release (20.04/focal); Stop using broken instructions from random blogs, follow the ones on the sabnzbd wiki instead; Stop adding broken systemd service files, the sabnzbdplus package comes with a perfectly fun...

Nice to know you did find a workaround. The PATH probably isn't the issue here, that can be annoying but only changes the order and/or locations the os searches when running a program without supplying a full path, e.g. just "sabnzbdplus" (also used by the desktop entry, see /usr/share/applications/...

No idea why rdp would do that. Is /usr/bin "gone" entirely when connected via rdp or does it just turn /bin into a copy of /usr/bin? What if you call sab with its full path /usr/bin/sabnzbdplus? Alternatively, maybe setting it up as a service (add a username in /etc/default/sabnzbdplus so it starts ...

2020-12-27 11:55:49,138::INFO::[sabnzbdplus:1150] Full executable path = /bin/sabnzbdplus It appears the sabnzbdplus executable being run is installed in /bin. That in turn causes the application to not find the interface templates, because the path to those is set in constants.py as a relative pat...

The init script isn't the problem, it's strict enough not to randomly select different configs. There's a second mechanism starting sab with a different config but at the same port, most likely a redundant systemd service you added (in /etc/systemd/ or /lib/systemd/) under a different name than sabn...