0.5.0Beta4 - 'optional' servers broken

[SenorClean]

Hi Guys,

I have been running 0.5.0 Beta1 and have been enjoying the 'optional' server option.  However, in 0.5.0 Beta4 it doesn't work.

When I launch sab - it functions properly until my unreliable server times out - the time out warnings show up in the connections tab, and then downloads halt.  They make no progress, and the download speed becomes frozen where it is - which is the same behavior as if a bad server is added (but not flagged as optional).

EDIT: sorry - this should probably be in the beta section

[shypike]

I'll have a look at it.
But there were virtually no changes in this area.
I'll look for side-effects from other changes.

[shypike]

Do you combine it with more reliable servers?
Are these non-optional?

Do you just use one server? In that case it shouldn't be optional.

[EnnZeeBee]

I cannot confirm SenorClean's observation.

[SenorClean]

I'll do some experiments to verify... but my setup is two reliable servers and one non-reliable.

The two reliable ones are enabled.  The other is 'optional'  (but set to backup now).  When the unreliable one is flagged as optional in beta4 and it times out, all the servers stop.

I'll try downloading something else now and see how it goes....

Below is what I am seeing in my log.  Basically, it is failing to connect to the server, but not ignoring it like it used to for 'optional' servers.  The client seems to sometimes download a small section of the queue, but then when it tries the unreliable server again it stops moving.

If I return the unreliable server to a 'backup' - all is well again.  But I prefer the functionality of 'optional'.

2009-12-18 09:50:31,296 ERROR: Too many connections to server newszilla6.xs4all.nl:119
2009-12-20 09:15:45,484 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:15:45,562 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:15:45,671 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:15:45,780 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:15:45,859 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:18:36,766 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:19:27,921 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:19:36,703 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:20:49,046 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:20:49,171 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:22:10,236 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:22:19,079 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:23:31,405 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:23:40,344 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:24:52,671 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:25:01,328 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:26:13,844 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119
2009-12-20 09:26:22,609 ERROR: Failed to connect: (10060, "(10060, 'Operation timed out')") [email protected]:119

[shypike]

In your case the setup should be this:

Unreliable server : non-backup, optional
reliable server 1 : backup
reliable server 2 : backup

This way the unreliable server is always tried first and will block if not present.

Having two reliable servers as primary will work, but why would you
want to include an unreliable one too?
Having an unreliable server as backup will serve no purpose. It will simply
never be used (assuming the reliable ones are always present AND have all articles).

[SenorClean]

My unreliable one used to be fantastic - and I'm hoping it will be back online soon.

I'll try your settings and see how it goes.  It still seems odd to me though that it worked well in beta1 - it seems to me that 'optional' is still broken.