r0.6.15: "nzb fetch" errors and does not email Errors
Posted: February 24th, 2012, 1:31 pm
Hello:
I'm loving the new features of 0.6, especially around email. Thank you! Though, I would like the emails to be much more detailed about the patching and such, if that is available.
This bug report is around the "Errors". The only error I've had since upgrading a few weeks ago is I seem to have a lot of "nzb fetch" timeouts. I saw maybe 1 or 2 timeouts before the upgrade, for well over a year of use of sabnzbd. But this version 0.6.15 that I upgraded to seems to have 2 or 3 nzb fetch errors per week now.
Not so bad, I just click Try again and it works.
But that brings me to my 2nd part of the bug report: no email is sent when the "nzb fetch" fails. Since my system is pretty much hands off (using Sick Beard and NZB MAtrix Favorites, with a lot of cmd-line scripting I've written), I am not notified when these fetch fails.
Only when the family asks, "Daddy, there is no X show today. Is the server ok?" Sure enough, I'll login and 2 or 3 NZB Fetch failures are sitting there waiting.
Yes, I have "Email Notification On Job Completion" set to "Always". But the fetching errors is not generating an email. Perhaps a separate "Email log errors?" option would be required?
An email of these errors would be nice, so I know when to go look.
But more to the point, why so many? I know the remote service is out of your control, but this happening far more often since the upgrade from 0.5.6 (my last version, I went straight to 0.6.15 following the upgrade guide without any issues). Perhaps there should be retry count built in? Possibly with increasing delays during each timeout, much like how SQL Server works on it's retries.
Thanks!
-E
I'm loving the new features of 0.6, especially around email. Thank you! Though, I would like the emails to be much more detailed about the patching and such, if that is available.
This bug report is around the "Errors". The only error I've had since upgrading a few weeks ago is I seem to have a lot of "nzb fetch" timeouts. I saw maybe 1 or 2 timeouts before the upgrade, for well over a year of use of sabnzbd. But this version 0.6.15 that I upgraded to seems to have 2 or 3 nzb fetch errors per week now.
Not so bad, I just click Try again and it works.
But that brings me to my 2nd part of the bug report: no email is sent when the "nzb fetch" fails. Since my system is pretty much hands off (using Sick Beard and NZB MAtrix Favorites, with a lot of cmd-line scripting I've written), I am not notified when these fetch fails.
Only when the family asks, "Daddy, there is no X show today. Is the server ok?" Sure enough, I'll login and 2 or 3 NZB Fetch failures are sitting there waiting.
Yes, I have "Email Notification On Job Completion" set to "Always". But the fetching errors is not generating an email. Perhaps a separate "Email log errors?" option would be required?
An email of these errors would be nice, so I know when to go look.
But more to the point, why so many? I know the remote service is out of your control, but this happening far more often since the upgrade from 0.5.6 (my last version, I went straight to 0.6.15 following the upgrade guide without any issues). Perhaps there should be retry count built in? Possibly with increasing delays during each timeout, much like how SQL Server works on it's retries.
Thanks!
-E