My 4-core machine has 11 uploads waiting, so that one can't download any more work. It's not urgent yet, though, there's about a 2 day cache left on it (I increased it just before hitting the limit).

as JSYKES mentioned, I have had 4 WU that continued to reset; they spun for over 24 hours and never got past 10 or 12 percent. I ended up aborting them. Plus one on the same laptop that won't upload and 3 others that I also aborted without letting them even start.

I'm all in on beta's but not this one.

It's really hard to understand how an institution like Harvard could let something like this happen.

Impressive back-off times......they've been hanging around a very long time.....

10/10/2016 19:22:11 | World Community Grid | Backing off 05:38:04 on upload of BETA_E299901_353_S.312.C32H18N10O4.KYRNVLFOJVVBBF-UHFFFAOYNA-N.7_s1_14_2_r1882252927_4 
10/10/2016 21:51:15 | World Community Grid | Backing off 04:55:00 on upload of BETA_E299901_404_S.314.C35H23N7O4.JCAIIGAKNAAJDN-UHFFFAOYNA-N.8_s1_14_2_r972877995_4 
10/10/2016 22:38:33 | World Community Grid | Backing off 05:10:00 on upload of BETA_E299901_473_S.314.C26H16N2S8.CFZDJMCZNYNUQJ-UHFFFAOYNA-N.2_s1_14_2_r519331991_4 
11/10/2016 01:00:18 | World Community Grid | Backing off 03:29:04 on upload of BETA_E299901_353_S.312.C32H18N10O4.KYRNVLFOJVVBBF-UHFFFAOYNA-N.7_s1_14_2_r1882252927_4

Funnily enough, all my unuploadable results are _2 reissues and the original copy in each case failed the same way:

<core_client_version>7.6.22</core_client_version> <![CDATA[ <message> app_version download error: couldn't get input files: <file_xfer_error> <file_name>wcgrid_cep2_qchem_prod_linux.x86_7.04_windows_intelx86</file_name> <error_code>-120 (RSA key check failed for file)</error_code> </file_xfer_error> </message> ]]>

Ironic that those who failed to start the WUs are arguably in better shape than those who did all the crunching now cannot upload....

@Uplinger - re. your comment on being on weekend standby via your phone: true dedication to the cause - appreciated!

I got 1 resend as a result of the 1st 2 wingmen being awarded "No reply". Should I abort it or let it run? Have suspended it 10h in, pending further developments at WCG or Harvard.
What should those of us who've received such resends do? Crunching them counts towards upgrading badges (whoopee!) but won't advance the science, so our CPU time would be better spent doing other work.

Updates to my earlier post re the machine running from the USB2 stick:
I do not have CEP2 selected to run on it, and would not normally do so with a USB stick.
It has now successfully run 2 of these betas 1 at a time to their 18h cutoff, and is 10h into a 3rd.
I will replace the USB drive with a 2.5" x 1TB HDD when I get time to install software on it.

@tonyh205 - re using app_config
I know about the app_config facility but haven't set it up on most machines because I haven't crunched CEP2 for quite a while. (App_config is documented near the bottom of the page at https://boinc.berkeley.edu/wiki/Client_configuration
)
How do you find the "short names" of all WCG sciences, and especially the name of the next betas, in advance?
Fishing them out of client_state.xml looks tricky since there are zillions of <name> entries in there, while the alternative of setting <sched_op_debug> is only going to work after the first beta has started.

PS/OT/@Sekerob, who can report stuff to the BOINC wiki authors:
The last line of the cc_config wiki says:
"If you remove app_config.xml, or one of its entries, you must reset the project in order to restore the proper values."
Should that read "restart your BOINC client", not "reset the project"? [/OT]