Support Forum

You're not supposed to write to the program folder. Where do you keep your INI file and admin/log folder? I hope in the user profile. When SABnzbd sees an INI file in the program folder it falls back to ancient (rel 2.5) behaviour. It will not try to write an INI file to the program folder spontane...

I suspect this has to do with the fact that Windows 7 sets the read-only attribute on EVERY folder, regardless, and then proceeds to ignore it. It wreaks havoc with things like sabnzbd that try to write files to that directory. Seriously, see if your c:\program files(x86)\sabnzbd folder has the read...

Wow! It worked. I tried everything and that did the trick. Something so easy was so difficult. I guess I was getting so frustrated and missed thinking of doing that. Note that if the read-write issue was causing your problem, you may be best advised to symlink /usr/local/sabnzbd (or even /usr/local...

I seem to get a lot of inquiries about problems installing the SABnzbd+ port or starting SABnzbd+ on these systems. Note that the news/sabnzbdplus port is tested against vanilla FreeBSD systems only, therefore I can't guarantee that it works on FreeNAS or NAS4Free or any other appliance-based system...

Note that this package is tested against vanilla FreeBSD releases, and not NAS4Free/FreeNAS, or other appliance-type installations. So, in terms of that, I can't really help much in terms of what's going on. I suspect your issue is likely due to the root file system being mounted read-only in these ...

Not something FreeBSD would do. I'm not familiar with NAS4Free, but some appliance-based embedded systems will mount a read-only partition in memory, the contents of which will be overwritten on boot as it will fall back to the "known good" values. This makes for easy upgrading and support...

My diff has been submitted and is waiting committal before it will show up in your ports tree. If you want to update to 0.6.15 now, apply the following diff to your /usr/ports/news/sabnzbdplus directory and rebuild the port (basically just changing version name and updating package checksums -- noth...

You may be right -- I'll do some research. I believe I had another report of a similar problem via email recently, so I'll see if I can replicate it on my end (should be easy), and if I can, I'll fix the script. I may not bother making a new port revision just for the init script, however, since it ...

Glad to hear it!

Try my suggestions in the post above. If you change it to a local disk or CIFS/SMB, does the problem persist?

If so, you may need to avoid NFS for temporary storage.

Unfortunately, I have no visibility into when ports are built as packages and provided on the FTP site. However, I suspect that no new ports are actively being added into the old FreeBSD 7.3 tree. FreeNAS 8.0+ (assuming it's built against the FreeBSD source of the same version) may have a different ...

You're right, I think I'll need to change the Makefile to include par2cmdline-tbb as a recognized option. You could edit it yourself and change the line that looks like: RUN_DEPENDS+= par2repair:${PORTSDIR}/archivers/par2cmdline to read: RUN_DEPENDS+= par2repair:${PORTSDIR}/archivers/par2cmdline-tbb...

So a few things. 1) Can you reproduce this problem at will, or is it intermittent? 2) If you can reproduce it at will, if you change your temp storage to a local disk, does the problem cease? If so, we can probably narrow this down to an issue with NFS (probably its notorious file locking) instead o...

The overworked commiters for FreeBSD have finally committed my changes to 0.6.9 as of today. Feel free to update your ports trees and install the latest version! Note there have been a few changes to news/sabnzbdplus for the 0.6.9 port: Includes the SABnzbd-packaged version of cherrypy instead of re...

Thanks for the feedback. I'm not sure what the holdup on getting 0.6.9 committed is. If you're feeling lucky and want the port ahead of it being committed, you can visit the PR here: http://www.freebsd.org/cgi/query-pr.cgi?pr=160710 Download the diff I supplied at the bottom of the thread (not the o...