rpi_logo
Validation Inconclusive Errors
Validation Inconclusive Errors
log in

Advanced search

Message boards : News : Validation Inconclusive Errors

1 · 2 · Next
Author Message
Sidd
Project developer
Project tester
Project scientist
Send message
Joined: 19 May 14
Posts: 70
Credit: 356,131
RAC: 0

Message 66933 - Posted: 6 Jan 2018, 2:42:37 UTC

Hi all,

There has been some reports of validation inconclusive issues occurring with the Nbody workunits. It seems to be isolated to the nbody app. I believe this coincided with a database issue on our end. I am working on resolving the issue.

Thank you for you patience and continued support,
Sidd

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66934 - Posted: 6 Jan 2018, 13:05:20 UTC - in response to Message 66933.

Thank you for the heads up!!

Svet pribehu
Send message
Joined: 2 Apr 17
Posts: 3
Credit: 447,013
RAC: 321

Message 66937 - Posted: 6 Jan 2018, 23:58:47 UTC

Yea, about 95% of tasks are inconclusive valid. I waiting to solve to solve this. :)

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66939 - Posted: 7 Jan 2018, 1:14:23 UTC - in response to Message 66937.

Yea, about 95% of tasks are inconclusive valid. I waiting to solve to solve this. :)


Te unsent problems are back though! I have a whole page of workunits I finished that are unsent to a 2nd pc!!

Svet pribehu
Send message
Joined: 2 Apr 17
Posts: 3
Credit: 447,013
RAC: 321

Message 66940 - Posted: 7 Jan 2018, 1:26:52 UTC - in response to Message 66939.

I have many tasks computed by me and the second compute is "Canceled by server" or "Unnecessary" or "unsend".

I think tha the unsend one is mater of time...

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66941 - Posted: 7 Jan 2018, 13:44:06 UTC - in response to Message 66940.

I have many tasks computed by me and the second compute is "Canceled by server" or "Unnecessary" or "unsend".

I think tha the unsend one is mater of time...


Yes it does seem to have caught up again for me, I do not like these ongoing problems they seem to be having.

Dataman
Avatar
Send message
Joined: 5 Sep 08
Posts: 19
Credit: 141,179,875
RAC: 111,591

Message 66943 - Posted: 9 Jan 2018, 13:46:14 UTC

I have ~1,500 inconclusive wu's now. If not resolved soon I will have to move over to another project. Any updates?
____________

Profile ritterm
Avatar
Send message
Joined: 16 Jun 08
Posts: 92
Credit: 365,629,434
RAC: 0

Message 66944 - Posted: 9 Jan 2018, 14:54:53 UTC

And I just noticed I'm building up inconclusives for the MilkyWay@Home app, not just the N-Body, as was the case in the last couple of days.
____________

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66945 - Posted: 9 Jan 2018, 17:30:47 UTC - in response to Message 66943.

I have ~1,500 inconclusive wu's now. If not resolved soon I will have to move over to another project. Any updates?


At least mine aren't 'unsent" anymore!! I still have 78 of them after not returning any workunits since last night, I had about 130 then with almost all of them "unsent". I going to resume crunching on my one machine I have here and see how bad it gets when I check later on. With the 10 day or so time frame and only getting 80 workunits at a time I can suspend MW whenever it gets too many "inconclusive" and within that too many "unsent" workunits.

Sidd
Project developer
Project tester
Project scientist
Send message
Joined: 19 May 14
Posts: 70
Credit: 356,131
RAC: 0

Message 66946 - Posted: 10 Jan 2018, 8:57:07 UTC

Hi all,

Can you please list some of the workunits that are marked as inconclusive and unsent?


Thanks,
Sidd

Svet pribehu
Send message
Joined: 2 Apr 17
Posts: 3
Credit: 447,013
RAC: 321

Message 66948 - Posted: 10 Jan 2018, 10:03:28 UTC
Last modified: 10 Jan 2018, 10:47:03 UTC

How about this?

Task- - - - - - - -Work unit
1555379414 1555377127
2214992488 1555377227
2214990445 1555375193
2214990446 1555375194
2214988358 1555373133
2214988359 1555373134
2214949997 1555335629
2214949998 1555335630
2214949999 1555335631
2214950079 1555335711
2214947692 1555333328
2214947701 1555333337
2214945106 1555330913

Profile ritterm
Avatar
Send message
Joined: 16 Jun 08
Posts: 92
Credit: 365,629,434
RAC: 0

Message 66949 - Posted: 10 Jan 2018, 11:38:12 UTC - in response to Message 66946.

Can you please list some of the workunits that are marked as inconclusive and unsent?

For me, the N-Body inconclusives are clearing out nicely. It seems now that it's the MilkyWay@Home app that's lagging. Recent examples:

1560210075
1560204482
1560197795
1560195886
1560188186
____________

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66950 - Posted: 10 Jan 2018, 12:50:03 UTC - in response to Message 66946.

Hi all,

Can you please list some of the workunits that are marked as inconclusive and unsent?


Thanks,
Sidd


I have a fricking page full of them!!!

1560426341
1560321565
1554916207
1560425463
1560279897
1560226938

I could go on and on but if they are showing up that way for me WHY can't YOU see them too? Validation inconclusive (132)

Profile ritterm
Avatar
Send message
Joined: 16 Jun 08
Posts: 92
Credit: 365,629,434
RAC: 0

Message 66951 - Posted: 10 Jan 2018, 14:42:50 UTC - in response to Message 66949.

For me, the N-Body inconclusives are clearing out nicely. It seems now that it's the MilkyWay@Home app that's lagging...

Looks like progress is being made. All of my inconclusives have wingmen now.
____________

Dataman
Avatar
Send message
Joined: 5 Sep 08
Posts: 19
Credit: 141,179,875
RAC: 111,591

Message 66952 - Posted: 10 Jan 2018, 15:27:42 UTC - in response to Message 66946.

Hi all,

Can you please list some of the workunits that are marked as inconclusive and unsent?


Thanks,
Sidd


Thanks Sidd for looking into this.It appears my wu's are clearing up as well.
____________

Profile Jozef J
Send message
Joined: 4 Mar 10
Posts: 60
Credit: 593,992,391
RAC: 2

Message 66954 - Posted: 11 Jan 2018, 2:09:24 UTC

whole day and until now i can not log in here or read.. database error. but some like this i see sometimes from autumn 2017 and last 1 month nearly every day .
if they work on database WHY not annoucment like other project?
Or "half failure state" on this project is new "normal" ??
turn project to beta or alfa state

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66957 - Posted: 11 Jan 2018, 14:12:11 UTC - in response to Message 66951.

For me, the N-Body inconclusives are clearing out nicely. It seems now that it's the MilkyWay@Home app that's lagging...


Looks like progress is being made. All of my inconclusives have wingmen now.


Mine appear to be also but then I have crunched any new ones since yesterday either! This is a royal pain having to babysit this project, I lost over 500 completed workunits during the last database crash and I'm very hesitant to let that happen again. I assume they are trying but something isn't working.

Mr McGill
Send message
Joined: 13 Nov 17
Posts: 4
Credit: 1,973,379
RAC: 4,424

Message 66964 - Posted: 14 Jan 2018, 17:44:44 UTC

I own a measly laptop and have been trying to contribute what i can using the decent computation , but the Nbody tasks have interesting properties where at least half tend to get 'caught' in their own processing, to the state where after a day of running, they claim they will be done in two days, or on occasion get trapped for a few days and report a completion time beyond the reporting time.

Is there a way to allow these processes that literally get stuck at a certain component to automatically abort and report the troublesome step or stage to you guys to permit improvements to the code?
As of right now if after a few hours the time remaining starts ballooning i abort manually as there is no way that a 95% complete process that has been running for 2 hours should still be at 95% completion an hour later, which is something i have witnessed.
I note that Bio-inc doesn't even notice when the predicted time to completion ends up beyond the report time and cancel the process then. which is what was previously happening to Nbody before i started manually monitoring it's progress.
I don't know why Nbody is doing this, but i have offered plenty of memory (which it hasn't used) it steadily reduces the CPU usage as it jams up and bioinc has access to a few gigs of storage which it has barely scratched while doing this computation, so i am puzzled if the issue is a bottleneck or a crashing component.

Cameron
Send message
Joined: 16 Dec 07
Posts: 25
Credit: 988,531
RAC: 2,696

Message 66965 - Posted: 15 Jan 2018, 2:55:55 UTC

Anything going to happen to the inconclusive.... Cancelled Results?

some of the 35 I have

workunit 1551469684
workunit 1555077585
workunit 1555224430
workunit 1555253384
workunit 1555405588

Profile mikey
Avatar
Send message
Joined: 8 May 09
Posts: 2182
Credit: 231,022,987
RAC: 204,448

Message 66966 - Posted: 15 Jan 2018, 13:19:34 UTC - in response to Message 66964.

I own a measly laptop and have been trying to contribute what i can using the decent computation , but the Nbody tasks have interesting properties where at least half tend to get 'caught' in their own processing, to the state where after a day of running, they claim they will be done in two days, or on occasion get trapped for a few days and report a completion time beyond the reporting time.

Is there a way to allow these processes that literally get stuck at a certain component to automatically abort and report the troublesome step or stage to you guys to permit improvements to the code?
As of right now if after a few hours the time remaining starts ballooning i abort manually as there is no way that a 95% complete process that has been running for 2 hours should still be at 95% completion an hour later, which is something i have witnessed.
I note that Bio-inc doesn't even notice when the predicted time to completion ends up beyond the report time and cancel the process then. which is what was previously happening to Nbody before i started manually monitoring it's progress.
I don't know why Nbody is doing this, but i have offered plenty of memory (which it hasn't used) it steadily reduces the CPU usage as it jams up and bioinc has access to a few gigs of storage which it has barely scratched while doing this computation, so i am puzzled if the issue is a bottleneck or a crashing component.


Some people have said if you suspend then resume them they finish right up.

1 · 2 · Next
Post to thread

Message boards : News : Validation Inconclusive Errors


Main page · Your account · Message boards


Copyright © 2018 AstroInformatics Group