| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Beta Testing
Forum: Beta Test Support Forum
Thread: BETA 8, version 6.08, April 15, 2008, ANONYMOUS |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 77
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Morning, Error code 131 is something that is fixed when the work units are created before they are loaded into the grid. What this means is that the work unit results are larger than we originally estimated. This is part of beta testing to figure out the kinks in the new work units as well as bugs in the application. We are going to look into these issues today and sort them out. Thank you again for your assistance in beta testing. -Uplinger Since you know the problem, does it make sense to continue crunching these units? If not, I will abort the few remaining I have left (currently suspended on 5 different machines). If you are still getting information from units with the 131 error code, then I will continue to crunch them. Please advise. Dan [Edit 2 times, last edit by Former Member at Apr 16, 2009 4:18:26 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hello,
I received a disk quota error at the end of the WU 16.04.2009 18:27:09|World Community Grid|Aborting task BETA_CMD2_0001-1K04_A.clustersOccur-1RKC_B.clustersOccur_0_4: exceeded disk limit: 204.50MB > 200.00MB 16.04.2009 18:27:10|World Community Grid|Computation for task BETA_CMD2_0001-1K04_A.clustersOccur-1RKC_B.clustersOccur_0_4 finished 16.04.2009 18:27:10|World Community Grid|Output file BETA_CMD2_0001-1K04_A.clustersOccur-1RKC_B.clustersOccur_0_4_0 for task BETA_CMD2_0001-1K04_A.clustersOccur-1RKC_B.clustersOccur_0_4 exceeds size limit. 16.04.2009 18:27:10|World Community Grid|File size: 100540570.000000 bytes. Limit: 13902608.000000 bytes 16.04.2009 18:27:10|World Community Grid|Output file BETA_CMD2_0001-1K04_A.clustersOccur-1RKC_B.clustersOccur_0_4_1 for task BETA_CMD2_0001-1K04_A.clustersOccur-1RKC_B.clustersOccur_0_4 exceeds size limit. 16.04.2009 18:27:10|World Community Grid|File size: 6942780.000000 bytes. Limit: 5000000.000000 bytes But I am sure that I set my disk quota to an higher level: 16.04.2009 11:16:12||Preferences limit disk usage to 9.31GB There are also some strange exeptions reported in my resultlogs like: Unhandled Exception Detected... - Unhandled Exception Record - Reason: Breakpoint Encountered (0x80000003) at address 0x77790004 There is also included a long BOINC debug dump in the result log if needed. This WU was already three times reported as an error |
||
|
|
roundup
Veteran Cruncher Switzerland Joined: Jul 25, 2006 Post Count: 843 Status: Offline Project Badges: 
|
I just got another CMD2 Beta unit:
BETA_CMD2_0001-1K04_A.clustersOccur-2DDF_A.clustersOccur_0 Two trials errored out. One general question: Does it make sense to continue crunching the Beta WU when two other crunchers had an error with the same unit? |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Nope, not your settings were wrong. See posts above yours for the answer. The tasks grew bigger than the techs allowed them to be.
----------------------------------------
WCG
Please help to make the Forums an enjoyable experience for All! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nope, not your settings were wrong. See posts above yours for the answer. The tasks grew bigger than the techs allowed them to be. So, should we abort the remaining WU's. It seems pointless to crunch when the results will be deemed in error anyway. I have mine on suspend awaiting an answer. I will crunch them if something will be learned from them. However, it appears that what can be learned from this batch has all ready been learned. I am running out of regular WU's to crunch, so I need an answer soon. Thanks, Dan |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hi.
Good news. There are also valid Beta WUs around.  Nombre del Proyecto: Beta Creado: 15.04.09 Nombre: BETA_CMD2_0001-MOL2AA.clustersOccur-TBAKA.clustersOccur_0 Quórum Mínimo: 2 Replica Inicial: 3 Nombre Resultado Estatus Hora Enviado Hora Debido / Tiempo de Envío Tiempo de CPU (horas) Crédito BOINC Reclamado /Concedido BETA_ CMD2_ 0001-MOL2AA.clustersOccur-TBAKA.clustersOccur_ 0_ 0-- Aprobación Pendiente 15.04.09 15:57:35 16.04.09 06:21:24 10.67 157.0 / 0.0 BETA_ CMD2_ 0001-MOL2AA.clustersOccur-TBAKA.clustersOccur_ 0_ 1-- Aprobación Pendiente 15.04.09 15:57:06 16.04.09 17:46:28 14.13 153.1 / 0.0 BETA_ CMD2_ 0001-MOL2AA.clustersOccur-TBAKA.clustersOccur_ 0_ 2-- Aprobación Pendiente 15.04.09 15:57:05 16.04.09 13:15:36 8.45 138.7 / 0.0 So in my opinion. If there is no error with your WU you should let it crunch. Ronaldo |
||
|
|
uplinger
Former World Community Grid Tech Joined: May 23, 2005 Post Count: 3952 Status: Offline Project Badges: 
|
Nope, not your settings were wrong. See posts above yours for the answer. The tasks grew bigger than the techs allowed them to be. So, should we abort the remaining WU's. It seems pointless to crunch when the results will be deemed in error anyway. I have mine on suspend awaiting an answer. I will crunch them if something will be learned from them. However, it appears that what can be learned from this batch has all ready been learned. I am running out of regular WU's to crunch, so I need an answer soon. Thanks, Dan Dan, I'm not sure when your result was sent to you but we have increased the size allowed for the work units last night and if yours was one that had the increase it should run to completion. If it still fails and you had the increased size, we will investigate further to reduce the file sizes. So please let your work unit crunch. Thanks, -Uplinger |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nope, not your settings were wrong. See posts above yours for the answer. The tasks grew bigger than the techs allowed them to be. So, should we abort the remaining WU's. It seems pointless to crunch when the results will be deemed in error anyway. I have mine on suspend awaiting an answer. I will crunch them if something will be learned from them. However, it appears that what can be learned from this batch has all ready been learned. I am running out of regular WU's to crunch, so I need an answer soon. Thanks, Dan Dan, I'm not sure when your result was sent to you but we have increased the size allowed for the work units last night and if yours was one that had the increase it should run to completion. If it still fails and you had the increased size, we will investigate further to reduce the file sizes. So please let your work unit crunch. Thanks, -Uplinger So, if I recieved the WU in the beginning, it will error out (so abort it), but if I recieved the WU last night, then crunch it? If this is what you mean, all of mine were downloaded yesterday morning. So abort? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nope, not your settings were wrong. See posts above yours for the answer. The tasks grew bigger than the techs allowed them to be. My result log does not show the typical error code 131 issue. It is maybe something similar but its not the standard 131 error log ErrorLogLink There is something written about GetLastError 126 ?! |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Nope, not your settings were wrong. See posts above yours for the answer. The tasks grew bigger than the techs allowed them to be. So, should we abort the remaining WU's. It seems pointless to crunch when the results will be deemed in error anyway. I have mine on suspend awaiting an answer. I will crunch them if something will be learned from them. However, it appears that what can be learned from this batch has all ready been learned. I am running out of regular WU's to crunch, so I need an answer soon. Thanks, Dan Dan, I'm not sure when your result was sent to you but we have increased the size allowed for the work units last night and if yours was one that had the increase it should run to completion. If it still fails and you had the increased size, we will investigate further to reduce the file sizes. So please let your work unit crunch. Thanks, -Uplinger So, if I recieved the WU in the beginning, it will error out (so abort it), but if I recieved the WU last night, then crunch it? If this is what you mean, all of mine were downloaded yesterday morning. So abort? All of my Beta WU's were sent during the same hour as these two that errored out BETA_ CMD2_ 0001-PP1BA.clustersOccur-Q5U5U6.clustersOccur_ 0_ 2-- Dell Error 4/15/09 15:44:46 4/16/09 15:17:43 11.82 82.9 / 0.0 BETA_ CMD2_ 0001-MOL2AA.clustersOccur-PRDX6.clustersOccur_ 0_ 1-- DAN2 Error 4/15/09 15:37:56 4/16/09 13:38:50 10.32 137.1 / 0.0 |
||
|
|
|