Help!

S

sl1982

Limp Gawd
Joined
Jul 24, 2008
Messages
365
Anyone know what this means / how to fix it?

[00:09:48] Completed 500000 out of 500000 steps (100 percent)
[00:09:48] Writing final coordinates.
[00:09:48] Past main M.D. loop
[00:09:48] Will end MPI now
[00:10:48]
[00:10:48] Finished Work Unit:
[00:10:48] - Reading up to 3722496 from "work/wudata_04.arc": Read 3722496
[00:10:48] - Reading up to 1778096 from "work/wudata_04.xtc": Read 1778096
[00:10:48] goefile size: 0
[00:10:48] logfile size: 17315
[00:10:48] Leaving Run
[00:10:51] - Writing 5522307 bytes of core data to disk...
[00:10:51] ... Done.
[00:10:51] - Failed to delete work/wudata_04.sas
[00:10:51] - Failed to delete work/wudata_04.goe
[00:10:51] Warning: check for stray files
[00:10:51] - Shutting down core
[00:12:51]
[00:12:51] Folding@home Core Shutdown: FINISHED_UNIT
[00:12:51]
[00:12:51] Folding@home Core Shutdown: FINISHED_UNIT
[00:12:56] CoreStatus = 7B (123)
[00:12:56] Client-core communications error: ERROR 0x7b
[00:12:56] This is a sign of more serious problems, shutting down.
 
Unfortunately your SMP client coughed up a hairball while trying to close out at the end of the run. Not all that uncommon. If you haven't tried kicking the client to see if it uploads on restart, try it. Otherwise I think your only option is to try and Qfix it and upload the result that way.

I haven't had to do that while running the SMP client though and am not really sure what is involved. I'm sure someone familiar with Qfix will check in on this though... ;)



 
Not really familiar with qfix but i ran it and it said the file was ok. Tried to force it to send the results but no dice. Oh well. No points for me today :(
 
Ah awesome. Just restarted and got this.

[05:07:34] - Going to use standard loops.
[05:07:34] - Files status OK
[05:07:45] SSING_WORK_FILES
[05:07:45] Finalizing output
[05:07:52] G_WORK_FILES
[05:07:52] Finalizing output
[05:09:54] CoreStatus = 1 (1)
[05:09:54] Client-core communications error: ERROR 0x1
[05:09:54] This is a sign of more serious problems, shutting down.

Fahwiki says error 0x1 is an unknown error
 
Didnt work. This is what qfix says.

entry 4, status 1, address 171.64.65.64:8080
Found results <work\wu_results.dat>: proj 2653, run 36, clone 7, gen 87
-- queue entry: proj 2653, run 36, clone 7, gen 87
-- queue entry isn't empty
File is OK
 
yeah. It says attempting to send results and then says Folding@Home client shutdown. Doesnt mention that it sent files or not. And if it did it must have been instantaneous.
 
no it didn't send it..hmm wonder if that server is down?
checked and it looks up
Anyone else have any ideas?
 
gah i dunno. nothing but problems these days. it sucks considering i bought that boxen for basically purely folding and all this work is for nothing
 
I hear ya..Sorry I'm out of ideas. Hopefully someone else comes up with something.
Does you Fahspy say Ready to Send?
If it does maybe during or the end of your next wu it will send it in.
 
Ok well how about getting rid of this bad unit so I can go back to folding?
 
Sorry missed that. Guess it bye bye baby. Fold on.
I'd look into as to the possable reason that happend so it doesn't happen at the end of your next wu.
Good luck.
 
I'd delete all in work folder and your queue.dat and unitinfo.txt then restart client
 
I just unistalled / deleted the whole client. I gave the deino client a go. Hopefully it works a little better
 
I've personally had better luck with MPICH than Denio. I hope it works for you though. Both clients are honestly unstable. Mine were working great for ages, then today I had 2 do the same thing and I couldn't fix them either. I had to dump 2 finished units because it refused to upload them. Gotta love losing 2x1920 points.
 
I feel your pain. At least its not just me though. All my research on the error codes pointed towards an unstable machine which doesnt make sense as everything is running at stock speeds and my temperatures are decent.
 
sl1982 said:
All my research on the error codes pointed towards an unstable client/WU which makes sense as everything is running at stock speeds and my temperatures are decent.
Click to expand...

Fixt...


 
He's telling you that it's the client and WUs that are causing the problem, not the computer. It says in their FAQ that it COULD be an unstable machine, but that is BS 99% of the time. I've never had one crash because of an overclock, because none of my machines have the processors overclocked. I have had several bad WUs though. Just had one crash and give a weird error 2 days ago.
 
Ah. Lol makes sense now. Damn stanford making me think my shiny new rig is garbage :mad:
 
You must log in or register to reply here.
Back
Top