Index  | Recent Threads  | Unanswered Threads  | Who's Active  | Guidelines  | Search
 

Quick Go »
No member browsing this thread
Thread Status: Active
Total posts in this thread: 148
Posts: 148   Pages: 15   [ Previous Page | 6 7 8 9 10 11 12 13 14 15 | Next Page ]
[ Jump to Last Post ]
Post new Thread
Author
Previous Thread This topic has been viewed 29316 times and has 147 replies Next Thread
uplinger
Former World Community Grid Tech
Joined: May 23, 2005
Post Count: 3952
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

I have re-validated what I still could. Some results had already been cleared before I could get to them. But about 75% of were able to be processed again. All should be caught up now.


I still have 10 pages (~150 WUs) of invalids showing on the website. Is there a lag in updating these or are we just SOL for these WUs?

For example, HST1_001725_000089_AT0023_T000_F00067_S00003 was invalid for all 5 sends.


marist_college,

Yes, unfortunately those that are still marked invalid are lost. There is nothing I can do to recover the data. You should still get credit for these. I checked Sekerob's results and all the invalids were granted credit.

Thanks,
-Uplinger
[May 14, 2016 3:27:00 AM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

From a research point of view, what will happen to a result like this, where all returns were either Invalid or Server Aborted? I'd like to think that the researchers will understand that the 13 May problem was a validator one and will be able to re-run the affected units that were still returned Invalid, despite your valiant efforts, Keith.

HST1_ 002010_ 000082_ MT0003_ T001_ F00097_ S00001_ 4-- Microsoft Windows 10 Professional x64 Edition, (10.00.10586.00) 714 Server Aborted 13/05/16 06:56:16 13/05/16 16:15:29 0.00 334.8 / 0.0
HST1_ 002010_ 000082_ MT0003_ T001_ F00097_ S00001_ 2-- Microsoft Windows 8.1 Professional x64 Edition, (06.03.9600.00) 714 Invalid 13/05/16 06:56:15 13/05/16 16:08:21 1.78 75.0 / 75.0
HST1_ 002010_ 000082_ MT0003_ T001_ F00097_ S00001_ 3-- Microsoft Windows 10 Professional x64 Edition, (10.00.10586.00) 714 Invalid 13/05/16 06:56:15 13/05/16 14:30:21 2.19 72.7 / 72.7
HST1_ 002010_ 000082_ MT0003_ T001_ F00097_ S00001_ 1-- Microsoft Windows 10 Professional x64 Edition, (10.00.10586.00) 714 Invalid 11/05/16 18:03:04 13/05/16 06:56:11 1.83 65.8 / 65.8
HST1_ 002010_ 000082_ MT0003_ T001_ F00097_ S00001_ 0-- Microsoft Windows 8.1 Professional x64 Edition, (06.03.9600.00) 714 Invalid 11/05/16 18:03:04 12/05/16 08:01:44 1.82 79.2 / 79.2
[May 14, 2016 6:50:44 AM]   Link   Report threatening or abusive post: please login first  Go to top 
SekeRob
Master Cruncher
Joined: Jan 7, 2013
Post Count: 2741
Status: Offline
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

I have re-validated what I still could. Some results had already been cleared before I could get to them. But about 75% of were able to be processed again. All should be caught up now.


I still have 10 pages (~150 WUs) of invalids showing on the website. Is there a lag in updating these or are we just SOL for these WUs?

For example, HST1_001725_000089_AT0023_T000_F00067_S00003 was invalid for all 5 sends.


marist_college,

Yes, unfortunately those that are still marked invalid are lost. There is nothing I can do to recover the data. You should still get credit for these. I checked Sekerob's results and all the invalids were granted credit.

Thanks,
-Uplinger

Glad you could at least recoup the bulk. Suppose it becomes a re-run for those that missed the boat [after some index yes/no accounting]. Have marked the 19 with a manual 1, creating a new mask to get them off the DB Active list in the hunting tool [They were at 00:06:02 UTC still listed as invalid]. Note though that the day stat total did not include the 19 still shown as invalid.

C'Est La Vie
[May 14, 2016 8:22:45 AM]   Link   Report threatening or abusive post: please login first  Go to top 
SekeRob
Master Cruncher
Joined: Jan 7, 2013
Post Count: 2741
Status: Offline
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

Some really weird wheels needed turning as of the 19 Invalid without credit 17 showed up again, this time with points credit in the 12:06 UTC stats, so almost all worked according some laid plan :D)
----------------------------------------
[Edit 1 times, last edit by SekeRob* at May 14, 2016 2:53:07 PM]
[May 14, 2016 2:48:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Simplex0
Advanced Cruncher
Sweden
Joined: Aug 14, 2008
Post Count: 83
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

It seams that I only get work units for my AMD-computer an they seams to work but ends up as Invalid after they are finished after 9 hours so from now on I will delete all TB work units on that computer. I also have en Intel-computer but it seams as I not get any TB work units on that one.
----------------------------------------
[Edit 1 times, last edit by Simplex0 at May 14, 2016 6:15:24 PM]
[May 14, 2016 2:48:52 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Eric_Kaiser
Veteran Cruncher
Germany (Hessen)
Joined: May 7, 2013
Post Count: 1047
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

Simplex0, create a profile for your amd and uncheck HST and you're done.
----------------------------------------

[May 14, 2016 3:44:28 PM]   Link   Report threatening or abusive post: please login first  Go to top 
KerSamson
Master Cruncher
Switzerland
Joined: Jan 29, 2007
Post Count: 1684
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

@Simplex0
What AMD CPU?
What operating system?
---
On my side, the major HST1 contributor hosts are two Phenom II x6 running Ubuntu 14.04 x64 LTS.
Cheers,
Yves
----------------------------------------
[May 14, 2016 10:14:05 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Former Member
Cruncher
Joined: May 22, 2018
Post Count: 0
Status: Offline
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

I've just seen a PVer go Invalid again, without any indication of a problem in the Result Log. In fact, _0 (mine, Valid) and _1 (Invalid) had very "clean" logs, whereas _2 (Valid) had 2 restarts from checkpoint, after steps 97550 & 98100. Clearly, the Result Logs don't show all the data used for validation.

HST1_ 002260_ 000061_ AC0019_ T300_ F00061_ S00004_ 2-- Microsoft Windows 8.1 Professional x64 Edition, (06.03.9600.00) 714 Valid 18/05/16 12:47:26 27/05/16 15:38:03 33.13 206.1 / 351.3
HST1_ 002260_ 000061_ AC0019_ T300_ F00061_ S00004_ 0-- Microsoft Windows 10 Core x64 Edition, (10.00.10586.00) 714 Valid 16/05/16 07:03:07 18/05/16 12:47:18 16.61 385.6 / 351.3
HST1_ 002260_ 000061_ AC0019_ T300_ F00061_ S00004_ 1-- Microsoft Windows 7 Home Premium x64 Edition, Service Pack 1, (06.01.7601.00) 714 Invalid 16/05/16 07:03:07 17/05/16 06:03:52 13.54 186.9 / 175.7
[May 28, 2016 7:36:54 AM]   Link   Report threatening or abusive post: please login first  Go to top 
RTS48
Veteran Cruncher
Bolivia
Joined: Aug 2, 2009
Post Count: 1353
Status: Offline
Project Badges:
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

Once again the Invalid WUs start (I'm sure that this one was Valid this morning. Can't see any error code. What's going wrong? Here's the Result Log

Result Name: HST1_ 003588_ 000067_ KT0004_ T400_ F00067_ S00001_ 0--
<core_client_version>7.6.22</core_client_version>
<![CDATA[
<stderr_txt>
INFO: No state to restore. Start from the beginning.
[14:12:26] INFO: Running initial simulation
Writing checkpoint at step 600.
Writing checkpoint at step 1190.
Writing checkpoint at step 1790.
[14:29:20] INFO: Completed step 2000 of initial simulation
Writing checkpoint at step 2390.
Writing checkpoint at step 3000.
Writing checkpoint at step 3610.
[14:45:45] INFO: Completed step 4000 of initial simulation
Writing checkpoint at step 4220.
Writing checkpoint at step 4830.
Writing checkpoint at step 5450.
[15:02:02] INFO: Completed step 6000 of initial simulation
Writing checkpoint at step 6060.
Writing checkpoint at step 6680.
Writing checkpoint at step 7300.
Writing checkpoint at step 7910.
[15:18:16] INFO: Completed step 8000 of initial simulation
Writing checkpoint at step 8520.
Writing checkpoint at step 9130.
Writing checkpoint at step 9740.
[15:34:40] INFO: Completed step 10000 of initial simulation
Writing checkpoint at step 10350.
Writing checkpoint at step 10970.
Writing checkpoint at step 11580.
[15:51:01] INFO: Completed step 12000 of initial simulation
Writing checkpoint at step 12190.
Writing checkpoint at step 12800.
Writing checkpoint at step 13410.
[16:07:24] INFO: Completed step 14000 of initial simulation
Writing checkpoint at step 14020.
Writing checkpoint at step 14630.
Writing checkpoint at step 15230.
Writing checkpoint at step 15830.
[16:23:55] INFO: Completed step 16000 of initial simulation
Writing checkpoint at step 16440.
Writing checkpoint at step 17040.
Writing checkpoint at step 17650.
[16:40:28] INFO: Completed step 18000 of initial simulation
Writing checkpoint at step 18250.
Writing checkpoint at step 18860.
Writing checkpoint at step 19460.
[16:57:02] INFO: Completed step 20000 of initial simulation
Writing checkpoint at step 20060.
Writing checkpoint at step 20670.
Writing checkpoint at step 21270.
Writing checkpoint at step 21870.
[17:13:38] INFO: Completed step 22000 of initial simulation
Writing checkpoint at step 22470.
Writing checkpoint at step 23070.
Writing checkpoint at step 23670.
[17:30:16] INFO: Completed step 24000 of initial simulation
Writing checkpoint at step 24270.
Writing checkpoint at step 24860.
Writing checkpoint at step 25460.
[17:47:05] INFO: Completed step 26000 of initial simulation
Writing checkpoint at step 26060.
Writing checkpoint at step 26660.
Writing checkpoint at step 27230.
Writing checkpoint at step 27820.
[18:04:03] INFO: Completed step 28000 of initial simulation
Writing checkpoint at step 28420.
Writing checkpoint at step 29010.
Writing checkpoint at step 29600.
[18:20:54] INFO: Completed step 30000 of initial simulation
Writing checkpoint at step 30200.
Writing checkpoint at step 30780.
Writing checkpoint at step 31370.
Writing checkpoint at step 31960.
[18:37:54] INFO: Completed step 32000 of initial simulation
Writing checkpoint at step 32550.
Writing checkpoint at step 33150.
Writing checkpoint at step 33740.
[18:54:44] INFO: Completed step 34000 of initial simulation
Writing checkpoint at step 34340.
Writing checkpoint at step 34930.
Writing checkpoint at step 35520.
[19:11:38] INFO: Completed step 36000 of initial simulation
Writing checkpoint at step 36110.
Writing checkpoint at step 36700.
Writing checkpoint at step 37290.
Writing checkpoint at step 37880.
[19:28:34] INFO: Completed step 38000 of initial simulation
Writing checkpoint at step 38470.
Writing checkpoint at step 39060.
Writing checkpoint at step 39650.
[19:45:31] INFO: Completed step 40000 of initial simulation
Writing checkpoint at step 40240.
Writing checkpoint at step 40830.
Writing checkpoint at step 41420.
[20:02:28] INFO: Completed step 42000 of initial simulation
Writing checkpoint at step 42010.
Writing checkpoint at step 42600.
Writing checkpoint at step 43190.
Writing checkpoint at step 43770.
[20:19:29] INFO: Completed step 44000 of initial simulation
Writing checkpoint at step 44360.
Writing checkpoint at step 44950.
Writing checkpoint at step 45540.
[20:36:29] INFO: Completed step 46000 of initial simulation
Writing checkpoint at step 46130.
Writing checkpoint at step 46720.
Writing checkpoint at step 47300.
Writing checkpoint at step 47890.
[20:53:28] INFO: Completed step 48000 of initial simulation
Writing checkpoint at step 48480.
Writing checkpoint at step 49070.
Writing checkpoint at step 49660.
[21:10:30] INFO: Completed step 50000 of initial simulation
Writing checkpoint at step 50240.
Writing checkpoint at step 50830.
Writing checkpoint at step 51410.
Writing checkpoint at step 51990.
[21:27:37] INFO: Completed step 52000 of initial simulation
Writing checkpoint at step 52580.
Writing checkpoint at step 53160.
Writing checkpoint at step 53740.
[21:44:49] INFO: Completed step 54000 of initial simulation
Writing checkpoint at step 54320.
Writing checkpoint at step 54890.
Writing checkpoint at step 55470.
[22:02:10] INFO: Completed step 56000 of initial simulation
Writing checkpoint at step 56050.
Writing checkpoint at step 56620.
Writing checkpoint at step 57200.
Writing checkpoint at step 57770.
[22:19:32] INFO: Completed step 58000 of initial simulation
Writing checkpoint at step 58350.
Writing checkpoint at step 58920.
Writing checkpoint at step 59490.
[22:36:58] INFO: Completed step 60000 of initial simulation
Writing checkpoint at step 60070.
Writing checkpoint at step 60640.
Writing checkpoint at step 61220.
Writing checkpoint at step 61790.
[22:54:25] INFO: Completed step 62000 of initial simulation
Writing checkpoint at step 62360.
Writing checkpoint at step 62930.
Writing checkpoint at step 63500.
[23:11:56] INFO: Completed step 64000 of initial simulation
Writing checkpoint at step 64070.
Writing checkpoint at step 64640.
Writing checkpoint at step 65210.
Writing checkpoint at step 65780.
[23:29:32] INFO: Completed step 66000 of initial simulation
Writing checkpoint at step 66340.
Writing checkpoint at step 66910.
Writing checkpoint at step 67480.
[23:47:11] INFO: Completed step 68000 of initial simulation
Writing checkpoint at step 68040.
Writing checkpoint at step 68610.
Writing checkpoint at step 69170.
Writing checkpoint at step 69740.
[00:04:52] INFO: Completed step 70000 of initial simulation
Writing checkpoint at step 70310.
Writing checkpoint at step 70870.
Writing checkpoint at step 71440.
[00:22:31] INFO: Completed step 72000 of initial simulation
Writing checkpoint at step 72010.
Writing checkpoint at step 72570.
Writing checkpoint at step 73130.
Writing checkpoint at step 73700.
[00:40:12] INFO: Completed step 74000 of initial simulation
Writing checkpoint at step 74270.
Writing checkpoint at step 74830.
Writing checkpoint at step 75400.
Writing checkpoint at step 75970.
[00:57:51] INFO: Completed step 76000 of initial simulation
Writing checkpoint at step 76530.
Writing checkpoint at step 77100.
Writing checkpoint at step 77670.
[01:15:31] INFO: Completed step 78000 of initial simulation
Writing checkpoint at step 78230.
Writing checkpoint at step 78800.
Writing checkpoint at step 79360.
Writing checkpoint at step 79930.
[01:33:11] INFO: Completed step 80000 of initial simulation
Writing checkpoint at step 80500.
Writing checkpoint at step 81060.
Writing checkpoint at step 81630.
[01:50:49] INFO: Completed step 82000 of initial simulation
Writing checkpoint at step 82200.
Writing checkpoint at step 82770.
Writing checkpoint at step 83330.
Writing checkpoint at step 83880.
[02:08:36] INFO: Completed step 84000 of initial simulation
Writing checkpoint at step 84440.
Writing checkpoint at step 85000.
Writing checkpoint at step 85560.
[02:26:23] INFO: Completed step 86000 of initial simulation
Writing checkpoint at step 86140.
Writing checkpoint at step 86710.
Writing checkpoint at step 87280.
Writing checkpoint at step 87860.
[02:43:44] INFO: Completed step 88000 of initial simulation
Writing checkpoint at step 88450.
Writing checkpoint at step 89040.
Writing checkpoint at step 89620.
[03:00:47] INFO: Completed step 90000 of initial simulation
Writing checkpoint at step 90210.
Writing checkpoint at step 90790.
Writing checkpoint at step 91380.
Writing checkpoint at step 91970.
[03:17:50] INFO: Completed step 92000 of initial simulation
Writing checkpoint at step 92550.
Writing checkpoint at step 93140.
Writing checkpoint at step 93730.
[03:34:53] INFO: Completed step 94000 of initial simulation
Writing checkpoint at step 94310.
Writing checkpoint at step 94900.
Writing checkpoint at step 95480.
[03:51:56] INFO: Completed step 96000 of initial simulation
Writing checkpoint at step 96070.
Writing checkpoint at step 96650.
Writing checkpoint at step 97220.
Writing checkpoint at step 97800.
[04:09:18] INFO: Completed step 98000 of initial simulation
Writing checkpoint at step 98380.
Writing checkpoint at step 98970.
Writing checkpoint at step 99560.
[04:26:18] INFO: Completed step 100000 of initial simulation
Writing checkpoint at step 100000.
[04:26:20] INFO: Finished initial simulation.
[04:26:20] INFO: Running secondary simulation
[04:34:48] INFO: Run complete, CPU time: 50831.831228
04:34:48 (381): called boinc_finish(0)

</stderr_txt>
]]>
----------------------------------------
Rod Peel
Santa Cruz
Bolivia
South America

,
,
[Jun 15, 2016 8:46:36 PM]   Link   Report threatening or abusive post: please login first  Go to top 
SekeRob
Master Cruncher
Joined: Jan 7, 2013
Post Count: 2741
Status: Offline
Reply to this Post  Reply with Quote 
Re: HST1 Pending Verification - Please report here exact OS if yours turns invalid!

Two beta threads for you

https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,39209
https://secure.worldcommunitygrid.org/forums/wcg/viewthread_thread,39243

Ponder on what they will resolve if the app is promoted to production... passes the tests.
[Jun 15, 2016 8:55:45 PM]   Link   Report threatening or abusive post: please login first  Go to top 
Posts: 148   Pages: 15   [ Previous Page | 6 7 8 9 10 11 12 13 14 15 | Next Page ]
[ Jump to Last Post ]
Post new Thread