Project: 2665 (Run 2, Clone 300, Gen 37)

[ChelseaOilman]

Code: Select all

[05:37:24] Project: 2665 (Run 2, Clone 300, Gen 37)
[05:37:24] 
[05:37:29] Assembly optimizations on if available.
[05:37:29] Entering M.D.
[05:37:35] Rejecting checkpoint
[05:37:37] Protein: HGG with glycosylations
[05:37:37] Writing local files
[05:37:45] Extra SSE boost OK.
[05:37:46] Writing local files
[05:37:46] Completed 0 out of 250000 steps  (0 percent)
[05:47:56] 
[05:47:56] - Writing 9957 bytes of core daGromacs cannot continue fu- Failed to delete work/wudata_04.sas
[05:47:56] - Failed to delete work/wudata_04.goe
[05:47:56] Warning:  check for stray files
[05:47:56] ... Done.
[05:47:56] - Failed to delete work/wudata_04.arc
[05:47:56] - Failed to delete work/wudata_04.sas
[05:47:56] - Failed to delete work/wudata_04.goe
[05:47:56] Warning:  check for stray files
[05:47:56] @home Core Shutdown: EARLY_UNIT_END
[05:47:56] Finalizing output
[05:49:56] ome Core Shutdown: EARLY_UNIT_END
[05:49:59] CoreStatus = 7B (123)
[05:49:59] Client-core communications error: ERROR 0x7b
[05:49:59] This is a sign of more serious problems, shutting down.

My client didn't upload anything to the WU database. I see three other people were able to upload something.

Your WU (P2665 R2 C300 G37) was added to the stats database on 2008-08-05 08:38:24 for 10.84 points of credit.

Your WU (P2665 R2 C300 G37) was added to the stats database on 2008-08-06 18:37:00 for 11.82 points of credit.

Your WU (P2665 R2 C300 G37) was added to the stats database on 2008-08-07 02:36:04 for 0 points of credit.

[MtM]

What client where you running?

[ChelseaOilman]

What client where you running?

This one: Folding@Home Client Version 6.22 SMP Beta2

The last line in my log was the clue: "This is a sign of more serious problems, shutting down."

This WU got me in an EUE loop that I could only get out of by deleting my User ID in the registry.

[MtM]

Well I'm abit confused to see this thread then as some of my forum members took a post from VJ concerning that error and the 6.22 client earlier today as a reason to downgrade to 5.91. So I'm prety stumped to see you report another simular issue while still on the new client as it seems to me as a known issue which already has an official stance? Or am I wrong? I was already abit stumped about the roll back advice as to me it wasn't very clear what issues VJ was actually adressing with it. Both the 0x7b and the upload issue where mentioned in that thread, like I said I'm abit unsure about how I'm seeing all this but to me it's pretty vague.

Apologies if my questions/concerns are totally wrong.

[ChelseaOilman]

I was just reporting the "Issues with a specific WU" I had, and the fact that three other people seemed to have issues with this WU as well. I don't know which client they were using. Maybe they got further because they were using 5.91, or 5.92.

Reverting to the older clients isn't a bad idea if you can't monitor the 6.22 SMP client closely. I lost over 10 hours processing time to this WU due to the new client stopping and waiting for me to acknowledge the error message.