While a progress of an unit reached 100% on my BOINC client, strangely it continues to work, and % of completed on the graphic keeps less than 100%, approximately 57%.
(here you can see a screen shot of it.) And I continue to work on the unit several minutes, but it remains at the same percentage.

Is this bug or not? thanks,

I think this is related to the phenomenon Mike Gelvin was reporting that some WU remain dormant after showing 100%. Perhaps you can check the task manager for the next WU.

---

Instant failure, no graphics displayed but two preempted WU from Rosetta in mem:
https://ralph.bakerlab.org/result.php?resultid=145667

Have two more of those WU, will watch them closely.

How can I turn debug-information on?

---

Instant failure, no graphics displayed but two preempted WU from Rosetta in mem:
https://ralph.bakerlab.org/result.php?resultid=145667

Have two more of those WU, will watch them closely.

How can I turn debug-information on?

The next two WUs failed as well with the same error code after the same time (6sec):

https://ralph.bakerlab.org/result.php?resultid=145641
https://ralph.bakerlab.org/result.php?resultid=145639

---

While a progress of an unit reached 100% on my BOINC client, strangely it continues to work, and % of completed on the graphic keeps less than 100%, approximately 57%.
(here you can see a screen shot of it.) And I continue to work on the unit several minutes, but it remains at the same percentage.

Is this bug or not? thanks,

I think this is related to the phenomenon Mike Gelvin was reporting that some WU remain dormant after showing 100%. Perhaps you can check the task manager for the next WU.

I can confirm this bug reported from suguruhirahara and Mike Gelvin. This WU:
https://ralph.bakerlab.org/result.php?resultid=145529

finished after 54 minutes and BOINC reported 100% but still running and in the task manager 0% CPU-ulilization was reported. This lasted for about 5 minutes until it finished. I checked the screensaver and the progress was 89% and it was shown that it had started a 4th model but which in fact seemed not to be calculated. Here is the screenshot

---

Instant failure, no graphics displayed but two preempted WU from Rosetta in mem:
https://ralph.bakerlab.org/result.php?resultid=145667

Have two more of those WU, will watch them closely.

How can I turn debug-information on?

The next two WUs failed as well with the same error code after the same time (6sec):

https://ralph.bakerlab.org/result.php?resultid=145641
https://ralph.bakerlab.org/result.php?resultid=145639

I got the same kind of error over whole fetched workunits such as,
https://ralph.bakerlab.org/result.php?resultid=145741
https://ralph.bakerlab.org/result.php?resultid=145770

Just re-attached to project, 3 WU's failed after 12 secs.

BOINCLogX reports Incorrect function. (0x1) - exit code 1 (0x1); ERROR:: Exit at: .barcode_classes.cc line:500

WTBroughton
BOINC in Northumberland

---

All WUs I tried crashed within the first seconds.


Unrecoverable error for result t296__CASP7_ABINITIO_SAVE_ALL_OUT_nterm_hom009__612_6_0 (Unzulässige Funktion. (0x1) - exit code 1 (0x1))

Unrecoverable error for result t296__CASP7_ABINITIO_SAVE_ALL_OUT_cterm_hom017__610_9_0 (Unzulässige Funktion. (0x1) - exit code 1 (0x1))

Unrecoverable error for result t296__CASP7_ABINITIO_SAVE_ALL_OUT_cterm_hom001__610_3_1 (Unzulässige Funktion. (0x1) - exit code 1 (0x1))

Unrecoverable error for result t296__CASP7_ABINITIO_SAVE_ALL_OUT_cterm_hom001__612_10_0 (Unzulässige Funktion. (0x1) - exit code 1 (0x1))

---

I confirm earlier reported error out condition:

Incorrect function. (0x1) - exit code 1 (0x1); ERROR:: Exit at: .barcode_classes.cc line:500

in these two work units:

146315
145904

AND

after observing several more dormant cases, I conclude that the application goes dormant until the wall clock time reaches an even hour after the app starts before terminating "normally". This time is TO THE SECOND. This is independent of the CPU time taken.

---

I received 12 WUs using 5.19. Eleven t296__CASP7_ABINITIO_* and one t299__CASP7_ABRELAX. The ABRELAX is running fine (was able to suspend/resume with no problems), but all of the ABINITIOs errored out during initialization.

For the ABINITIOS:
<core_client_version>5.4.9</core_client_version>
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# cpu_run_time_pref: 3600
ERROR:: Exit at: .barcode_classes.cc line:500

</stderr_txt>



Huh. While I was watching the ABRELAX, it whizzed along to step 340000, seemed to pause for a bit, and is now moving very slowly. And the "to completion time" keeps increasing. CPU keeps working, though.

Update: At 40 min (66.6% completion according to the graphic, 100% by the client), the ABRELAX unit seems to have gone dormant. Stopped at step 340539 in stage 2, not using any CPU. I'll keep an eye on it to see if/when it resumes.

Update2: Or...it really was finished? It exited with no problems and is valid. Never mind about that one then.

---

Rosetta_beta 5.19 Windows

Exit status 1 (0x1)

Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
ERROR:: Exit at: .barcode_classes.cc line:500


https://ralph.bakerlab.org/result.php?resultid=146649
https://ralph.bakerlab.org/result.php?resultid=146648

---

Click signature for global team stats

Ditto, same error shown in this result.

Errored out immediately (cpu = 14 seconds) with the exit code 1 @ barcode_classes.cc line:500

app is 5.19, client 5.4.9, windows XPsp2

Thanks for posting about this! I've fixed the problem, and I'm sending out the workunit again.

Ditto, same error shown in this result.

Errored out immediately (cpu = 14 seconds) with the exit code 1 @ barcode_classes.cc line:500

app is 5.19, client 5.4.9, windows XPsp2

---

Hi: this behavior occurs for some work units (the ones with "RELAX" in the name). They should end up completing if you wait an hour. If the workunit is going beyond four times your preference (4x1 hours on ralph by default; 4x3 hours on rosetta@home by default), go ahead and abort it. I've been paying close attention to WU's on my powerbook (Mac OS 10.4.2) -- the simulations do run slower on a Mac than on Windows (for now), but I've never seen a workunit totally get stuck.

rosetta_beta version 518
WU Name: JUMP_RELAX_3142__t285__SAVE_ALL_OUT_594_22_0
running on Mac OS 10.4.6

BOINC Manager Tasks tab shows CPU Time stuck at 08:53:24 and 70%
top command shows TIME = 36:04:48 and climbing

stopped and restarted BOINC
CPU Time reverted to 05:35:00 and 70% but no longer stuck

---

got some interesting 5.19 stuff too, was not infront of my pc to see it happen mostly though.
the first result took less than 2 hours (my ralph preference) to run according to the resultpage, in realtime it took almost exactly 2 hours to run.
next result took just a little less than 2 hours of processing time looking at the result page, but took in fact 3 hours realtime.
the third result took almost exactly 2 hours on the result page, but consumed 3 hours of realtime too.
fourth was a little more complicated, it was running for 3 hours when it got preempted, cputime in the boincmanager was showing 1:59:07, the grahpics the same cpu time, 99.2% in the graphics, but 100% in boincmanager. upon being resumed it instantly completed.
last i got ended with incorrect function right at the start. result

I think I found the problem causing the missing/broken graphic!!!!


I am right now running following wu
FRA_t301_hom029_1_LOOPRLX_IGNORE_THE_REST__hom029_1_1bwzA__100_627_5_0 using rosetta_beta version 519

It didn't display ANY of the three graphic... I played around with the mouse and suddenly got some graphic in the low energy window!

I can rotate it with the mouse, so that it is completely rotated out of the window, and i can zoom it that big, that parts of the graphic are missing!!!

As you can see on the third picture, the both other graphs have the same problem!

I think, it is just the rotation center point that must be placed in the center of the model... Seems currently to be much behind the model....

That would also fix the broken graph:
Parts of the graphic vanish, because the model moves "out" of the display spa ce!

Let me know if my poor english explanation did point the problem out, or if you have further questions!

Update1: later in this model, the error vanishes, I think because the graphics change in a way that fixes the center point..

---

I ran into one of those 'stuck' abrelax wu's overnite:
resid 144202
running ralph 5.19 on my P-M laptop. It showed 100% done at 3:14:58 CPU time, but no activity, screensaver wouldn't come up (blank area only), task manager showed all cycles going to System Idle Process. Suspended acty and re-started Boinc, no-joy. Closed BM and re-started machine, brought it back up, no-joy. Aborted the WU and BM went right back to work. Didn't want to wait ?16hrs? (4x4) to see if it would somehow wake-up and finish on its own!

The wu mentioned below did show the same behaviour:

BOINC reported 100%, GUI about 98! No CPU-usage!

Had a similar problem with some HashClash units, maybe it is a problem of the
BOINC 5.4.9 client..?

---

I ran into one of those 'stuck' abrelax wu's overnite:
resid 144202
running ralph 5.19 on my P-M laptop. It showed 100% done at 3:14:58 CPU time, but no activity, screensaver wouldn't come up (blank area only), task manager showed all cycles going to System Idle Process. Suspended acty and re-started Boinc, no-joy. Closed BM and re-started machine, brought it back up, no-joy. Aborted the WU and BM went right back to work. Didn't want to wait ?16hrs? (4x4) to see if it would somehow wake-up and finish on its own!

My experiance with this is that it will always finish within one hour of getting into this mode. If you look at the messages, and see when the WU started, take the minutes and seconds portion (like 5:10:20). When your PC time (wall time) reaches the same minutes and seconds (like 7:10:20), the work unit will complete. I know its weird, but thats what I am seeing.

Mike

---

thats definetley something that has to be fixed before it goes out on the main project. out of the 4 5.19 units that i completed succesfully (2 hour pref) 3 wasted 1 hour that could have been used elsewhere, and the 4th used at least a couple of extra minutes to reach the 2 hour mark.

I ran into one of those 'stuck' abrelax wu's overnite:
resid 144202
running ralph 5.19 on my P-M laptop. It showed 100% done at 3:14:58 CPU time, but no activity, screensaver wouldn't come up (blank area only), task manager showed all cycles going to System Idle Process. Suspended acty and re-started Boinc, no-joy. Closed BM and re-started machine, brought it back up, no-joy. Aborted the WU and BM went right back to work. Didn't want to wait ?16hrs? (4x4) to see if it would somehow wake-up and finish on its own!

My experiance with this is that it will always finish within one hour of getting into this mode. If you look at the messages, and see when the WU started, take the minutes and seconds portion (like 5:10:20). When your PC time (wall time) reaches the same minutes and seconds (like 7:10:20), the work unit will complete. I know its weird, but thats what I am seeing.

Mike

Yes, this is really weird.

I have one stuck right now: https://ralph.bakerlab.org/workunit.php?wuid=129926

I took this screendump of the BOINC Manager: http://img.photobucket.com/albums/v680/lsh55/Setiweb/Ralph/BOINC_Mgr_Ralph.jpg


And this is the graphic: http://img.photobucket.com/albums/v680/lsh55/Setiweb/Ralph/RalphWU.jpg

This is really weird, the screen is rolling very fast to the left and this "band" is showing at the bottom of the screen.


I'll leave it as it is and see if it will finish as you say at the minute. Else I'll abort it.

---

[color=navy][b]"I'm trying to maintain a shred of dignity in this world." - Me[/b][/color]