On Fri, 10 Jul 2009 10:44:33 -0700, you wrote: >I just checked in the change you describe. >Actually it was added 4 years ago, >but was backed out because there were reports that it wasn't working right. > >This time I added some <file_xfer_debug>-enabled messages, >so we should be able to track down any problems. >
Now v6.6.38 is available, did a couple quick tests by disabling network, waiting some hours till some uploads was present, blocked BOINC's ability to connect, and enabled network. The result: 1: After tried 3 different uploads and all failing with 60-second backoff, got a "project-wide xfer delay". 2: After any later backoffs, the same upload was always tried, giving a new "project-wide xfer delay". Also tried downloads for a different project, and these was running on an independent project-wide backoff from the failing uploads in the other project. So, based on the debug-messages, the code seems to work as it should... But, for the "Normal users" on the other hand, the code does not work, because there's no indication (except for the debug-messages very few users will have enabled), why transfers isn't happening. The Transfer-tab only displays "Upload pending" or "Download pending", so users will see one or more pending transfers, with no active, and no counting-down to be re-tried later. A look on Message-tab will show example: 22.07.2009 14:21:08 World Community Grid Temporarily failed upload of dddt1602o0804_100296_0_0: connect() failed 22.07.2009 14:21:08 World Community Grid Backing off 3 min 19 sec on upload of dddt1602o0804_100296_0_0 Anyone looking on either Transfer-tab or Message-tab around 14:30:00 won't see any backoffs, and will see BOINC-client hasn't tried again, as it is indicating it should have been doing some minutes ago. So, for the "Normal users", the client is very clearly fatally broken, and they'll either starts complaining on the message-boards, just downgrade to an older client, or just ditch the broken BOINC-client since it clearly isn't working. Now, with debug-message turned-on the log is: 22.07.2009 14:21:08 World Community Grid Temporarily failed upload of dddt1602o0804_100296_0_0: connect() failed 22.07.2009 14:21:08 World Community Grid [file_xfer_debug] project-wide xfer delay for 1764.330447 sec 22.07.2009 14:21:08 World Community Grid Backing off 3 min 19 sec on upload of dddt1602o0804_100296_0_0 This does show why nothing is happening, but for the wast majority of BOINC-users, it's unlikely they'll run with debugging turned-on, so for these users the BOINC-client isn't working. It was the same problem 4 years ago, there was no indication on the Transfer-tab why nothing was progressing as it should. The debug-message is a nice addition, since it shows the code is working, but only debug-message is not enough in this instance, since most users won't run with debugging turned-on. And, it shouldn't be neccessary for "normal users" to run with debugging turned-on... -- "I make so many mistakes. But then just think of all the mistakes I don't make, although I might." _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
