n-body workunits with maximum time elapsed
log in

Advanced search

Message boards : News : n-body workunits with maximum time elapsed

Author Message
Profile Travis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0

Message 48516 - Posted: 7 May 2011, 5:12:52 UTC

I've been pretty busy trying to track down this bug (I've seen the same thing happening to us over at DNA@Home), and tried a couple changes to the database today. Is anyone still seeing this issue, or did that happen to fix it?
____________

Profile The Gas Giant
Avatar
Send message
Joined: 24 Dec 07
Posts: 1947
Credit: 240,884,648
RAC: 29

Message 48517 - Posted: 7 May 2011, 5:28:05 UTC
Last modified: 7 May 2011, 5:32:57 UTC

I'm seeing all wu's being marked as invalid...as are others!

Profile Travis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0

Message 48518 - Posted: 7 May 2011, 5:44:08 UTC - in response to Message 48517.

I'm seeing all wu's being marked as invalid...as are others!


I think that's an application problem. Are they immediately erroring out?

On my end it looks like workunits are being reported and validated correctly.
____________

Profile The Gas Giant
Avatar
Send message
Joined: 24 Dec 07
Posts: 1947
Credit: 240,884,648
RAC: 29

Message 48519 - Posted: 7 May 2011, 5:50:07 UTC
Last modified: 7 May 2011, 5:51:47 UTC

Completing in normal time.. check this out.

Thought you might have made a change as I was running an app_info and 2 concurrent wu's, so I got rid of the app_info and restarted. Still being marked as invalid.

John G
Send message
Joined: 1 Apr 10
Posts: 49
Credit: 171,863,025
RAC: 0

Message 48520 - Posted: 7 May 2011, 6:05:26 UTC

Not fixed for sure --- it appears that almost all of my wu's at this point are getting invalidated ??? and has only happened in the last 2 to 3 hours ??
____________

Profile Toppie*
Send message
Joined: 28 Mar 09
Posts: 68
Credit: 1,003,982,681
RAC: 0

Message 48521 - Posted: 7 May 2011, 6:35:22 UTC - in response to Message 48520.

Not fixed for sure --- it appears that almost all of my wu's at this point are getting invalidated ??? and has only happened in the last 2 to 3 hours ??


Same here. A from 04:54 UTC all (looks like it) 60+ wu invalidated.

Jesse Viviano
Send message
Joined: 4 Feb 11
Posts: 82
Credit: 35,684,299
RAC: 12,908

Message 48522 - Posted: 7 May 2011, 6:49:11 UTC

It seems that all the results I am turning in are now being marked invalid for the main MilkyWay@home application.

FruehwF
Send message
Joined: 28 Feb 10
Posts: 120
Credit: 109,840,492
RAC: 0

Message 48523 - Posted: 7 May 2011, 7:30:33 UTC

same here on all machines.

after some time:
Error Message:
07.05.2011 08:39:55 | Milkyway@home | [coproc] Insufficient ATI for de_separation_13_3s_fix20_1_4617297_1304743175_1: need 0.500000

and bonic switched to backup project

when i switch to 1 concurrent Tasks milkyway@home continued working, but Wu's erroed out again.
-.-

Profile Travis
Volunteer moderator
Project administrator
Project developer
Project tester
Project scientist
Send message
Joined: 30 Aug 07
Posts: 2046
Credit: 26,480
RAC: 0

Message 48524 - Posted: 7 May 2011, 7:39:35 UTC - in response to Message 48519.

Completing in normal time.. check this out.

Thought you might have made a change as I was running an app_info and 2 concurrent wu's, so I got rid of the app_info and restarted. Still being marked as invalid.


Those are the regular application, not the n-body application.
____________

Profile The Gas Giant
Avatar
Send message
Joined: 24 Dec 07
Posts: 1947
Credit: 240,884,648
RAC: 29

Message 48532 - Posted: 7 May 2011, 10:47:28 UTC

OK...fair cop. Still have the invalid problem though...

ivk
Send message
Joined: 10 Feb 10
Posts: 6
Credit: 157,756,946
RAC: 0

Message 48559 - Posted: 7 May 2011, 21:49:18 UTC - in response to Message 48516.

all of my WUs are being aborted, prematurely, with the following diagnostics:

07/05/2011 22:43:54 Milkyway@home Starting de_separation_10_3s_fix10_1_287737_1304804381_0
07/05/2011 22:43:54 Milkyway@home Starting task de_separation_10_3s_fix10_1_287737_1304804381_0 using milkyway version 62
07/05/2011 22:45:25 Milkyway@home Aborting task de_separation_10_3s_fix10_1_287737_1304804381_0: exceeded elapsed time limit 89.484881
07/05/2011 22:45:26 Milkyway@home Computation for task de_separation_10_3s_fix10_1_287737_1304804381_0 finished

obviously the "elapsed time limit2 is being computed incorrectly by the server.
____________

Profile Toppie*
Send message
Joined: 28 Mar 09
Posts: 68
Credit: 1,003,982,681
RAC: 0

Message 48599 - Posted: 8 May 2011, 15:08:28 UTC - in response to Message 48532.

I started tearing my hair out. Resetting didn't help and neither detaching / reattaching. Uninstalled Boinc and a complete re-install did the trick for me.
Running n-body merrily now...just have to wait for the validation trick...
Still don't know hy it seems to work.

And apologies to my wingmen for all the aborted tasks...

TJ
Send message
Joined: 12 Aug 09
Posts: 262
Credit: 91,881,498
RAC: 26

Message 48600 - Posted: 8 May 2011, 16:15:41 UTC

Travis what have you done?

The GPU WU's run again at my rig and are validated and granted credit as well.
But thet are running in high priorty while the deadline is May 16th and they only take 01:55 to complete.
And they cued up, before one maximum two where ready and then send to your database and I got new ones.

Last week everything was running like a rocket.
____________
Greetings from,
TJ


Post to thread

Message boards : News : n-body workunits with maximum time elapsed


Main page · Your account · Message boards


Copyright © 2018 AstroInformatics Group