client errors - max time exceeded

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35825044
RAC: 0
Topic 197021

hi folks! been a while. ive got a couple "client errors" and trying to figure out why, (well i mean i know its because the run time was exceeded but, why?)

result id 386684060

and

result id 386669775

boinc version 7.0.64

im running avast a/v but ive got boinc\* in the exclusions and i dont see any notices in its log.

any ideas?

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

Bernd Machenschalk
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4332
Credit: 251724801
RAC: 35607

client errors - max time exceeded

Sorry, our fault. See this thread.

BM

BM

paul milton
paul milton
Joined: 16 Sep 05
Posts: 329
Credit: 35825044
RAC: 0

ah! whew, ironically thats a

ah! whew, ironically thats a relief :)

seeing without seeing is something the blind learn to do, and seeing beyond vision can be a gift.

Professor Ray
Professor Ray
Joined: 22 Feb 05
Posts: 46
Credit: 12593465
RAC: 3478

So I get no credit-dinged for

So I get no credit-dinged for 25+ hrs crunch time on WU w/ due date: 13 Jul 4?

6/26/2013 12:59:08 AM | Einstein@Home | Aborting task LATeah0028U_80.0_220_-9.52e-10_1: exceeded elapsed time limit 92062.11 (132273.00G/1.44G)

http://einsteinathome.org/task/386636317

Professor Ray
Professor Ray
Joined: 22 Feb 05
Posts: 46
Credit: 12593465
RAC: 3478

7/1/2013 11:29:33 PM |

7/1/2013 11:29:33 PM | Einstein@Home | Aborting task LATeah0028U_560.0_1980_0.0_1: exceeded elapsed time limit 208800.24 (300000.00G/1.44G)

Deadline: 4 Jul 2013 6:05:35 UTC

http://einsteinathome.org/task/386638957

I've aborted current WU and am suspending further participation in this project until WU's don't abort until after the deadline.

I've been dinged for almost 100 hrs now. This is an utter waste of my time otherwise.

Alinator
Alinator
Joined: 8 May 05
Posts: 927
Credit: 9352143
RAC: 0

Well, guess what. If you

Well, guess what.

If you had been paying attention, you would have realized the one you should have aborted was the one which just METE'd, since it was sent to your host BEFORE the config error was detected and fixed.

The one you aborted was sent on June 26th, and had been fixed.

So this looks more like controlled flight into terrain than anything else.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.