For me at least v13 is the most stable version yet. Specifcally all the par2 edge case weirdness is gone.

 

Would like to see this plugin updated at it seems to not want to go past "NZBGet 12.0-testing-r927" whereas the current testing is really "NZBGet 13.0-testing-r963"

I think overbyrn is busy with other stuff at the moment, so can't work on this at the moment, unfortunately.

 

Have you compiled it for unRAID yourself? If so, pass it on, please! 

For me at least v13 is the most stable version yet. Specifcally all the par2 edge case weirdness is gone.

 

Would like to see this plugin updated at it seems to not want to go past "NZBGet 12.0-testing-r927" whereas the current testing is really "NZBGet 13.0-testing-r963"

I think overbyrn is busy with other stuff at the moment, so can't work on this at the moment, unfortunately.

 

Have you compiled it for unRAID yourself? If so, pass it on, please! 

 

Guys, I'll see what I can do.  As Neil says, I'm a tad busy as I'm currently about two months out from waving goodbye to the UK and saying hello USA.  House resembles a war zone and my unRAID box is about to be reduced to its component parts ready for shipping.  I'll do a v13 testing release from the current source, but it'll probably be many months until I'm able to do more.

Version of v13 testing branch built... nzbget-13.0-testing-r963

 

If you are running the regular 32bit version of the plugin and on the testing branch, then you should be offered an option to update to r963 of the v13 build.

 

Note: I don't have a dev unRAID server at the moment, so I have not been able to test this prior to release.

Upgrade itself went seamlessly. very professionally done.

 

However it defaulted to the base config and all manual changes were lost. backup your config first

Upgrade itself went seamlessly. very professionally done.

 

However it defaulted to the base config and all manual changes were lost. backup your config first

NAS, thank you for the feed-back.  Yep, config changes have been a pain to manage and it's always best to keep a copy of your config.  The plugin also makes a backup copy to the plugin directory before an update.  The underlying config file must remain relevant to the config options for NZBGet and this gets interesting when new config options are introduced or old ones removed/changed.  The author utilises a template system whereby when the config is written from within the application it ensures parameters and their values are written out to match what that version of NZBGet expects.  I try to account for that during an NZBGet update, but it doesn't always work out as well as I hope.

 

It's probably fair to say if someone wants to go from a stable anything to a testing anything, then assume the config will change sufficiently to need some manual intervention.

 

I'd offer to do some checking this end and make the version switch more robust, but that will mean getting sucked in a little more than I want at the moment.

TBH i would just require a user backs up first and leave it at that. Removes a bunch of checks and hurdles for you.

 

The NZBget export and import is pretty amazing anyway allowing selective subsection import etc

 

nice work now go pack

I backed up some of nzbget before upgrading, but actually forgot to do the settings backup.

 

I have seen that trashed in the past, but it was fine this time.

 

I did see nzbget crash the first time it downloaded something, I restarted it and it seems fine now.

 

Those of us who run the testing versions should expect this, I suppose. Generally, the testing versions are pretty solid though - I've only run testing versions since about 2009.

 

Sent from Moto G using Tapatalk

 

 

I'm testing this trying to replace SabNzb. I too got the

Mar 24 11:40:11 FileServer kernel: nzbget[13824]: segfault at 1c4f ip 4056bee1 sp 41068d8c error 4 in libc-2.11.1.so[404f2000+15c000] (Errors)

and have confirmed downgrading the zlib package fixes the problem, as discussed previously in this thread. Did anyone find a good way to do this permanently?

 

I'm concerned getnzb will start downloading and crash before the go script gets to it if I put it in there, and I also want to make sure it is executed after the couchpotato plugin starts up.

 

Lastly, those of you who were able to upgrade to V13, how did you do that exactly? I already have the latest version of the plugin, and when I try to update inside getnzb, it tells me "Automatic updates are not configured for your platform".

 

Lastly, those of you who were able to upgrade to V13, how did you do that exactly? I already have the latest version of the plugin, and when I try to update inside getnzb, it tells me "Automatic updates are not configured for your platform".

 

in your unraid nzbget config settings change your branch from stable to testing and apply changes

youll then be able to upgrade

Just installed this but the webui is asking for username and password what are they? I already tried the default nzbget and tegbzn6789. Thanks

Just installed this but the webui is asking for username and password what are they? I already tried the default nzbget and tegbzn6789. Thanks

The plugin tells you the username and password if you hover your mouse over the hyperlink to nzbget from within the webui.

 

Username: nzbget

Password: password

I am testing out nzbget coming from sabnzbd

 

all i did was remove username and password so both are empty and i installed nzbget-chrome extension i tried to send a nzb with it to nzbget and i get this

 

Communication error, retrying...

 

then

 

Communication error!

Cannot establish connection to NZBGet.

 

im on the nzbget 13.0-testing-r963 is this software not as good as sabnzbd?  any ideas where the logs are saved to see why its crashing?

 

EDIT:

ok nzbget makes no good logs but unraid has something i think is causing the problem

 

Apr 14 21:51:05 Tower kernel: nzbget[14066]: segfault at 1c4f ip 40579ee1 sp 40c76d7c error 4 in libc-2.11.1.so[40500000+15c000]

 

any ideas how to fix that?

I am testing out nzbget coming from sabnzbd

 

all i did was remove username and password so both are empty and i installed nzbget-chrome extension i tried to send a nzb with it to nzbget and i get this

 

Communication error, retrying...

 

then

 

Communication error!

Cannot establish connection to NZBGet.

 

im on the nzbget 13.0-testing-r963 is this software not as good as sabnzbd?  any ideas where the logs are saved to see why its crashing?

 

EDIT:

ok nzbget makes no good logs but unraid has something i think is causing the problem

 

Apr 14 21:51:05 Tower kernel: nzbget[14066]: segfault at 1c4f ip 40579ee1 sp 40c76d7c error 4 in libc-2.11.1.so[40500000+15c000]

 

any ideas how to fix that?

Did you try the fix posted on an earlier message in this thread? 

 

http://lime-technology.com/forum/index.php?topic=23423.msg294687;topicseen#msg294687

 

If that fixes your segfault issue, then it's because of conflicting versions of zlib. 

 

i see i have two packages of zlib

zlib-1.2.5-i486-4

zlib-1.2.6-i486-1

 

can i just delete the first one and update plugins the used the old one to the new one? is the reason it crashes because of two version or because nzbget needs specific version?

 

EDIT:

I tested out 1.2.6 also crashes the one in the other post works fine, i guess i am going to edit all the plugins so it installs that version not the newer one.

I made a script that uninstalls and installs the older zlib, and then starts NZBget using rc.d.nzbget  (which will only start it if it had not yet started or had already had time to crash). I then call that from the go script 1 minute after the go script finishes (using 'at now + 1 minute' I think), ensuring all the other plugins have finished installing. It's not pretty but it works. I can post up the specifics later if anyone wants.

i set every up was working fine and then it just lost all the settings everything went to default. I added a server again and then few minutes later again it reset to default any ideas what's going on?

 

EDIT:

 

i just set everything up and made a backup of the config hopefully it wont happen again.

I made a script that uninstalls and installs the older zlib, and then starts NZBget using rc.d.nzbget  (which will only start it if it had not yet started or had already had time to crash). I then call that from the go script 1 minute after the go script finishes (using 'at now + 1 minute' I think), ensuring all the other plugins have finished installing. It's not pretty but it works. I can post up the specifics later if anyone wants.

 

Yes please.

Here is how I am replacing the zlib library at boot.

 

Somewhere near the end in the go script:

#Downgrade zlib package for NZBGET to eliminate segfault while downloading
echo "/boot/scripts/downgrade_zlib.sh" | at now + 1 minutes

 

Contents of /boot/scripts/downgrade_zlib.sh

/etc/rc.d/rc.nzbget stop
removepkg zlib-1.2.5-i486-4
installpkg /boot/packages/zlib-1.2.3-i486-2.txz
wait 5
/etc/rc.d/rc.nzbget start

does nzbget extract files slower then sabnzbd? they both use unrar correct? could be just me but it feels like its a lot slower, nzbget does download faster 13MB/s vs 11MB/s.

 

does nzbget extract files slower then sabnzbd? they both use unrar correct? could be just me but it feels like its a lot slower, nzbget does download faster 13MB/s vs 11MB/s.

 

No.

 

Yes.

 

Yes.

does nzbget extract files slower then sabnzbd? they both use unrar correct? could be just me but it feels like its a lot slower, nzbget does download faster 13MB/s vs 11MB/s.

 

No.

 

Yes.

 

Yes.

 

damn i think something is wrong its extracting at arond 12MB/s on a cache drive  i am going to test sabnzbd, this feels like i am writing to the array because that's around the speed i get

nzbget doesn't unpack, unrar does. Do a speed test with SABnzbd and nzbget, but use the same NZB each time.

 

A RAR set can be packed in different ways.

has anybody got the "testing" branch to work on unraid 6?  I done everything I know to do and it still just gives me v12 (vs. 13...).  Just trying to understand if just me or not...

has anybody got the "testing" branch to work on unraid 6?  I done everything I know to do and it still just gives me v12 (vs. 13...).  Just trying to understand if just me or not...

There's a reason for that.  I've not compiled a 64bit version of the testing branch.  Last compiled version for x64 is 12.0 stable.  Choosing testing branch if using the 64bit version of the plugin will only install the v12 stable at this time.

 

 

has anybody got the "testing" branch to work on unraid 6?  I done everything I know to do and it still just gives me v12 (vs. 13...).  Just trying to understand if just me or not...

There's a reason for that.  I've not compiled a 64bit version of the testing branch.  Last compiled version for x64 is 12.0 stable.  Choosing testing branch if using the 64bit version of the plugin will only install the v12 stable at this time.

 

Ok....thx.  Happy it isn't just me. 

 

Note to others:  Moving from r13 on unraid 5 to r12 on unraid 6 crapped out the config file (error on load and wiped out when hit save in settings)...... live and learn (should have backed up).