| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: New to BOINC - Error or Invalid status codes? |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 26
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Hey all,
I just moved all of my computers from UD.com to WCG and when I did I decided to migrate to BOINC for the first time. So far so good, for the most part, but the "error" and "invalid" status codes are new to me. I did a search but couldn't find an existing thread that provided any help. Received this on a new PC I just added last night (first time I've seen this): <core_client_version>5.4.9</core_client_version> <message> The environment is incorrect. (0xa) - exit code 10 (0xa) </message> <stderr_txt> [20:27:43] [INFO] Checkpoint complete [21:16:43] [INFO] Checkpoint complete [21:57:28] [INFO] Checkpoint complete [22:38:11] [INFO] Checkpoint complete [23:09:43] [INFO] Checkpoint complete [23:39:18] [INFO] Checkpoint complete [00:12:01] [INFO] Checkpoint complete [00:45:18] [INFO] Checkpoint complete [01:12:54] [INFO] Checkpoint complete ERROR Exception occurred while running Rosetta: Exception code: 0xc0000005 Exception address: 0x00488EB6 And I had my first BOINC computer return four of these "invalid" responses in the same day, then it no longer happened. <core_client_version>5.4.9</core_client_version> <stderr_txt> [05:28:20] [INFO] Checkpoint complete [05:34:50] [INFO] Checkpoint complete [05:43:21] [INFO] Checkpoint complete [05:51:23] [INFO] Checkpoint complete [05:58:43] [INFO] Checkpoint complete [06:05:13] [INFO] Checkpoint complete [06:11:30] [INFO] Checkpoint complete [06:16:38] [INFO] Checkpoint complete [06:24:05] [INFO] Checkpoint complete [06:30:51] [INFO] Checkpoint complete [06:37:56] [INFO] Checkpoint complete [06:43:31] [INFO] Checkpoint complete [06:51:39] [INFO] Checkpoint complete [06:58:45] [INFO] Checkpoint complete [07:05:16] [INFO] Checkpoint complete [07:12:47] [INFO] Checkpoint complete [07:25:51] [INFO] Checkpoint complete [07:38:43] [INFO] Checkpoint complete [07:46:43] [INFO] Checkpoint complete [07:53:47] [INFO] Checkpoint complete [08:00:04] [INFO] Checkpoint complete [08:06:22] [INFO] Checkpoint complete [08:12:42] [INFO] Checkpoint complete [08:19:10] [INFO] Checkpoint complete [08:28:34] [INFO] Checkpoint complete [08:32:55] [INFO] Checkpoint complete [08:41:26] [INFO] Checkpoint complete [08:47:17] [INFO] Checkpoint complete [08:55:07] [INFO] Checkpoint complete [INFO] Rosetta finishing with return code: 0 </stderr_txt> PLUS, I still have a TON of work units listed as "Pending", some from as far back as from July 3 (the day I migrated from UD) and July 5. Is this normal behavior for BOINC? If so, no problems. I'm just not familiar enough with BOINC to know that yet. Thanks in advance for any help.... -John Phoenix, AZ |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The "Pending" results are nothing to worry about - in the worst case, work units may hang around for a week.
The invalid results were probably caused by the transition from HPF2 5.06->5.07. This was an exceptional situation, and you will have received credit for these results (normally you don't for invalid results, because it means your result didn't match all the others). The errors are more important. There are still a few glitches even with the new 5.07 version, and the tech team are working on it. If you could provide the work unit names and times you returned them (just for the error results) that would help immensely. Have you just had this single error? |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Not sure on the error codes. Could be you were running some of the new HPF2 files. At the beginning of the project there was some problems with the files which caused them to not run properly. We should jusst about have all the bad files flushed out of the grid or will shortly.
On the pending validation, not a big deal. What there waiting for is someone else to get done processing that same file and then you'll get credit for it. It's not unusual to have pending files 2-4 weeks old sitting there. Some members have had as many as 35-40 pending validation, so don't worry. This thread talks about some of the new problems: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=7744 Talks about the same problem you had: http://www.worldcommunitygrid.org/forums/wcg/viewthread?thread=7892#63516 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Sorry in advance for the long length but I cut and pasted the entire log from the client, from installation last night up to now. I BOLDED the lines with the error.. any thoughts? This machine isn't the fastest in the world so it hasn't returned another work unit yet.
7/7/2006 7:42:23 PM||Starting BOINC client version 5.4.9 for windows_intelx86 7/7/2006 7:42:23 PM||libcurl/7.15.3 OpenSSL/0.9.8a zlib/1.2.3 7/7/2006 7:42:23 PM||Data directory: C:\Program Files\BOINC 7/7/2006 7:42:23 PM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 CPU 1.60GHz 7/7/2006 7:42:23 PM||Memory: 511.55 MB physical, 1.22 GB virtual 7/7/2006 7:42:23 PM||Disk: 37.26 GB total, 30.23 GB free 7/7/2006 7:42:26 PM||No general preferences found - using BOINC defaults 7/7/2006 7:42:26 PM||Local control only allowed 7/7/2006 7:42:26 PM||Listening on port 31416 7/7/2006 7:42:26 PM||Platform changed from to windows_intelx86 - resetting projects 7/7/2006 7:42:26 PM||This computer is not attached to any projects 7/7/2006 7:42:26 PM||Visit http://boinc.berkeley.edu for instructions 7/7/2006 7:42:26 PM||Suspending network activity - running CPU benchmarks 7/7/2006 7:42:27 PM||Resuming network activity 7/7/2006 7:42:28 PM||Running CPU benchmarks 7/7/2006 7:42:43 PM||Fetching configuration file from http://www.worldcommunitygrid.org/get_project_config.php 7/7/2006 7:42:56 PM|http://www.worldcommunitygrid.org/|Scheduler list download succeeded 7/7/2006 7:42:56 PM|http://www.worldcommunitygrid.org/|Sending scheduler request to https://secure.worldcommunitygrid.org/boinc/wcg_cgi/fcgi 7/7/2006 7:42:56 PM|http://www.worldcommunitygrid.org/|Reason: Requested by user 7/7/2006 7:42:56 PM|http://www.worldcommunitygrid.org/|Requesting 8640 seconds of new work 7/7/2006 7:42:58 PM|http://www.worldcommunitygrid.org/|Scheduler request succeeded 7/7/2006 7:42:58 PM|World Community Grid|General preferences have been updated 7/7/2006 7:42:58 PM||General prefs: from World Community Grid (last modified 2006-07-04 06:25:15) 7/7/2006 7:42:58 PM||General prefs: using your defaults 7/7/2006 7:42:58 PM|World Community Grid|Successfully attached to World Community Grid 7/7/2006 7:43:00 PM|World Community Grid|Started download of file wcg_hpf2_rosetta_5.07_windows_intelx86 7/7/2006 7:43:00 PM|World Community Grid|Started download of file hpf2_5.07_win_paths.txt 7/7/2006 7:43:02 PM|World Community Grid|Finished download of file hpf2_5.07_win_paths.txt 7/7/2006 7:43:02 PM|World Community Grid|Throughput 2408 bytes/sec 7/7/2006 7:43:02 PM|World Community Grid|Started download of file hpf2.avgE_from_pdb.gz 7/7/2006 7:43:12 PM|World Community Grid|Finished download of file hpf2.avgE_from_pdb.gz 7/7/2006 7:43:12 PM|World Community Grid|Throughput 1337 bytes/sec 7/7/2006 7:43:12 PM|World Community Grid|Started download of file hpf2.Paa_n.gz 7/7/2006 7:43:20 PM|World Community Grid|Finished download of file hpf2.Paa_n.gz 7/7/2006 7:43:20 PM|World Community Grid|Throughput 238 bytes/sec 7/7/2006 7:43:20 PM|World Community Grid|Started download of file hpf2.plane_data_table_1015.dat.gz 7/7/2006 7:43:30 PM||Benchmark results: 7/7/2006 7:43:30 PM|| Number of CPUs: 1 7/7/2006 7:43:30 PM|| 781 floating point MIPS (Whetstone) per CPU 7/7/2006 7:43:30 PM|| 1584 integer MIPS (Dhrystone) per CPU 7/7/2006 7:43:30 PM||Finished CPU benchmarks 7/7/2006 7:43:31 PM||Resuming computation 7/7/2006 7:43:31 PM||Rescheduling CPU: Resuming computation 7/7/2006 7:43:45 PM|World Community Grid|Finished download of file hpf2.plane_data_table_1015.dat.gz 7/7/2006 7:43:45 PM|World Community Grid|Throughput 5508 bytes/sec 7/7/2006 7:43:45 PM|World Community Grid|Started download of file hpf2.bbdep02.May.sortlib.gz 7/7/2006 7:51:22 PM|World Community Grid|Finished download of file hpf2.bbdep02.May.sortlib.gz 7/7/2006 7:51:22 PM|World Community Grid|Throughput 12851 bytes/sec 7/7/2006 7:51:22 PM|World Community Grid|Started download of file hpf2.Paa_pp.gz 7/7/2006 7:51:42 PM|World Community Grid|Finished download of file hpf2.Paa_pp.gz 7/7/2006 7:51:42 PM|World Community Grid|Throughput 6333 bytes/sec 7/7/2006 7:51:42 PM|World Community Grid|Started download of file hpf2.Rama_smooth_dyn.dat_ss_6.4.gz 7/7/2006 7:52:23 PM|World Community Grid|Finished download of file hpf2.Rama_smooth_dyn.dat_ss_6.4.gz 7/7/2006 7:52:23 PM|World Community Grid|Throughput 9496 bytes/sec 7/7/2006 7:52:23 PM|World Community Grid|Started download of file hpf2.sasa_prob_cdf.txt.gz 7/7/2006 7:52:38 PM|World Community Grid|Finished download of file hpf2.sasa_prob_cdf.txt.gz 7/7/2006 7:52:38 PM|World Community Grid|Throughput 2536 bytes/sec 7/7/2006 7:52:38 PM|World Community Grid|Started download of file hpf2.paircutoffs.gz 7/7/2006 7:52:46 PM|World Community Grid|Finished download of file hpf2.paircutoffs.gz 7/7/2006 7:52:46 PM|World Community Grid|Throughput 315 bytes/sec 7/7/2006 7:52:46 PM|World Community Grid|Started download of file hpf2.SASA-angles.dat.gz 7/7/2006 7:52:54 PM|World Community Grid|Finished download of file hpf2.SASA-angles.dat.gz 7/7/2006 7:52:54 PM|World Community Grid|Throughput 148 bytes/sec 7/7/2006 7:52:54 PM|World Community Grid|Started download of file hpf2.SASA-masks.dat.gz 7/7/2006 7:53:12 PM|World Community Grid|Finished download of file hpf2.SASA-masks.dat.gz 7/7/2006 7:53:12 PM|World Community Grid|Throughput 3759 bytes/sec 7/7/2006 7:53:12 PM|World Community Grid|Started download of file hpf2.pdbpairstats_fine.gz 7/7/2006 7:53:31 PM|World Community Grid|Finished download of file hpf2.pdbpairstats_fine.gz 7/7/2006 7:53:31 PM|World Community Grid|Throughput 3966 bytes/sec 7/7/2006 7:53:31 PM|World Community Grid|Started download of file hpf2.sasa_offsets.txt.gz 7/7/2006 7:53:39 PM|World Community Grid|Finished download of file hpf2.sasa_offsets.txt.gz 7/7/2006 7:53:39 PM|World Community Grid|Throughput 326 bytes/sec 7/7/2006 7:53:39 PM|World Community Grid|Started download of file hpf2.phi.theta.36.HS.resmooth.gz 7/7/2006 7:53:50 PM|World Community Grid|Finished download of file hpf2.phi.theta.36.HS.resmooth.gz 7/7/2006 7:53:50 PM|World Community Grid|Throughput 1818 bytes/sec 7/7/2006 7:53:50 PM|World Community Grid|Started download of file hpf2.Paa.gz 7/7/2006 7:53:56 PM|World Community Grid|Finished download of file hpf2.Paa.gz 7/7/2006 7:53:56 PM|World Community Grid|Throughput 31 bytes/sec 7/7/2006 7:53:56 PM|World Community Grid|Started download of file hpf2.phi.theta.36.SS.resmooth.gz 7/7/2006 7:54:07 PM|World Community Grid|Finished download of file hpf2.phi.theta.36.SS.resmooth.gz 7/7/2006 7:54:07 PM|World Community Grid|Throughput 1139 bytes/sec 7/7/2006 7:54:07 PM|World Community Grid|Started download of file za098_00880_za098.fasta.gz 7/7/2006 7:54:15 PM|World Community Grid|Finished download of file za098_00880_za098.fasta.gz 7/7/2006 7:54:15 PM|World Community Grid|Throughput 33 bytes/sec 7/7/2006 7:54:15 PM|World Community Grid|Started download of file za098_00880_za098.psipred.gz 7/7/2006 7:54:23 PM|World Community Grid|Finished download of file za098_00880_za098.psipred.gz 7/7/2006 7:54:23 PM|World Community Grid|Throughput 40 bytes/sec 7/7/2006 7:54:23 PM|World Community Grid|Started download of file za098_00880_za098.psipred_ss2.gz 7/7/2006 7:54:28 PM|World Community Grid|Finished download of file wcg_hpf2_rosetta_5.07_windows_intelx86 7/7/2006 7:54:28 PM|World Community Grid|Throughput 17112 bytes/sec 7/7/2006 7:54:28 PM|World Community Grid|Finished download of file za098_00880_za098.psipred_ss2.gz 7/7/2006 7:54:28 PM|World Community Grid|Throughput 370 bytes/sec 7/7/2006 7:54:28 PM|World Community Grid|Started download of file za098_00880_aaza09803_05.075_v1_3.gz 7/7/2006 7:54:28 PM|World Community Grid|Started download of file za098_00880_aaza09809_05.075_v1_3.gz 7/7/2006 7:54:57 PM|World Community Grid|Finished download of file za098_00880_aaza09803_05.075_v1_3.gz 7/7/2006 7:54:57 PM|World Community Grid|Throughput 13093 bytes/sec 7/7/2006 7:55:15 PM|World Community Grid|Finished download of file za098_00880_aaza09809_05.075_v1_3.gz 7/7/2006 7:55:15 PM|World Community Grid|Throughput 18910 bytes/sec 7/7/2006 7:55:16 PM||Rescheduling CPU: files downloaded 7/7/2006 7:55:16 PM|World Community Grid|Starting task za098_00880_4 using hpf2 version 507 7/8/2006 1:38:14 AM|World Community Grid|Unrecoverable error for result za098_00880_4 (The environment is incorrect. (0xa) - exit code 10 (0xa)) 7/8/2006 1:38:14 AM|World Community Grid|Deferring scheduler requests for 1 minutes and 0 seconds 7/8/2006 1:38:14 AM||Rescheduling CPU: application exited 7/8/2006 1:38:14 AM|World Community Grid|Computation for task za098_00880_4 finished7/8/2006 1:39:17 AM|World Community Grid|Sending scheduler request to https://secure.worldcommunitygrid.org/boinc/wcg_cgi/fcgi 7/8/2006 1:39:17 AM|World Community Grid|Reason: To fetch work 7/8/2006 1:39:17 AM|World Community Grid|Requesting 8640 seconds of new work, and reporting 1 completed tasks 7/8/2006 1:39:22 AM|World Community Grid|Scheduler request succeeded 7/8/2006 1:39:24 AM|World Community Grid|Started download of file za099_00329_za099.fasta.gz 7/8/2006 1:39:24 AM|World Community Grid|Started download of file za099_00329_za099.psipred.gz 7/8/2006 1:39:25 AM|World Community Grid|Finished download of file za099_00329_za099.fasta.gz 7/8/2006 1:39:25 AM|World Community Grid|Throughput 399 bytes/sec 7/8/2006 1:39:25 AM|World Community Grid|Finished download of file za099_00329_za099.psipred.gz 7/8/2006 1:39:25 AM|World Community Grid|Throughput 420 bytes/sec 7/8/2006 1:39:25 AM|World Community Grid|Started download of file za099_00329_za099.psipred_ss2.gz 7/8/2006 1:39:25 AM|World Community Grid|Started download of file za099_00329_aaza09903_05.075_v1_3.gz 7/8/2006 1:39:26 AM|World Community Grid|Finished download of file za099_00329_za099.psipred_ss2.gz 7/8/2006 1:39:26 AM|World Community Grid|Throughput 1201 bytes/sec 7/8/2006 1:39:26 AM|World Community Grid|Started download of file za099_00329_aaza09909_05.075_v1_3.gz 7/8/2006 1:39:36 AM|World Community Grid|Finished download of file za099_00329_aaza09903_05.075_v1_3.gz 7/8/2006 1:39:36 AM|World Community Grid|Throughput 23617 bytes/sec 7/8/2006 1:39:57 AM|World Community Grid|Finished download of file za099_00329_aaza09909_05.075_v1_3.gz 7/8/2006 1:39:57 AM|World Community Grid|Throughput 19187 bytes/sec 7/8/2006 1:39:58 AM||Rescheduling CPU: files downloaded 7/8/2006 1:39:59 AM|World Community Grid|Starting task za099_00329_0 using hpf2 version 507 |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
OH, and thanks to all for explaining the Pending status. Yeah, it makes sense that I would have to wait until another machine completes the same work unit. I hear Homer Simpson in my head.... "DoH!"
 |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Hi Enlightenedpoint,
----------------------------------------The log is not giving away alot on the error, but reading it top to bottom, looks either like a new install or a project reset/reattach, then retrieval of a HPF2 version 5.075, a crunch of 5:43 hours, then bombing followed by a download of a new WU (work Unit), which is immediately crunched. The fact that the second unit needed to be downloaded immediately , then commenced for crunching, suggests that in percent terms the WU had not progressed enough for BOINC to signal a pre-fetch of a work unit. BOINC by default schedules a server contact every 2.4 hours. What i'm saying is, that if BOINC knew there was still say 10 hours to crunch, it would not go and collect a new WU. It waits till closer to finish time of current WU. That ensures u get a WU as fresh as it can get. Don't know what timezone u r in (plz put your country in your forum profile plz), but given that its been working on the 2nd WU since 1:39am your time it looks like its okay.....you're awake and writing here, so presume its saturday after breakfast pancakes. The "exit code 10 (OxA)" error has also been reported by others in discussions like A few unusual HPF2 work units. Cant though locate what it means. There error data is send back to WCG, so once that is analysed, it will help to make amends to the next rosetta version. Just keep crunching and advise on re-occurance.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 3 times, last edit by Sekerob at Jul 8, 2006 5:10:53 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I am located in Phoenix, AZ USA. We are currently on Mountain time, no daylight savings so I share time with Pacific Time zone right now. The machine in question, however, is actually in Colorado so it's on actual Mountain time zone.
Thanks to all for the feedback. I will continue to watch that machine closely (I have remote access to it so that's the easy part). So, between BOINC and the UD client, which is the "better", factoring in performance, reliability, etc? I had PAINFUL experiences with the UD.com stuff and it's essentially the same client AND back end systems so I was actually quite uneasy at first signing up for WCG since it looked like the same stuff. Thanks! -John |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I've said it before, and I'll say it again: I prefer BOINC. This is partly because it has a few features that UD doesn't, but mostly because it is entirely transparent - when things go wrong, you can look into the issue to whatever depth you need. Viva Open Source!
But the main difference between WCG and other crunching projects has to be the people. WCG have a whole team working tirelessly to improve the grid, and keep it humming along. They work with some great scientists, and they have stringent rules for approving projects to run on the grid. And finally, they have their members (and the CAs) to keep them honest, and to bring to their attention things that need fixing. Now, this error code - actually, it has appeared (rarely) on entirely unrelated BOINC projects. I think it's a new one for WCG. We'll have to wait for the verdict from the techs. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The UD project is a joke. I've posted on their forum so many times about data integrity issues.... any reputable researcher would be foolish to take their data as anything but tainted. Their systems have had so many problems and there's been so much "data loss" that it seems hopeless. I donated 11 years of CPU time before I had finally reached my limit.
So far, WCG has impressed me. Heck, having stats RUN is new compared to UD. Having it run multiple times per day? Amazing. I'm happy |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The invalid results were probably caused by the transition from HPF2 5.06->5.07. While that was certainly true in the first few days after the switch on 6/28, I'm still seeing about one third of my results turn out to be invalid even for fresh units just issued in the past few days (which would all be using 5.07). I think the Inconclusives and Invalids we're still seeing now are probably caused by getting slightly different results on different platforms. Since I run XP, I have a good chance of the eventual quorum agreeing with me, so the majority of my results end up Valid. I'd be curious to see the Valid/Invalid ratio of a minority system; if I'm right, the less common machines will be having a harder time getting their results voted Valid. |
||
|
|
|