Problem with Project: 6511 (Run 7, Clone 16, Gen 34)

Moderators: Site Moderators, FAHC Science Team

Post Reply
The_Celt
Posts: 20
Joined: Sat Jan 26, 2008 7:29 pm

Problem with Project: 6511 (Run 7, Clone 16, Gen 34)

Post by The_Celt »

Hi. I am having a proble with Project: 6511 (Run 7, Clone 16, Gen 34)
Every time I delete the queue and work folder and restart, the same WU is downloaded again and errors out with this:

Code: Select all

[12:01:38] Trying to send all finished work units
[12:01:38] + No unsent completed units remaining.
[12:01:38] - Autosend completed
[12:01:38] Posted data.
[12:01:38] Initial: 40AB; - Successful: assigned to (171.64.65.62).
[12:01:38] + News From Folding@Home: Welcome to Folding@Home
[12:01:39] Loaded queue successfully.
[12:01:39] Connecting to http://171.64.65.62:8080/
[12:01:39] Posted data.
[12:01:39] Initial: 0000; - Receiving payload (expected size: 749031)
[12:01:41] - Downloaded at ~365 kB/s
[12:01:41] - Averaged speed for that direction ~365 kB/s
[12:01:41] + Received work.
[12:01:41] + Closed connections
[12:01:41] 
[12:01:41] + Processing work unit
[12:01:41] Core required: FahCore_78.exe
[12:01:41] Core found.
[12:01:41] Working on queue slot 01 [April 2 12:01:41 UTC]
[12:01:41] + Working ...
[12:01:41] - Calling '.\FahCore_78.exe -dir work/ -suffix 01 -checkpoint 15 -service -verbose -lifeline 4040 -version 620'

[12:01:41] 
[12:01:41] *------------------------------*
[12:01:41] Folding@Home Gromacs Core
[12:01:41] Version 1.90 (March 8, 2006)
[12:01:41] 
[12:01:41] Preparing to commence simulation
[12:01:41] - Looking at optimizations...
[12:01:41] - Created dyn
[12:01:41] - Files status OK
[12:01:43] - Expanded 748519 -> 3743169 (decompressed 500.0 percent)
[12:01:43] - Starting from initial work packet
[12:01:43] 
[12:01:43] Project: 6511 (Run 7, Clone 16, Gen 34)
[12:01:43] 
[12:01:43] Assembly optimizations on if available.
[12:01:43] Entering M.D.
[12:01:49] Gromacs error.
[12:01:49] 
[12:01:49] Folding@home Core Shutdown: UNKNOWN_ERROR
[12:01:52] CoreStatus = 79 (121)
[12:01:52] Client-core communications error: ERROR 0x79
[12:01:52] This is a sign of more serious problems, shutting down.
I even tried to delete the core, it redownloaded, same problem. This is a two CPU system, P III x2 1 GHz (Yeah - its old) and it is not overclocked.
The other fah client is currently working on Project: 6521 (Run 5, Clone 58, Gen 43) with no problems.

Thanks.
HendricksSA
Posts: 336
Joined: Fri Jun 26, 2009 4:34 am

Re: Problem with Project: 6511 (Run 7, Clone 16, Gen 34)

Post by HendricksSA »

The PantherX guide to problems with work units should get you going. You can find it at: viewtopic.php?f=19&t=16526

It may not help us solve this problem with this work unit. If this computer normally runs work units without problems, then the steps you tried plus changing your machine ID to a unique value should get you a new work unit. However, while you have the client stopped I would suggest you update to the newest version. You are currently running 6.20 and 6.23 is the latest.

Let us know how it goes.
The_Celt
Posts: 20
Joined: Sat Jan 26, 2008 7:29 pm

Re: Problem with Project: 6511 (Run 7, Clone 16, Gen 34)

Post by The_Celt »

HendricksSA, I did upgrade my client to 6.23, and deleted the work files again. This time the new client noticed the crash, and then downloaded a new WU without my intervention. Thanks, I hadn't noticed I was using an old client.
toTOW
Site Moderator
Posts: 6359
Joined: Sun Dec 02, 2007 10:38 am
Location: Bordeaux, France
Contact:

Re: Problem with Project: 6511 (Run 7, Clone 16, Gen 34)

Post by toTOW »

For the time being, there's no data for Project: 6511 (Run 7, Clone 16, Gen 34) in the stats DB which means no one has been able to return results yet :(
Image

Folding@Home beta tester since 2002. Folding Forum moderator since July 2008.
sortofageek
Site Admin
Posts: 3110
Joined: Fri Nov 30, 2007 8:06 pm
Location: Team Helix
Contact:

Re: Problem with Project: 6511 (Run 7, Clone 16, Gen 34)

Post by sortofageek »

The WU (P6511,R7,C16,G34) has been reported as a bad WU.
Post Reply