Sorry Guys
these are my time, my money and my costs
So i will stop Rosetta now

Have been unable to upload work units since yesterday (two have timed out). Keeps telling me "project backoff."

I'm on an iMac Pro 2017 running macOS 10.14 Mojave and BOINC 7.12

Do these Rosetta WU's Need to have a deadline that is very short?

Yes. R@h tasks have deadlines that reflect the needs of the project and the specific tasks. 3 days is the shortest deadline used by R@h at this point.

Dang it, I'm still getting the same error.

I tried to find the file app_control.cpp, but couldn't find it - is this a file I can edit?

Thanks!!

Franko

[snip]

Files with the .cpp extension are usually C++ source files, which can be edited. However, doing so is not useful unless:

The error message is displayed by the BOINC Client.
I think it is just a BOINC Client timing issue that they have declared "fixed" several times.
I don't think it is ever a problem, just annoying.

client/app_control.cpp

// Check for finish files every 10 sec.
// If we already found a finish file, abort the app;
// it must be hung somewhere in boinc_finish();
//
static double last_finish_check_time = 0;
if (gstate.clock_change || gstate.now - last_finish_check_time > 10) {
last_finish_check_time = gstate.now;
for (i=0; i<active_tasks.size(); i++) {
ACTIVE_TASK* atp = active_tasks[i];
if (atp->task_state() == PROCESS_UNINITIALIZED) continue;
if (atp->finish_file_time) {
// process is still there 10 sec after it wrote finish file.
// abort the job
atp->abort_task(EXIT_ABORTED_BY_CLIENT, "finish file present too long"); <<<<<<<<<<<< line 140
} else if (atp->finish_file_present()) {
atp->finish_file_time = gstate.now;
}
}
}

The error message is displayed by the BOINC Client.
I think it is just a BOINC Client timing issue that they have declared "fixed" several times.
I don't think it is ever a problem, just annoying.

client/app_control.cpp

// Check for finish files every 10 sec.
// If we already found a finish file, abort the app;
// it must be hung somewhere in boinc_finish();
//
static double last_finish_check_time = 0;
if (gstate.clock_change || gstate.now - last_finish_check_time > 10) {
last_finish_check_time = gstate.now;
for (i=0; i<active_tasks.size(); i++) {
ACTIVE_TASK* atp = active_tasks[i];
if (atp->task_state() == PROCESS_UNINITIALIZED) continue;
if (atp->finish_file_time) {
// process is still there 10 sec after it wrote finish file.
// abort the job
atp->abort_task(EXIT_ABORTED_BY_CLIENT, "finish file present too long"); <<<<<<<<<<<< line 140
} else if (atp->finish_file_present()) {
atp->finish_file_time = gstate.now;
}
}
}

I get the same error (and not only on Rosetta@home. I think my hard disk is too busy to output a 'finished file' on time for Boinc.

That is an interesting thought. I have not seen that error for a long time, and I now use only SSDs on all my machines.
Also, I usually use a write-cache (or ramdisk), so most of my writes and even reads are from main memory. I think that does it.

I received Avast (Windows) Virus Alerts on Both the Rosetta AND the SETI Results web sites:

I can't attach a screenshot, so here's a summary:

http://boinc.bakerlab.org/rosetta/results.php?userid=472655
http://setiathome.berkeley.edu/results.php?userid=521624

Infected with HTML:ChaseBank-A[Phish]

Thanks!!

Franko

me to (Avast)