Any progress on solving the issue I'm seeing on multiple machines?

No, not yet, but it's on the list.

Matt

Jozef,

Are you saying that the estimates for the CPU application are somehow interfering with the estimates for the other applications? If so, I would be inclined to chalk that up as a client bug, because it doesn't make any sense for there to be coupling between applications.

Matt

GPUGrid Admins:

Regarding estimates:

GPUGrid uses "Duration Correction Factor", which I believe makes client-side estimation corrections globally for the entire project. It is not a "per-application" concept.

World Community Grid stopped using it, I believe when they introduced GPU tasks, because the estimates varied so much.

If you do not intend on creating very close estimated/approximations for certain application types, then you might need to turn off the global project "Use Duration Correction Factor" switch, which I believe is at your control. Richard H. knows more about this than I do.

"Duration Correction Factor"

Oh yes, I remember how much fun we had with that last year.

Matt

It is not only the "Duration Correction Factor" that applies for the entire project, but also the miscalculated (on the part of the WU implementors) total processing work required for these WUs. The abrupt jump from ~5% to 100% is proof of the miscalculation.

I believe that it is this "jump" that drives BOINC's estimations berserk.

---

It is not only the "Duration Correction Factor" that applies for the entire project, but also the miscalculated (on the part of the WU implementors) total processing work required for these WUs. The abrupt jump from ~5% to 100% is proof of the miscalculation.

I believe that it is this "jump" that drives BOINC's estimations berserk.

Well, it's the global DCF which does the real damage to other applications within the project, and DCF is only adjusted on the basis of the total elapsed time for the task, and only on task completion at that.

But I agree, the erratic jumps in progress %age would make it even harder to get an accurate <rsc_fpops_est> value for the tasks, and that's the fundamental driver for all these estimate problems.

We are already using the 'APR' runtime estimation component of CreditNew here, so in theory the estimates should be normalised towards DCF=1.0000 by the server: but that's a very slow process, and DCF - which is a much faster-response mechanism - has already started fighting against it. We could disable DCF, as Jacob suggests, but that could apply a sudden shock to the system if applied while DCF is skewed. I'd suggest asking the few people who are running both CPU and NV to bear with the problems for a short time while the runtime estimates are fixed at source (not least, because that way we can watch and confirm that the solution has worked properly when finished). Then, set <dont_use_dcf>, to prevent it escaping again.

It's been another week, and this infuriating bug is still continually wasting tons of CPU time on the 2 laptops that I previously mentioned. Is there anything I can do to help or expedite the solution? I was really excited that they might get their first ever GPUGrid units processed, but so far, I've only been met with disappointment.

Any progress on solving the issue I'm seeing on multiple machines?

No, not yet, but it's on the list.

Matt

I doubt the Event Log will say much, but I'll try to monitor it sometime.
From what I can see, this is an application error that GPUGrid (MJH) needs to fix.
Each "attempt" is a waste of 10 CPU seconds, and you can see below just how many times each task is attempted before failure.

It is literally wasting several minutes of CPU, for each task, only to fail.

MJH: I hope you can solve this one, please!

Looking at the timestamps below, I see:
01:22:53
...
01:38:25

That's 16 minutes of wasted CPU, and the log file wasn't even captured entirely, as the introduction was truncated. So.... we're looking at 20+ minutes of wasted CPU per task.

Please fix!

Stderr output

<core_client_version>7.2.42</core_client_version>
<![CDATA[
<message>
too many exit(0)s
</message>
<stderr_txt>
7236): BOINC client no longer exists - exiting
01:22:53 (7236): timer handler: client dead, exiting
# (BOINC) Mapping [ligand.tar]->[ligand.tar] 
# (BOINC) Mapping [results.tar]->[../../projects/www.gpugrid.net/2784-DOCK_LAB_MJHARVEY_18211_3HHM2_ZINC9-0-1-RND7172_0_0] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt] 
nextfile: reading [in]
[.]
[..]
[ligand-9243.pdbqt]
NEXTFILE : [out] [ligand-9243.pdbqt] 
copy [in/ligand-9243.pdbqt]->[ligand.pdbqt]
# (BOINC) Mapping [input.dat]->[input.dat] 
# (BOINC) Mapping [progress.log]->[progress.log] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [ligand.pdbqt]->[ligand.pdbqt] 
01:23:03 (216): BOINC client no longer exists - exiting
01:23:03 (216): timer handler: client dead, exiting
# (BOINC) Mapping [ligand.tar]->[ligand.tar] 
# (BOINC) Mapping [results.tar]->[../../projects/www.gpugrid.net/2784-DOCK_LAB_MJHARVEY_18211_3HHM2_ZINC9-0-1-RND7172_0_0] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt] 
nextfile: reading [in]
[.]
[..]
[ligand-9243.pdbqt]
NEXTFILE : [out] [ligand-9243.pdbqt] 
copy [in/ligand-9243.pdbqt]->[ligand.pdbqt]
# (BOINC) Mapping [input.dat]->[input.dat] 
# (BOINC) Mapping [progress.log]->[progress.log] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [ligand.pdbqt]->[ligand.pdbqt] 
01:23:14 (7032): BOINC client no longer exists - exiting
01:23:14 (7032): timer handler: client dead, exiting
# (BOINC) Mapping [ligand.tar]->[ligand.tar] 
# (BOINC) Mapping [results.tar]->[../../projects/www.gpugrid.net/2784-DOCK_LAB_MJHARVEY_18211_3HHM2_ZINC9-0-1-RND7172_0_0] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt] 
nextfile: reading [in]
[.]
[..]
[ligand-9243.pdbqt]
NEXTFILE : [out] [ligand-9243.pdbqt] 
copy [in/ligand-9243.pdbqt]->[ligand.pdbqt]
# (BOINC) Mapping [input.dat]->[input.dat] 
# (BOINC) Mapping [progress.log]->[progress.log] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [ligand.pdbqt]->[ligand.pdbqt] 
01:23:25 (7480): BOINC client no longer exists - exiting
01:23:25 (7480): timer handler: client dead, exiting
# (BOINC) Mapping [ligand.tar]->[ligand.tar] 
# (BOINC) Mapping [results.tar]->[../../projects/www.gpugrid.net/2784-DOCK_LAB_MJHARVEY_18211_3HHM2_ZINC9-0-1-RND7172_0_0] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt] 
nextfile: reading [in]
[.]
[..]


.....

[.]
[..]
[ligand-9243.pdbqt]
NEXTFILE : [out] [ligand-9243.pdbqt] 
copy [in/ligand-9243.pdbqt]->[ligand.pdbqt]
# (BOINC) Mapping [input.dat]->[input.dat] 
# (BOINC) Mapping [progress.log]->[progress.log] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [ligand.pdbqt]->[ligand.pdbqt] 
01:38:15 (6340): BOINC client no longer exists - exiting
01:38:15 (6340): timer handler: client dead, exiting
# (BOINC) Mapping [ligand.tar]->[ligand.tar] 
# (BOINC) Mapping [results.tar]->[../../projects/www.gpugrid.net/2784-DOCK_LAB_MJHARVEY_18211_3HHM2_ZINC9-0-1-RND7172_0_0] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [flexible.pdbqt]->[flexible.pdbqt] 
nextfile: reading [in]
[.]
[..]
[ligand-9243.pdbqt]
NEXTFILE : [out] [ligand-9243.pdbqt] 
copy [in/ligand-9243.pdbqt]->[ligand.pdbqt]
# (BOINC) Mapping [input.dat]->[input.dat] 
# (BOINC) Mapping [progress.log]->[progress.log] 
# (BOINC) Mapping [protein.pdbqt]->[protein.pdbqt] 
# (BOINC) Mapping [ligand.pdbqt]->[ligand.pdbqt] 
01:38:25 (7780): BOINC client no longer exists - exiting
01:38:25 (7780): timer handler: client dead, exiting

</stderr_txt>
]]>

Can you please have a look at this host's tasks (my wife's laptop) -- the tasks seem to be erroring out.
http://www.gpugrid.net/results.php?hostid=85944

Exit status -226 (0xffffffffffffff1e) ERR_TOO_MANY_EXITS

... near step:
# (BOINC) Mapping [ligand.pdbqt]->[ligand.pdbqt]
17:11:39 (1732): BOINC client no longer exists - exiting
17:11:39 (1732): timer handler: client dead, exiting

MJH:
All of the GPUGrid CPU tasks are erroring out, on these 2 hosts I manage:
http://www.gpugrid.net/results.php?hostid=137361
http://www.gpugrid.net/results.php?hostid=85944
... Do you have any idea what is happening with the repeated exits near the step mentioned above?
I'll try unattaching and reattaching the project, but... it'd be nice if you might mention if you know what might be causing this problem on 2 separate machines. Edit: Project unattach/reattach and resets.. did not help.

Please help!

I'm super excited about the possibility about having these non-GPU computers do work for your project, for the first time ever, but...

They need your help!

It's been another week, and this infuriating bug is still continually wasting tons of CPU time on the 2 laptops that I previously mentioned. Is there anything I can do to help or expedite the solution? I was really excited that they might get their first ever GPUGrid units processed, but so far, I've only been met with disappointment.

Jacob,

What's the problem here? The only laptop visible on your account - host 167515 - completed and validated a load of CPU tasks as recently as yesterday. The only errors visible date back to 27 March.

Agreed, the two hosts 137361, 85944 on the KSMooney account are still throwing errors, but according to the message log you posted, the problem on both those machines is

BOINC client no longer exists - exiting
timer handler: client dead, exiting

It would seem to me that the first step in curing this needs to happen at your end: why does the client fail to run continously? What messages, if any, can you retrieve from the Event Log or stdoutdae.txt? Do the machines run tasks from other projects without BOINC dying?

Only if you can establish a causal link (and better yet, suggest a plausible mechanism) by which the GPUGrid CPU app is *responsible* for the failure of the client does it become the responsibility of the project to fix something. But I can't imagine what that 'something' could be: the app works for you, as it worked for me.

Sigh.

All other projects work fine on those 2 laptops (KSMooney is my wife, and those 2 laptops are hers, and I manage them). The stderr is, as you saw. Namely: On those 2 machines, they get stuck in some sort of loop that wastes at least 20 minutes of CPU time per failed GPUGrid task. I believe the problem is something in the app, making it restart continuously. "Why does the client fail to run continously?" is a bit troubling... because the client itself is not crashing/failing, from what I can tell. I'd love to say "the problem is on my end", or even to say "I have more info that further identifies the problem", but I can't. All I have is the stderr.txt you see.

It might be helpful if the admins looked to see if any other hosts were having similar problems. I wish I know how I could do that.

Does this help? (shows I was freshly-attached, where the job repeatedly started until eventually giving up after wasting 20 minutes of CPU)

A quick scan for the text "exited with zero status but no 'finished' file" ... shows that it "failed" exactly 100 times. So, maybe knowing that loop-limit somehow narrows down the problem?

08-Apr-2014 18:43:41 [---] Attaching to http://www.gpugrid.net/
08-Apr-2014 18:43:43 [http://www.gpugrid.net/] Master file download succeeded
08-Apr-2014 18:43:49 [http://www.gpugrid.net/] Sending scheduler request: Project initialization.
08-Apr-2014 18:43:49 [http://www.gpugrid.net/] Requesting new tasks for CPU
08-Apr-2014 18:43:52 [---] [unparsed_xml] FILE_REF::parse(): unrecognized: 'rboinc/'
08-Apr-2014 18:43:52 [---] [unparsed_xml] FILE_REF::parse(): unrecognized: 'rboinc/'
08-Apr-2014 18:43:52 [---] [unparsed_xml] FILE_REF::parse(): unrecognized: 'rboinc/'
08-Apr-2014 18:43:52 [---] [unparsed_xml] FILE_INFO::parse(): unrecognized: rboinc/
08-Apr-2014 18:43:52 [---] [unparsed_xml] FILE_INFO::parse(): unrecognized: rboinc/
08-Apr-2014 18:43:52 [GPUGRID] Scheduler request completed: got 1 new tasks
08-Apr-2014 18:43:54 [GPUGRID] Started download of gpugrid-vina-windows_intelx86.105
08-Apr-2014 18:43:54 [GPUGRID] Started download of 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-input
08-Apr-2014 18:43:54 [GPUGRID] Started download of 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-receptor
08-Apr-2014 18:43:54 [GPUGRID] Started download of 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-ligand
08-Apr-2014 18:43:58 [GPUGRID] Finished download of 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-input
08-Apr-2014 18:43:58 [GPUGRID] Started download of logogpugrid.png
08-Apr-2014 18:43:59 [GPUGRID] Finished download of logogpugrid.png
08-Apr-2014 18:43:59 [GPUGRID] Started download of project_1.png
08-Apr-2014 18:44:01 [GPUGRID] Finished download of 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-ligand
08-Apr-2014 18:44:01 [GPUGRID] Started download of project_2.png
08-Apr-2014 18:44:02 [GPUGRID] Finished download of project_1.png
08-Apr-2014 18:44:02 [GPUGRID] Started download of project_3.png
08-Apr-2014 18:44:03 [GPUGRID] Finished download of project_2.png
08-Apr-2014 18:44:04 [GPUGRID] Finished download of project_3.png
08-Apr-2014 18:44:07 [GPUGRID] Finished download of gpugrid-vina-windows_intelx86.105
08-Apr-2014 18:44:07 [GPUGRID] Finished download of 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-receptor
08-Apr-2014 18:44:07 [GPUGRID] Starting task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0
08-Apr-2014 18:44:19 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:44:19 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:44:32 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:44:32 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:44:44 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:44:44 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:44:55 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:44:55 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:45:06 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:45:06 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:45:18 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:45:18 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:45:30 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:45:30 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:45:41 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:45:41 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:45:53 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:45:53 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:46:05 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:46:05 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:46:17 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:46:17 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:46:24 [---] Suspending network activity - time of day
08-Apr-2014 18:46:28 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:46:28 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:46:39 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:46:39 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:46:51 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:46:51 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:47:02 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:47:02 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:47:13 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:47:13 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:47:24 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:47:24 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:47:35 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:47:35 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:47:48 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:47:48 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:47:59 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:47:59 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:48:11 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:48:11 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:48:23 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:48:23 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:48:36 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:48:36 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:48:48 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:48:48 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:48:59 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:48:59 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:49:12 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:49:12 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:49:24 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:49:24 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:49:36 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:49:36 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:49:47 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:49:47 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:50:00 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:50:00 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:50:12 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:50:12 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:50:24 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:50:24 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:50:35 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:50:35 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:50:48 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:50:48 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:51:01 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:51:01 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:51:15 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:51:15 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:51:29 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:51:29 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:51:43 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:51:43 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:51:55 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:51:55 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:52:07 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:52:07 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:52:22 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:52:22 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:52:34 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:52:34 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:52:45 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:52:45 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:52:58 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:52:58 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:53:10 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:53:10 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:53:22 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:53:22 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:53:37 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:53:37 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:53:52 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:53:52 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:54:04 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:54:04 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:54:15 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:54:15 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:54:27 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:54:27 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:54:38 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:54:38 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:54:49 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:54:49 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:55:00 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:55:00 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:55:12 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:55:12 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:55:23 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:55:23 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:55:34 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:55:34 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:55:46 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:55:46 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:55:57 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:55:57 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:56:09 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:56:09 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:56:20 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:56:20 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:56:31 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:56:31 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:56:43 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:56:43 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:56:54 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:56:54 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:57:05 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:57:05 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:57:16 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:57:16 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:57:28 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:57:28 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:57:39 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:57:39 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:57:50 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:57:50 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:58:01 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:58:01 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:58:13 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:58:13 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:58:24 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:58:24 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:58:35 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:58:35 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:58:47 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:58:47 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:58:58 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:58:58 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:59:09 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:59:09 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:59:20 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:59:20 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:59:31 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:59:31 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:59:42 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:59:42 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 18:59:54 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 18:59:54 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:00:06 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:00:06 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:00:17 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:00:17 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:00:29 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:00:29 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:00:40 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:00:40 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:00:52 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:00:52 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:01:03 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:01:03 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:01:14 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:01:14 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:01:25 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:01:25 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:01:37 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:01:37 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:01:48 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:01:48 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:01:59 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:01:59 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:02:10 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:02:10 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:02:21 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:02:21 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:02:33 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:02:33 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:02:44 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:02:44 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:02:56 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:02:56 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:03:08 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:03:08 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:03:22 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:03:22 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:03:37 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:03:37 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:03:52 [GPUGRID] Task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 exited with zero status but no 'finished' file
08-Apr-2014 19:03:52 [GPUGRID] If this happens repeatedly you may need to reset the project.
08-Apr-2014 19:04:07 [GPUGRID] Computation for task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 finished
08-Apr-2014 19:04:07 [GPUGRID] Output file 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0_0 for task 4900-DOCK_LAB_MJHARVEY_18206_3HHM2_ZINC4-0-1-RND3680_0 absent

Both of those machines are service-installs. I'm starting to think that "being a service install" might be relevant to the problem.

Didn't we recently have some sort of "service-install heartbeat bug" in the BOINC API - is it possible this new CPU App is using a bugged version of the API?

I seriously feel like I recall a recently-identified-(by-me)-and-fixed-(by-ROM) BOINC API Bug that caused service-installs to not work at all, for apps that were compiled against the bugged API. I think Rom even sent out an email to the projects. GPUGrid Admins: Is it possible that the CPU app was compiled against the bugged API?

Both of those machines are service-installs. I'm starting to think that "being a service install" might be relevant to the problem.

Didn't we recently have some sort of "service-install heartbeat bug" in the BOINC API - is it possible this new CPU App is using a bugged version of the API?

Here's the email (it pretty much describes, exactly, the behavior I am seeing on these 2 service-install laptops)

> Date: Wed, 6 Nov 2013 10:40:17 -0500
> From: r****@rom****.org
> To: boinc_proj****@ssl.berkeley.edu
> Subject: [boinc_projects] BOINC API Change
>
> Yesterday we discovered a problem with the BOINC API where it would
> shutdown applications after 10 seconds on Windows when the BOINC client
> was installed as a service.
>
>
>
> The bug will affect all applications built with since July of this year.
> If you have built your application between July and now with a recent
> BOINC API you should probably deploy a new version of the application.
>
>
>
> The commit that fixed the issue is:
> 3aaeadaf99669c6460a183e7e9f2063f39152031
>
>
>
> Thanks in advance.
>
>
>
> ----- Rom

So... Looking at the email pasted above....

Are we using a bugged BOINC API? And, if so, was it aliens? And, if not, can we fix it yet please?

I seriously feel like I recall a recently-identified-(by-me)-and-fixed-(by-ROM) BOINC API Bug that caused service-installs to not work at all, for apps that were compiled against the bugged API. I think Rom even sent out an email to the projects. GPUGrid Admins: Is it possible that the CPU app was compiled against the bugged API?

Both of those machines are service-installs. I'm starting to think that "being a service install" might be relevant to the problem.

Didn't we recently have some sort of "service-install heartbeat bug" in the BOINC API - is it possible this new CPU App is using a bugged version of the API?

Ah-ha. Now we're cooking. You're absolutely right.

Rom Walton to BOINC Projects, 6 November 2013, subject line "BOINC API Change":

Yesterday we discovered a problem with the BOINC API where it would
shutdown applications after 10 seconds on Windows when the BOINC client
was installed as a service.

The bug will affect all applications built with since July of this year.
If you have built your application between July and now with a recent
BOINC API you should probably deploy a new version of the application.

The commit that fixed the issue is:
3aaeadaf99669c6460a183e7e9f2063f39152031

Thanks in advance.

----- Rom

http://lists.ssl.berkeley.edu/mailman/private/boinc_projects/2013-November/010493.html

That should give Matt enough info to track it down ;)

Looks plausible, Jacob. I think my fork of the client code dates from that window. I'll check and see. But, this is the same library as I have in the GPU application, and that's not affected, is it?

Matt

It likely is affected (in the sense that a service-install Windows PC would suffer the heartbeat problem running the GPU app that was compiled against bad BOINC API), but not highly noticeable (since Windows GPU apps cannot run on service installs on OS's newer than Windows XP I think).

So, your GPU app is affected, but only on Windows XP or prior... maybe.

I look forward to you fixing this. These poor laptops are REALLY WANTING to do GPUGrid work :) :)

Looks plausible, Jacob. I think my fork of the client code dates from that window. I'll check and see. But, this is the same library as I have in the GPU application, and that's not affected, is it?

Matt

I am running the GPU apps on two machines with service installs (Windows XP, BOINC client 6.12.34, which is the last combination for which this is allowed)

Host 43404 - as yet cuda55 max, I haven't updated the driver recently
Host 45218 - recently upgraded to GTX 750Ti, so getting cuda60 only.

Both machines are running from the 'short task' queue only. The bug doesn't bite.

I'm not positive, but I believe it's possible the the bug possibly also only affects newer clients.

Matt, any chance we could compile against newer non-bugged BOINC API, to see if it fixes the problem, please?

PS: I'm sorry I didn't figure this out earlier, while the app was still in Testing. I just want it fixed :/

PS: I got confirmation from Rom that it's possible XP might not be susceptible to the "service-install BOINC API heartbeat bug", since it might return different error codes for OpenProcess() and have different default process ACLs than newer operating systems.

All of my machines (and my wife's 2 service-install laptops) are running Windows 8.1 Update 1.

Long story short:
I'm still quite confident that compiling against a newer non-bugged BOINC API, will fix the issue. Hope you guys can do it soon - Rom said it was a relatively easy thing to fix.

Thanks in advance,
Jacob

Jacob - app updated.

Matt