[nzbget] NZBget 0.7.0 download and discussion

[hugbug]

Version r380 has not that much changes comparing to version r357 - a few small new features and fixes but nothing that could cause such a big difference in CPU usage.

I'm still thinking the reported problems have nothing to do with NZBGet but rather a general NMT issue possibly caused by other NMT functions (video playback etc.) and therefore should not be reproducible.

If someone having issues with r380 would like to make the program better and has some time for testing please make the following test:

• Uninstall NZBGet;
• Reboot device;
• Install r380;
• Setup your news-server data (do not change any other settings);
• Reboot device;
• Try to download nzb-files.
  

If the problem still exist please reinstall version r357 using the same instructions (do not change any config settings except of news server data). Is the problem gone? If so please make the test few more times with r380 and r357 to be sure you can always reproduce the problem with r380 but it never occur with r357. You should use the same nzb-files for testing. You should also do the same things on NMT (watch the same movie ;-) ).

There are over 1500 downloads of r380. There should be people who doesn't feel r380 is worse than previous versions. Are there any?

[RedHat]

I really would like to help and test things out. But that wouldn't be a good test. My mainboard is not good, I have freezing movies all the time now.

Besides that, how can a previous version be installed? I know the points where I had problems with 380, so I can test that. I installed 380 with CSI.
I downloaded 357 from sourceforge. So how can I install 357? Just by copying it over 380?

Thanks

[hugbug]

(02-23-2010 10:18 AM)RedHat Wrote:  I downloaded 357 from sourceforge. So how can I install 357?

• Uninstall existing version.
• Download a csi-package from sourceforge (the one with word "csi" and zip-extension). I also posted direct links in post #290.
• Then use command "Install from file" in CSI, it's somewhere in the menu. It installs the package in the same way it installs packages from repository except the package is taken from disk instead of being downloaded.

[RedHat]

Thanks, now I understand the procedure.
Will do.

(02-23-2010 10:48 AM)hugbug Wrote:  

• Uninstall existing version.
• Download a csi-package from sourceforge (the one with word "csi" and zip-extension). I also posted direct links in post #290.
• Then use command "Install from file" in CSI, it's somewhere in the menu. It installs the package in the same way it installs packages from repository except the package is taken from disk instead of being downloaded.

[defer]

were can I find version 342 of nzbget. I like to reinstall that one, to see the difference with version 380.
thanks

[hugbug]

CSI-packages for versions prior r357 were created by Ger. May be he has backup copies.

[Ger Teunis]

I've got the following versions, take you pick

100 series (A100/A110 etc)
http://repository.nmtinstaller.com/Appli...nzbget.zip (version 0.6.0)
http://repository.nmtinstaller.com/Appli...70-308.zip (version 0.7.0-308)
http://repository.nmtinstaller.com/[%20old%20]/nzbget070-317.zip (version 0.7.0-317)
http://repository.nmtinstaller.com/Appli...70-342.zip (version 0.7.0-342)

200 series (C200, A200)
http://repository.nmtinstaller.com/Appli...00-csi.zip (0.7.0-357)

[RedHat]

Thanks Ger, usefull links.!

[pbranly]

Hello

I did make the tests you describe several times

Everything stays the same; I install the -380 ----->I have the problem
I uninstall the -380 and install the -357 -----> no problem

I reinstall the -380 ----> problem

Please note that it seems that the problem is quite rare when you put only one short nzb file (as a lossless music CD) ; you have to put several nzb or a big nzb file to get the issue. (as a Blueray movie)

In the rare 0.0000001 % (!) of good work, I noticed in the traces that there are opened sessions of nzb files that are queued in addition to the the normal sessions of the actrive nzb one.

This never happens with any of the -357 and prior versions.


I also notice during those very rare periods that the "ps" command gives a lot of -nzbget processes and that it is enough to kill the last one to have during a short time the hand

I hope I am clear .....

Regards

Philippe

[hugbug]

pbranly
Thanks for the test.

1.

(02-26-2010 08:30 PM)pbranly Wrote:  In the rare 0.0000001 % (!) of good work, I noticed in the traces that there are opened sessions of nzb files that are queued in addition to the the normal sessions of the actrive nzb one.

What do you mean with nzb sessions?

2. You don't use bandwidth throttling (limiting of download speed), right?

3. Can you please test the version r374 too?

[pbranly]

(02-27-2010 10:28 AM)hugbug Wrote:  pbranly
Thanks for the test.

1.

What do you mean with nzb sessions?

------->I mean tentatives of connection to a server to get one of the files of a non "downloading" nzb; this can be seen in the real time trace screen.

2. You don't use bandwidth throttling (limiting of download speed), right?

------>I do use bandwidth reduction; I just have a poor 1 Mb/s; so except during the night, I limit to 80. Nevertheless, even without, it hangs
For information, I also use a complicated connection system: I use the two free newsgroup servers that work only with IPV6: As Syabas never wanted to implement the ipv6 layers in the nmt and never answered to my post (!!) I use the PC as a IPV4 to IPV6 gateway; so the configuration of the server is 192.168.2 % 192.168.1.1 (192.168.1.1 is the router and 192.168.1.2 is the address of the PC)
I have a post of that somewhere) http://www.networkedmediatank.com/showth...#pid192602

3. Can you please test the version r374 too?

-----> I did already tried with the same results

Hope it will help !

Regards

Philippe

[mmccking]

(02-26-2010 08:30 PM)pbranly Wrote:  Hello

I did make the tests you describe several times

Everything stays the same; I install the -380 ----->I have the problem
I uninstall the -380 and install the -357 -----> no problem

I reinstall the -380 ----> problem

Please note that it seems that the problem is quite rare when you put only one short nzb file (as a lossless music CD) ; you have to put several nzb or a big nzb file to get the issue. (as a Blueray movie)

In the rare 0.0000001 % (!) of good work, I noticed in the traces that there are opened sessions of nzb files that are queued in addition to the the normal sessions of the actrive nzb one.

This never happens with any of the -357 and prior versions.


I also notice during those very rare periods that the "ps" command gives a lot of -nzbget processes and that it is enough to kill the last one to have during a short time the hand

I hope I am clear .....

Regards

Philippe

maybe your nzb is over the 10000 KB default?

[lordy]

Hi, just a heads up, when I installed csi nzbget , right after fresh NMT apps install, but before running stock usenet client, then /share/.nzbget/{nzb,tmp} folders do not exist, but firmware nzbget cannot start via NMT Apps setup to create the folders (probably using same admin port as CSI nzbget ?). I created the folders manually and was good to go... (someone else mentioned in this thread also)

[PrairieSailor]

My internet connection was flaky while nzbget was downloading so there a ton of parts missing. The unpak (lordys) ran and tried to repair but there wasn't enough parts. Is there a way to force a re-download now of the incomplete parts?

[hugbug]

pbranly
There was a small change in bandwidth throttling in particular the sleep interval between download of small data chunks was reduced from 200 msec to 20 msec in order to provide better speed uniformity. May be that change has increased the CPU load significantly.

However it doesn't explain why you still have the problem even if you don't use bandwidth throttling.

Anyway I'll make a test binary using the same sleep interval as was before and send it to you for testing.

---

lordy
1. CSI-nzbget doesn't install properly if the firmware nzbget was never started.
2. you can't start firmware nzbget after installing CSI-nzbget because the start-command in menu refers to CSI-nzbget.

These are two of reasons why I want to change the installing behavior of CSI-nzbget.