January 19, 201412 yr Hi overbyrn, could you maybe include a newer unrar Version in your package, because the included one is not compatible with Winrar which some uploads now use. I have a package here i compiled and used with Influencers Sabnzbd, but because Influencer seems to have taken a break and Sabnzbd lacks 7Zip support i am now using your NZBget package. You can find the package for unrar 5.0.14 here: http://dl.bintray.com/darkside401/unrar5-unraid/unrar-5.0.14-i486-1cf.txz It is hosted on bintray because it was the easiest solution for me.
January 20, 201412 yr Author Hi overbyrn, could you maybe include a newer unrar Version in your package, because the included one is not compatible with Winrar which some uploads now use. I have a package here i compiled and used with Influencers Sabnzbd, but because Influencer seems to have taken a break and Sabnzbd lacks 7Zip support i am now using your NZBget package. You can find the package for unrar 5.0.14 here: http://dl.bintray.com/darkside401/unrar5-unraid/unrar-5.0.14-i486-1cf.txz It is hosted on bintray because it was the easiest solution for me. Darkside, thank you for the updated unrar. I did a similar package a while ago to use on a private SABnzbd plugin fork but yours is likely more up to date than mine. I removed the doc, man and install dirs from your package to keep things clean and stored locally on my Dropbox with the rest of the packages used. The plugin has been updated to reference the newer package and change committed to git. Thanks again, overbyrn.
January 20, 201412 yr A huge thank you to Overbryn for creating such a great plugin! Until recently switching to nzbget, I was running influencer's SABnzbd on a Pentium 4 3.2GHz machine and the performance was adequate. Since the switch, I have been experiencing some extremely long repair times (12GB download - 7 hour repair). While I am certainly running on outdated hardware, I believe much of this issue was caused by nzbget's use of libpar2 compared to SABnzbd's use of par2cmdline. In hopes of correcting this issue, I recompiled libpar2 incorporating nzbget's recommended patches. Since doing so, repair times have plummeted (12GB download - 25 minute repair). Other than a significantly smaller size, I cannot say what the differences are between Overbyrn's libpar2 and the attached version. Nonetheless, hopefully this helps out any others who are experiencing extremely long repair times. libpar2-0.2-i486-1rj.tgz.zip
January 20, 201412 yr I don't quite follow what you've done to make libpar2 faster -- have you included the multicore (TBB) modifications? Sent from Moto G using Tapatalk
January 20, 201412 yr Repair speed depends on the amount of damaged data and of the par2 block size (which is choosed when building par2 files). You can't compare repair speed from one download to another. The patches included with NZBGet fix few seg faults, they don't make libpar2 faster.
January 20, 201412 yr Author A huge thank you to Overbryn for creating such a great plugin! Until recently switching to nzbget, I was running influencer's SABnzbd on a Pentium 4 3.2GHz machine and the performance was adequate. Since the switch, I have been experiencing some extremely long repair times (12GB download - 7 hour repair). While I am certainly running on outdated hardware, I believe much of this issue was caused by nzbget's use of libpar2 compared to SABnzbd's use of par2cmdline. In hopes of correcting this issue, I recompiled libpar2 incorporating nzbget's recommended patches. Since doing so, repair times have plummeted (12GB download - 25 minute repair). Other than a significantly smaller size, I cannot say what the differences are between Overbyrn's libpar2 and the attached version. Nonetheless, hopefully this helps out any others who are experiencing extremely long repair times. Thank you for the kind words. I'm happy the plugin has been of use to you. With regard to the issue of libpar, the libpar package I distribute with NZBGet was compiled incorporating the patches from nzbget. As hugbug has stated, these patches themselves do not make libpar faster and perhaps there are other factors such as the block size used during par2 creation and the level of damaged data during a repair. Did you only compile libpar 2.0.2 with the two patches as detailed in the README within nzbget source? If so, then that is the same as I have done also. I wonder perhaps if there is some other reason why you are seeing an increase in repair speed?
January 20, 201412 yr Thanks for integrating the new Winrar Version. Now i can switch to NZBget to get the 7Zip support i need.
January 21, 201412 yr A huge thank you to Overbryn for creating such a great plugin! Until recently switching to nzbget, I was running influencer's SABnzbd on a Pentium 4 3.2GHz machine and the performance was adequate. Since the switch, I have been experiencing some extremely long repair times (12GB download - 7 hour repair). While I am certainly running on outdated hardware, I believe much of this issue was caused by nzbget's use of libpar2 compared to SABnzbd's use of par2cmdline. In hopes of correcting this issue, I recompiled libpar2 incorporating nzbget's recommended patches. Since doing so, repair times have plummeted (12GB download - 25 minute repair). Other than a significantly smaller size, I cannot say what the differences are between Overbyrn's libpar2 and the attached version. Nonetheless, hopefully this helps out any others who are experiencing extremely long repair times. Thank you for the kind words. I'm happy the plugin has been of use to you. With regard to the issue of libpar, the libpar package I distribute with NZBGet was compiled incorporating the patches from nzbget. As hugbug has stated, these patches themselves do not make libpar faster and perhaps there are other factors such as the block size used during par2 creation and the level of damaged data during a repair. Did you only compile libpar 2.0.2 with the two patches as detailed in the README within nzbget source? If so, then that is the same as I have done also. I wonder perhaps if there is some other reason why you are seeing an increase in repair speed? hugbug and overbyrn, I appreciate your replies. When I recompiled libpar2, I only included the 2 patches detailed in the nzbget source README making the file for all intensive purposes identical to overbyrns. My comparison was actually on the same download (after waiting for 4 hours, I completely deleted the half completed first attempt...) and did see a significant increase in repair speed with the second attempt/newly compiled libpar2. Obviously, I falsely believe that the increase in repair speed was due to libpar2. It is possible that download #2 may have been more complete than download #1. Thinking back, it may be more likely that changing the nzbget ParScan from Auto to Limited. Nonetheless, I'm thrilled with the switch from SABnzbd to nzbget!
January 21, 201412 yr One way to really speed up repair would be to write a script to call the multicore par2cmdline (including parameters) rather than use the built-in single core par2lib. For long repairs, I'll cancel nzbget's built-in par2lib repair and run: par2 r -m2048 whatever.par2 * That's using the TBB par2cmdline and the -m parameter lets you assign more RAM during the repair which does seem to help as well. I've seen repairs go from (say) 2 hours to 20 minutes (ish). Apparently such a script wouldn't be too hard to write, but it's beyond my ken. ETA: One benefit of par2lib is that it can scan, pause, get pars and repair without scanning again, saving a lot of time with a large NZB. However, the script could call "par2 r" rather than "par2 v" if you set nzbget to download all pars rather than just one. That way it would still only need to do one scan. That's how I'd set mine up if such a script was available, as I have a fast connection and an unlimited news server.
January 24, 201412 yr Any thoughts or plans for a 64bit version of this plugin? It is the only one I am waiting on! *chomps at the bit*
January 24, 201412 yr Author Any thoughts or plans for a 64bit version of this plugin? It is the only one I am waiting on! *chomps at the bit* Check my Github page.
January 24, 201412 yr Any thoughts or plans for a 64bit version of this plugin? It is the only one I am waiting on! *chomps at the bit* Check my Github page. Thank you! Nabbed and it is running great!
January 24, 201412 yr Nice work, overbyrn. I set up a test system and it looks like I'm doing something wrong? Jan 24 14:18:53 N36L logger: Installing user plugins Jan 24 14:18:53 N36L logger: installing plugin: nzbget_x64_overbyrn Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): /boot/config/plugins/nzbget_x64_overbyrn.plg:33: parser error : Specification mandate value for attribute data-pjax-transient in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): /boot/config/plugins/nzbget_x64_overbyrn.plg:54: parser error : Specification mandate value for attribute data-pjax-transient in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): /boot/config/plugins/nzbget_x64_overbyrn.plg:180: parser error : Specification mandate value for attribute itemscope in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger:
January 25, 201412 yr Nice work, overbyrn. I set up a test system and it looks like I'm doing something wrong? Jan 24 14:18:53 N36L logger: Installing user plugins Jan 24 14:18:53 N36L logger: installing plugin: nzbget_x64_overbyrn Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): /boot/config/plugins/nzbget_x64_overbyrn.plg:33: parser error : Specification mandate value for attribute data-pjax-transient in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): /boot/config/plugins/nzbget_x64_overbyrn.plg:54: parser error : Specification mandate value for attribute data-pjax-transient in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): ^ in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Jan 24 14:18:53 N36L logger: Warning: simplexml_load_file(): /boot/config/plugins/nzbget_x64_overbyrn.plg:180: parser error : Specification mandate value for attribute itemscope in /usr/local/sbin/installplg on line 13 Jan 24 14:18:53 N36L logger: Looks like you downloaded the HTML. Right-click RAW and save as
January 25, 201412 yr Looks like you downloaded the HTML. Right-click RAW and save as Thanks, that worked. I would have never worked that one out.
January 27, 201412 yr When i try the 64 bit version i am getting https://dl.dropbox.com/u/572553/UnRAID/packages.generic/libsigc++-2.2.10-x86_64-2alien.tgz ... bad download, deleting thanks
January 28, 201412 yr When i try the 64 bit version i am getting https://dl.dropbox.com/u/572553/UnRAID/packages.generic/libsigc++-2.2.10-x86_64-2alien.tgz ... bad download, deleting thanks I have been able to locate the files elsewhere except for this one file libpar2-0.2-x86_64-1rj.tgz Any body care to share?
January 28, 201412 yr Author When i try the 64 bit version i am getting https://dl.dropbox.com/u/572553/UnRAID/packages.generic/libsigc++-2.2.10-x86_64-2alien.tgz ... bad download, deleting thanks I have been able to locate the files elsewhere except for this one file libpar2-0.2-x86_64-1rj.tgz Any body care to share? I am in the process of reorganizing my Dropbox package download locations, to make life easier to manage 32bit and 64bit plugins. Should be done soon. Keep an eye on my Github for an updated commit to nzbget 64bit plugin soon. I will post an update when complete here also. Thanks, overbyrn
February 18, 201412 yr Thanks for that, I missed that info. I've got it working now but it is very unstable, every time I try to add an NZB it crashes the program and I have to restart the service If you are using Influencer's plugins he upgrades the zlib which breaks nzbget. To fix this login to your unRAID server and run the following commands: removepkg zlib-1.2.5-i486-4 installpkg zlib-1.2.3-i486-2.txz Sickbeard, etc. will still work and now nzbget won't crash. Is there anyway to get this change to persist through a restart?
February 20, 201412 yr Thanks for that, I missed that info. I've got it working now but it is very unstable, every time I try to add an NZB it crashes the program and I have to restart the service If you are using Influencer's plugins he upgrades the zlib which breaks nzbget. To fix this login to your unRAID server and run the following commands: removepkg zlib-1.2.5-i486-4 installpkg zlib-1.2.3-i486-2.txz Sickbeard, etc. will still work and now nzbget won't crash. Is there anyway to get this change to persist through a restart? Add it to your go file?
February 27, 201412 yr Kudos for this addon. Very professionally put together Update: For some reason the fix to change the default user from root to nobody never worked. As you might expect this caused all sorts of weird perm issues.
March 3, 201412 yr hi - firstly thanks for the work and getting the plugin setup. I had some initial issues with segfaults much like some other users which meant that NZBGet kept 'crashing' and loosing connection. As mentioned, it was down to some issues with zlib-1.2.5-i486-4 therefore I installed the NZBGet plugin and then ran the following commands: removepkg zlib-1.2.5-i486-4 wget http://slackware.cs.utah.edu/pub/slackware/slackware-13.1/slackware/l/zlib-1.2.3-i486-2.txz installpkg zlib-1.2.3-i486-2.txz That fixed the issues with the crashing and I managed to get downloads working fine The only problem I have now is that Sickbeard refuses to move completed files to their relevant directories during the post processing steps, it does however copy them. This is different behaviour to how my Sickbeard and SABNZB setup used to work (Sickbeard post processing would move the file across and then delete the original source which was all nice and neat). I think it may be due to permissions or some other setting - just wanted to know if there was anyone else who may have encountered this issue and what they did to overcome the problem. ohh and one last thing - is it normal for there to be constant write activity to the disk where the plugin is installed to? This means that disk and my parity drive never spin down. I've checked and there is no active file being downloaded and i cant understand what is writing to the disk. I am fairly sure it is NZBGET related since when i stop the plugin (via unraid plugin settings page) the write activity on the disk stops. Any help would be really appreciated! thanks
March 19, 201412 yr 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"
Archived
This topic is now archived and is closed to further replies.