Search found 13 matches

by arfyness
Sat Oct 18, 2008 7:52 am
Forum: 3rd party contributed software
Topic: Sample SysV Init Script for fah6 (Recyclable, too!)
Replies: 1
Views: 2010

Sample SysV Init Script for fah6 (Recyclable, too!)

I've been messing with this for a while, and now it looks stable enough to share without much embarrasment. :o) You'll have to change the variables at the top of the file to match your system. My system configuration has it running under my username nate in a working directory /usr/local/folding ......
by arfyness
Sun Sep 07, 2008 11:18 pm
Forum: Issues with a specific WU
Topic: 2170 (Run 58, Clone 427, Gen 5) - CoreStatus = 75 (117)
Replies: 4
Views: 932

Re: 2170 (Run 58, Clone 427, Gen 5) - CoreStatus = 75 (117)

Where is this database? Is it publicly accessible?

-- Nate
by arfyness
Sat Sep 06, 2008 11:02 pm
Forum: Issues with a specific WU
Topic: Is this right? [Project: 2665 (Run 2, Clone 343, Gen 37)]
Replies: 6
Views: 1089

Re: Is this right?

Ancient_Dragon: Post back if this happens again. There is also a separate board Issues with a specific WU for repeated problems with the same work unit ... In your case, look for "Project: 2665 (Run 2, Clone 343, Gen 37)" if you have any future errors.

-- Nate
by arfyness
Sat Sep 06, 2008 10:50 pm
Forum: Issues with a specific WU
Topic: 782 (Run 0, Clone 77, Gen 3) - Gives ERROR 0x79's - Core a0
Replies: 8
Views: 1173

Re: 782 (Run 0, Clone 77, Gen 3) - Gives ERROR 0x79's - Core a0

I tried different combinations of big/small/normal, with different memory reporting (64mb is the minimum, i found out). Finally I disabled -advmethods and it couldn't find any work to do (normal / 220mb). After a while, it's using core 82 on project 2170 (which I can't find any info about). We'll se...
by arfyness
Sat Sep 06, 2008 10:42 pm
Forum: Issues with a specific WU
Topic: Project 5113
Replies: 16
Views: 2826

Re: Project 5113

In my limited experience, any error caused by overclocking has affected the whole system. For example, blue screen, kernel panic, system hang, sudden poweroff, etc. It's my assumption that our difficulties with these projects (in my case 781) are not due to hardware. It's probably a good thing I ca...
by arfyness
Thu Sep 04, 2008 9:06 pm
Forum: Issues with a specific WU
Topic: 782 (Run 0, Clone 77, Gen 3) - Gives ERROR 0x79's - Core a0
Replies: 8
Views: 1173

Re: 782 (Run 0, Clone 77, Gen 3) - Gives ERROR 0x79's - Core a0

I have a uniprocessor machine ... Is there a different (previous?) Linux uniprocessor version of the client that I might try? I keep getting assigned work units for the mini-chaperonin projects 781 and 782 (core a0)... and they have failed every single time, usually with ERROR 0x79 and sometimes wit...
by arfyness
Wed Sep 03, 2008 10:55 pm
Forum: Issues with a specific WU
Topic: 782 (Run 0, Clone 77, Gen 3) - Gives ERROR 0x79's - Core a0
Replies: 8
Views: 1173

782 (Run 0, Clone 77, Gen 3) - Gives ERROR 0x79's - Core a0

So, I've got two more errors since I went to bed last night... Still on the same work unit. This machine has been folding for almost 3 weeks, and still has not submitted a work unit yet. They always fail. Before my trouble was with project 781 , which seems to be a similar simulation, using the same...
by arfyness
Mon Sep 01, 2008 3:09 pm
Forum: Issues with a specific WU
Topic: Project 5113
Replies: 16
Views: 2826

Re: Project 5113

In my limited experience, any error caused by overclocking has affected the whole system. For example, blue screen, kernel panic, system hang, sudden poweroff, etc. It's my assumption that our difficulties with these projects (in my case 781) are not due to hardware. It's probably a good thing I can...
by arfyness
Mon Sep 01, 2008 2:55 pm
Forum: Issues with a specific WU
Topic: Project 781 -- FahCore_a0.exe ERRORs -- Deletes WUs
Replies: 2
Views: 691

Re: Project 781 -- FahCore_a0.exe ERRORs -- Deletes WUs

Well, okay. that was fast, Crashed again with ERROR 0x0 [08:14:51] Completed 115000 out of 500000 steps (23 percent) [09:32:58] Writing local files [09:32:58] Completed 120000 out of 500000 steps (24 percent) [09:38:29] CoreStatus = 0 (0) [09:38:29] Client-core communications error: ERROR 0x0 [09:38...
by arfyness
Mon Sep 01, 2008 5:48 am
Forum: Issues with a specific WU
Topic: Project 781 -- FahCore_a0.exe ERRORs -- Deletes WUs
Replies: 2
Views: 691

Re: Project 781 -- FahCore_a0.exe ERRORs -- Deletes WUs

UPDATE: I'm not sure if this will have any effect whatsoever, but it crossed my mind to delete all the core FahCore_a0.exe so that it'll have to download the latest core, in case anything has changed. I have seen the notes about the A2 core. Of course, I stopped the client, deleted it, and restarted...
by arfyness
Mon Sep 01, 2008 4:43 am
Forum: Issues with a specific WU
Topic: Project: 2665 (Run 0, Clone 479, Gen 20)
Replies: 15
Views: 2390

Re: Project: 2665 (Run 0, Clone 479, Gen 20)

Have y'all tried running one instance per core? I ask cause I'm curious whether the Linux 6.02 client will work that way. That's what I do on my mom's winxp dual core anyway, with the 6.20 console/service version. It works fine. But that's in Windows, which sadly still seems to have higher priority....
by arfyness
Mon Sep 01, 2008 3:52 am
Forum: Issues with a specific WU
Topic: Project 781 -- FahCore_a0.exe ERRORs -- Deletes WUs
Replies: 2
Views: 691

Project 781 -- FahCore_a0.exe ERRORs -- Deletes WUs

I'm not sure what's going on here, but I have yet to successfully submit a work unit on my Ubuntu 8.04.1 machine. To the point - pasted below the asterisks (and below the config stuff) are the errors I've been getting on every single work unit on the Gromacs 3.3 core (FahCore_a0.exe). I am using the...
by arfyness
Mon Sep 01, 2008 3:46 am
Forum: Issues with a specific WU
Topic: Project 5113
Replies: 16
Views: 2826

Re: Project 5113

I've had a similar situation several times with this same core, but with Project 781. In my case, the errors are different. Several occasions of ERROR 0x0 and a couple others, including "NaN detected" My post is here Maybe it's something with these projects, or maybe we've found a bug in t...