i've seen this too, but this may just be a reflection of hellanzb operates under rate limiting and not a bug in lottanzb
Please see attached video - my settings rate limit hellanzb to 450 (about half the 8-20 megabit rate on my net connection). You will see it will burst to >2000, the sit at zero until the rate limiting is complete - both the hellanzb console and lottanzb are visible in the capture.
Also, i've noticed that when i change hellanzb maxrate after startup, that the console starts updating at odd intervals making the transfer rate display show 0 even more often even though data is flowing in.
Please forgive my delay in replying to this bug report. The user Gio has reported a problem which is most probably related or identical to this one: https://answers.launchpad.net/lottanzb/+question/33708. As I've written it in the answer section, this the issue doesn't seem to be a result of HellaNZB's bandwidth throttling feature, since the value that indicates the remaining MBs to download constantly decreases.
@Thomas: You could try the same as I suggested Gio to do: "Run HellaNZB from command line without LottaNZB ("hellanzb -c ~/.lottanzb/hellanzb.conf" if you're using LottaNZB's standalone mode) to see if the download speed is displayed there. You could also post HellaNZB (most likely in ~/.hellanzb/log) and LottaNZB logs (when running LottaNZB from command line), but I guess this won't help much."
Quote: "Also, i've noticed that when i change hellanzb maxrate after startup, that the console starts updating at odd intervals making the transfer rate display show 0 even more often even though data is flowing in." Hmm. I need to try this out. Perhaps this would be an explanation.
thanks for the detailed list of steps to reproduce the problem. I also encounter this bug when playing with the download speed limit and unfortunately, this is something we simply cannot fix, because it's actually HellaNZB's fault. LottaNZB just displays the download speed reported by HellaNZB.
After the release of 0.5, we're going to evaluate the migration to SABnzbd. Nothing has been decided yet, but compared to HellaNZB, this software is actively being developed, has a much better API and developers that would be eager to help us.
+1 for the migration. HellaNZB has been full of problems for a long time now. The fact that development is not active would suggest that these things probably wont get fixed. I've never used SABnzbd but it has to be better than HellaNZB as it is at the moment!
Well, I guess it doesn't make much sense to leave this bug report open as we cannot fix it and it will most probably not be fixed in HellaNZB either. Thanks everyone for your help, though.
i've seen this too, but this may just be a reflection of hellanzb operates under rate limiting and not a bug in lottanzb
Please see attached video - my settings rate limit hellanzb to 450 (about half the 8-20 megabit rate on my net connection). You will see it will burst to >2000, the sit at zero until the rate limiting is complete - both the hellanzb console and lottanzb are visible in the capture.
Also, i've noticed that when i change hellanzb maxrate after startup, that the console starts updating at odd intervals making the transfer rate display show 0 even more often even though data is flowing in.