LHC@home

I got a work unit on the computer named desktopII.

The WU is reported as Task ID 18592738, WU ID 3825590.
The WU ended in error; but the reports have a discrepancy and are confusing. Outcome=Client error, Client State= Compute error, CPU time 14.24sec.

stderr out reads

<core_client_version>6.10.43</core_client_version>
<![CDATA[
<message>
Maximum elapsed time exceeded
</message>
]]>

Now, how can 14.24 seconds exceed a maximum elapsed time? I have a WU right now on a different machine, laptopII, which is almost completed with a total time of over 23 hours.

What is 14.24 seconds?

How to explain this discrepancy?

---

Please check out my blog
http://sciencesprings.wordpress.com
http://facebook.com/sciencesprings

The same ``song``
17/08/2010 18:19:29 lhcathome Aborting task wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__44_46__6__21_1_sixvf_boinc722_0: exceeded CPU time limit 1723.796707
Very confused. :-(

---

The same situation on all hosts. All tasks for SixTrack ending with limited CPU time error.
Dear project team!
What are You doing? Looking for supercomputers? ;o)

---

WOW!
I got work for SixTrackBNL.
And it looks like - this application contains the same screen saver bug. :-(

---

WOW!
I got work for SixTrackBNL.
And it looks like - this application contains the same screen saver bug. :-(

I also have one of the NBL workunits, to be specific:
SixTrackBNL 4209.00

I wonder what they are?

---

Warped

Same here:

17/08/2010 19:18:56 lhcathome Aborting task wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__76_78__6__78_1_sixvf_boinc1704_3: exceeded elapsed time limit 1352.531625
17/08/2010 19:18:56 lhcathome Aborting task wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__48_50__6__6_1_sixvf_boinc830_4: exceeded elapsed time limit 1352.531625

Seems like they don't have much trust in the stability of their WUs.

But there is also this error:
17/08/2010 19:19:01 lhcathome [error] Error reported by file upload server: nbytes missing or negative
17/08/2010 19:19:01 lhcathome Giving up on upload of wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__48_50__6__6_1_sixvf_boinc830_4_0: permanent upload error

---

WU ID 3962978 for all six computers:

<![CDATA[
<message>
Maximum CPU time exceeded
</message>
]]>

Even i7 CPU 920 @ 2.67GHz could not complete....

---

I have several these waiting to crunch on a couple of my machines as well. All have been returned by my wingmen with the same error and continue to be re-issued, probably until the max error count of 10 is reached. Looks like it\'s a totally chowdered batch of work units.

That ::thud:: you hear is my daily WU quota dropping like a stone... :-)


-- Tony D.

...All have been returned by my wingmen with the same error and continue to be re-issued, probably until the max error count of 10 is reached.

Confirmed! :-)

18/08/2010 08:18:27 lhcathome Starting wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__84_86__6__87_1_sixvf_boinc1946_7
18/08/2010 08:18:27 lhcathome Starting task wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__84_86__6__87_1_sixvf_boinc1946_7 using sixtrack version 420900
18/08/2010 08:35:37 lhcathome Aborting task wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__84_86__6__87_1_sixvf_boinc1946_7: exceeded elapsed time limit 1029.291298
18/08/2010 08:35:38 lhcathome Computation for task wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__84_86__6__87_1_sixvf_boinc1946_7 finished
18/08/2010 08:35:40 lhcathome Started upload of wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__84_86__6__87_1_sixvf_boinc1946_7_0
18/08/2010 08:35:41 lhcathome [error] Error reported by file upload server: nbytes missing or negative
18/08/2010 08:35:41 lhcathome Giving up on upload of wbnlaug10_DA-scaling-law1__1__s__64.31_59.32__84_86__6__87_1_sixvf_boinc1946_7_0: permanent upload error
18/08/2010 08:36:37 lhcathome Sending scheduler request: To fetch work.
18/08/2010 08:36:37 lhcathome Reporting 1 completed tasks, requesting new tasks for CPU
18/08/2010 08:36:42 lhcathome Scheduler request completed: got 0 new tasks

And I went to the trouble of cancelling another project WU and disabling receiving new works for others projects so that lhc@home would get optimal time T_T

I just saw the tasks I got on 27 Aug 2010 and today ended successfully.
Right now parts of the project are not running,but it look like a fix is being applied and work units are getting ready again,good news ^_^.