From time to time eweka.nl does not respond, and when that happen, sabnzbd have a really hard time to fall back to the backup server, it seem to have the need to test every post anyways, waiting for the timeout to happen, this takes a looooong time to complete. sabnzbd should be able to detect such server problem and disable the server for let's say 1 hours or maybe 30 minutes, and why not let the user decide how much time to wait after a timeout. We could say after 8 timeout in 1 hour we stop using that server for 30 minutes and then we try again, if we still have something to download. While at it it would be great to receive an email of that fact, if a free server goes offline we would receive many emails from that server knowing that it might have been taken offline somehow, that allow the user to disable that server.
I have 5 active servers that I use, my ISP server that give me about 95% completion over 2 days and then posts start to be lost after that at a rate unknown... I have the famous news.ipv6.eweka.nl and newszilla6.xs4all.nl I also have the free.teranews.com (setup fee are required and only 50 MB / days, but it works great as a backup server) and finally I have a block account with news.astraweb.com
If I could prioritize my servers that would go like
1=ISP,
2=eweka and newszilla,
3=teranews,
4=astraweb
If I could setup a maximum transfer amount per server that would go like
- ISP, eweka, newszilla=unlimited
- teranews=50MB/day
- astraweb=130GB/forever
I understand that sabnzbd have no control over other clients that could use credit, but hey... Who here use anything else than sabnzbd... ;-) The maximum transfer would be great to avoid connecting to the server for nothing when limit is reach, speeding things a little bit.
MageMinds
Handle Non Responsive Server
Re: Handle Non Responsive Server
There will be some solution for unreliable servers in 0.5.0
(a penalty lockout when they don't behave nice).
We're not very keen on overloading the server configuration with even more parameters.
That's what your requests would require.
So far we don't even have per server byte counting, so we would have to do that first.
Your request is interesting, but will not have a high priority with the team.
(a penalty lockout when they don't behave nice).
We're not very keen on overloading the server configuration with even more parameters.
That's what your requests would require.
So far we don't even have per server byte counting, so we would have to do that first.
Your request is interesting, but will not have a high priority with the team.
Re: Handle Non Responsive Server
Not a high priority is fine by me ... Your software is still the most important piece of software that is running at home ... I even have a Watchdog setup to make sure it's being started back when it crashes ... Yes it crashes from time to time, but I can't find anything in logfile so I can't file a bug report... It might be my computer too, I don't know, all I know is sometimes the process is not there and believe me, I'm not the one that close it...
I found "Watchdog - O - Matic" like 2 or 3 days ago and since then SABnzbd didn't crash, so I don't know if it's working, I hope to be able to test it before the Trial end.
MageMinds
I found "Watchdog - O - Matic" like 2 or 3 days ago and since then SABnzbd didn't crash, so I don't know if it's working, I hope to be able to test it before the Trial end.
MageMinds
Re: Handle Non Responsive Server
More people complain about this, so far we haven't been able to reproduce it.MageMinds wrote: Yes it crashes from time to time, but I can't find anything in logfile so I can't file a bug report...
Which doesn't mean that the problem does not exist.
Which OS do you use?