Support Forum

Sorry for bumping this thread, but what was the fix for this? I'm on latest release (2.3.9) and I'm experiencing this problem. Do I have to build from source to get the fix? https://github.com/sabnzbd/sabnzbd/commit/d7fc7f02de6ffe84a94635cd6a71ce8083b36548 There's no release yet that includes that ...

Just put it on pastebin and mention that in a reply here along with the unique id of the paste.

Linux mint is an ubuntu derivative, just follow the ppa instructions for that and you won't have any problem updating.

The flattened dir structure for the Movie stuff is probably caused by category settings, in which "ending the path with an asterisk * will prevent creation of job folders". Tv could be similar, but might also involve sorting settings. Anyway, start with the category stuff and go from there.

You can run multiple scripts by having a single, very simple script call as many others as you want, passing along the command line arguments. If all scripts are shell, you could also source them. See viewtopic.php?f=9&t=15392&p=86847#p86852

A PEBKAC after all ... ? The git version is running now as wanted. It seems the ~/.sabnzbd/logs/sabnzbd.log I was looking at is not updated at all, so I was looking at old info? Could well be, the packaged version is patched to change some homedir handling , see https://sources.debian.org/src/sabnz...

Does DirectUnpack pause until the repair scan at the end? If it's possible (but probably tricky) you could track and repair during download, the direct-unpacking could resume and the file could continue playing. Par2 needs the data from a (mostly) complete download in order to do a repair; i.e. the...

Another benefit is you can access files shortly after they start downloading, I would use DirectUnpack to start playing files, but the problem is I can't tell whether it's going to work and have to delete the download if I'm looking to start playing a file now. You can't know for certain whether a ...

Could this be a system policy that's unhappy with Sab resources? That would either just leave sab to deal with its limited resources, or result in a kill signal (9) from the oom killer. Not an interrupt (2) or a regular term signal (15). The latter would be what sab receives when someone tries to t...

Thanks for the feedback, docs should be fixed now with commit 380be83 and pr 1192

Since I don't need any logging at all, I would like to have the opportunity to completely disable any logging in sabnzbd. I also tried to set logging parameters in sabnzbds config file, but they get changed back automatically on start. Sab has a command line option for this, setting it to -1 disabl...

Something in that list of plesky stuff to be removed has been designed to conflict with something in the list of mostly bog standard packages to be installed. I have a hunch it's going to be avahi or consolekit, but since I don't run anything plesk the fastest way to figure that out the details is f...

what url are you using for that connect? dns issue/timeout?

sander wrote: ↑

October 2nd, 2018, 8:08 am

I think the "md5" is the problem

It is indeed. Support for md5 message digests was removed from openssl some time ago, because it's too weak (too easy to generate hash collisions).

autofile = open("AutoNames.txt","a+") Using a relative filename here may be the problem. It assumes that the script has a work dir, that it is always the same, and writable at that. That might be true in your tests but not when run by sab. Suggest you check the script indentation. Python requires i...