Folding Forum

Hello,

This is my first post here.

I've been running F@H for a while now. Usually, I just click it on, and forget it... and go about my daily routine, on my computer. Been doing this for months now, with no problems.

I noticed that the CPU temp was not rising, as it usually does, when I turn Folding on. So I began to look around.

Found that it seems to be stuck in a loop. If I open the log, it is always ending like this:

16:58:39] Digital signatures verified
[16:58:39] Completed 0 out of 499375 steps (0%)
[16:58:39] Completed 5000 out of 499375 steps (1%)
[16:58:39] Completed 10000 out of 499375 steps (2%)
[16:58:39] Pausing core


If I scroll back up the log a bit, I find that it has been happening over and over, and continues like this:

16:58:19] Reading tar file core.xml
[16:58:19] Digital signatures verified
[16:58:19] Completed 0 out of 499375 steps (0%)
[16:58:19] Completed 5000 out of 499375 steps (1%)
[16:58:19] Completed 10000 out of 499375 steps (2%)
[16:58:19] Pausing core
[16:58:39] CoreStatus = 62 (98)
[16:58:39] + Restarting core (settings changed)
[16:58:39]
[16:58:39] + Processing work unit
[16:58:39] Core required: FahCore_b4.exe
[16:58:39] Core found.
[16:58:39] Working on queue slot 04 [October 6 16:58:39 UTC]
[16:58:39] + Working ...
[16:58:39] *********************** Log Started 05/Oct/2010 18:41:43 ***********************
[16:58:39] ************************** ProtoMol Folding@Home Core *************************
...
.....


I assume you need more info from me, to be able to help diagnose and tell me what to do to fix it.
Ask, and direct me, and I'll try to get whatever you need, and post it here.


Thank you

Is it the same work unit?

Delete the work folder, queue.dat and info files and the restart the client.

Computer/CPU, OS, and F@H client version would be a good start for info. Also, a lot of valuable info is in the beginning of the log, so post that as well. Use tags around the log entry to help with formatting here.

In the mean time, you may want to try initializing the client from scratch. Close the client. Delete the queue.dat, unitinfo.txt, client.cfg, and any fahcore files, and the \work folder. Restart the client, and it will go into the config screens. Set up your username and team number as desired, and go into the advanced menu. Add -verbosity 9 as a parameter in the last entry so we get more log info. When it starts, it should download a new core and work unit.

Is there a quote function, for use when replying?


"Is it the same work unit?"
I don't know.


"Delete the work folder, queue.dat and info files and the restart bthe client."
Where do I find the work folder and queue.dat and info files?
What is the restart bthe client, and where is it?


Thanks

Hello Willyw, welcome to the forum.

Yes, there are quoting options. There is a Quote button to quote the whole post, or you can copy and paste a a part, and then use the [quote][/quote] tags. Tags are on the preview page.

Those files are in the same place as the fahlog.txt file. Same folder where you installed the client. The graphical client installes to C:\program files\Folding@home\

jrweiss wrote:Computer/CPU, OS,

Computer = homebrew
CPU = AMD Athlon II 3.0 Ghz
OS = Windows 7 x64

and F@H client version

Where do I get it?

would be a good start for info. Also, a lot of valuable info is in the beginning of the log, so post that as well. Use

Code: Select all

tags around the log entry to help with formatting here.

Code: Select all

--- Opening Log file [October 6 17:21:17 UTC] 


# Windows CPU Systray Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

###############################################################################
###############################################################################

Launch directory: C:\Users\*********\AppData\Roaming\Folding@home-x86


[17:21:17] - Ask before connecting: Yes
[17:21:17] - User name: Willyw (Team 171165)
[17:21:17] - User ID: 18F0F5CF6F00C9DA
[17:21:17] - Machine ID: 1
[17:21:17] 
[17:21:17] Loaded queue successfully.
[17:21:17] Initialization complete
[17:21:17] 
[17:21:17] + Processing work unit
[17:21:17] Core required: FahCore_b4.exe
[17:21:17] Core found.
[17:21:17] Working on queue slot 04 [October 6 17:21:17 UTC]
[17:21:17] + Working ...
[17:21:17] *********************** Log Started 05/Oct/2010 18:41:43 ***********************
[17:21:17] ************************** ProtoMol Folding@Home Core **************************
[17:21:17]   Version: 25
[17:21:17]      Type: 180
[17:21:17]      Core: ProtoMol
[17:21:17]   Website: http://folding.stanford.edu/
[17:21:17] Copyright: (c) 2009 Stanford University
[17:21:17]    Author: Joseph Coffland <joseph@cauldrondevelopment.com>
[17:21:17]      Args: -dir work/ -suffix 04 -checkpoint 5 -lifeline 2592 -version 623
[17:21:17] ************************************ Build *************************************
[17:21:17]      Date: May 18 2010
[17:21:17]      Time: 23:43:52
[17:21:17]  Revision: 1819
[17:21:17]  Compiler: Intel(R) C++ MSVC 1500 mode 1110
[17:21:17]   Options: /TP /nologo /EHsc /wd4297 /wd4103 /wd1786 /arch:IA32 /Ox
[17:21:17]            /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qrestrict /MT
[17:21:17]   Defines: _CRT_SECURE_NO_WARNINGS NDEBUG HAVE_GEEKINFO BOOST_ALL_NO_LIB
[17:21:17]            XML_STATIC HAVE_EXPAT HAVE_OPENSSL HAVE_LIBFAH HAVE_SIMTK_LAPACK
[17:21:17]  Platform: Windows XP
[17:21:17]      Bits: 32
[17:21:17]      Mode: Release
[17:21:17] ************************************ System ************************************
[17:21:17]        OS: Microsoft Windows 7 Home Premium
[17:21:17]       CPU: AMD Athlon(tm) II X2 250 Processor
[17:21:17]    CPU ID: AuthenticAMD Family 16 Model 6 Stepping 2
[17:21:17]      CPUs: 2 Logical, 2 Physical
[17:21:17]    Memory: 3.75 GB
[17:21:17]   Threads: Windows
[17:21:17] ********************************************************************************
[17:21:17] Project: 10009 (Run 53, Clone 0, Gen 84)
[17:21:17] Unit: 0x000000820001329c4ba393a200000027
[17:21:17] User: 0x00000000000000000000000000000000
[17:21:17] Machine: 1
[17:21:17] Reading tar file par_all27_prot_lipid.inp
[17:21:17] Reading tar file scpismQuartic.inp
[17:21:17] Reading tar file par_all27_prot_lipid.inp
[17:21:17] Reading tar file scpismQuartic.inp
[17:21:17] Reading tar file ww_structure_14_charm.pdb
[17:21:17] Reading tar file ww_structure_14_charm.psf
[17:21:17] Reading tar file ww_structure_14_charm.vel
[17:21:17] Reading tar file checkpt
[17:21:17] Reading tar file ww_structure_14_charm.8197.pos
[17:21:17] Reading tar file ww_structure_14_charm.8197.vel
[17:21:17] Reading tar file protomol.conf
[17:21:17] Reading tar file core.xml
[17:21:17] Digital signatures verified
[17:21:17] Completed 0 out of 499375 steps (0%)
[17:21:17] Completed 5000 out of 499375 steps (1%)
[17:21:17] Completed 10000 out of 499375 steps (2%)
[17:21:17] Pausing core
[17:21:37] CoreStatus = 62 (98)
[17:21:37] + Restarting core (settings changed) 
[17:21:37] 
[17:21:37] + Processing work unit
[17:21:37] Core required: FahCore_b4.exe
[17:21:37] Core found.
[17:21:37] Working on queue slot 04 [October 6 17:21:37 UTC]
[17:21:37] + Working ...
[17:21:37] *********************** Log Started 05/Oct/2010 18:41:43 ***********************
[17:21:37] ************************** ProtoMol Folding@Home Core **************************
[17:21:37]   Version: 25
[17:21:37]      Type: 180
[17:21:37]      Core: ProtoMol
[17:21:37]   Website: http://folding.stanford.edu/
[17:21:37] Copyright: (c) 2009 Stanford University
[17:21:37]    Author: Joseph Coffland <joseph@cauldrondevelopment.com>
[17:21:37]      Args: -dir work/ -suffix 04 -checkpoint 5 -lifeline 2592 -version 623
[17:21:37] ************************************ Build *************************************
[17:21:37]      Date: May 18 2010
[17:21:37]      Time: 23:43:52
[17:21:37]  Revision: 1819
[17:21:37]  Compiler: Intel(R) C++ MSVC 1500 mode 1110
[17:21:37]   Options: /TP /nologo /EHsc /wd4297 /wd4103 /wd1786 /arch:IA32 /Ox
[17:21:37]            /QaxSSE2,SSE3,SSSE3,SSE4.1,SSE4.2 /Qrestrict /MT
[17:21:37]   Defines: _CRT_SECURE_NO_WARNINGS NDEBUG HAVE_GEEKINFO BOOST_ALL_NO_LIB
[17:21:37]            XML_STATIC HAVE_EXPAT HAVE_OPENSSL HAVE_LIBFAH HAVE_SIMTK_LAPACK
[17:21:37]  Platform: Windows XP
[17:21:37]      Bits: 32
[17:21:37]      Mode: Release
[17:21:37] ************************************ System ************************************
[17:21:37]        OS: Microsoft Windows 7 Home Premium
[17:21:37]       CPU: AMD Athlon(tm) II X2 250 Processor
[17:21:37]    CPU ID: AuthenticAMD Family 16 Model 6 Stepping 2
[17:21:37]      CPUs: 2 Logical, 2 Physical
[17:21:37]    Memory: 3.75 GB
[17:21:37]   Threads: Windows
[17:21:37] ********************************************************************************
[17:21:37] Project: 10009 (Run 53, Clone 0, Gen 84)
[17:21:37] Unit: 0x000000820001329c4ba393a200000027
[17:21:37] User: 0x00000000000000000000000000000000
[17:21:37] Machine: 1
[17:21:37] Reading tar file par_all27_prot_lipid.inp
[17:21:37] Reading tar file scpismQuartic.inp
[17:21:37] Reading tar file par_all27_prot_lipid.inp
[17:21:37] Reading tar file scpismQuartic.inp
[17:21:37] Reading tar file ww_structure_14_charm.pdb
[17:21:37] Reading tar file ww_structure_14_charm.psf
[17:21:37] Reading tar file ww_structure_14_charm.vel
[17:21:37] Reading tar file checkpt
[17:21:37] Reading tar file ww_structure_14_charm.8197.pos
[17:21:37] Reading tar file ww_structure_14_charm.8197.vel
[17:21:37] Reading tar file protomol.conf
[17:21:37] Reading tar file core.xml
[17:21:37] Digital signatures verified
[17:21:37] Completed 0 out of 499375 steps (0%)
[17:21:37] Completed 5000 out of 499375 steps (1%)
[17:21:37] Completed 10000 out of 499375 steps (2%)
[17:21:37] Pausing core
[17:21:58] CoreStatus = 62 (98)
[17:21:58] + Restarting core (settings changed) 
[17:21:58] 
[17:21:58] + Processing work unit
[17:21:58] Core required: FahCore_b4.exe
[17:21:58] Core found.
[17:21:58] Working on queue slot 04 [October 6 17:21:58 UTC]
[17:21:58] + Working ...
[17:21:58] *********************** Log Started 05/Oct/2010 18:41:43 ***********************
[17:21:58] ************************** ProtoMol Folding@Home Core **************************
[17:21:58]   Version: 25
[17:21:58]      Type: 180
[17:21:58]      Core: ProtoMol
[17:21:58]   Website: http://folding.stanford.edu/
[17:21:58] Copyright: (c) 2009 Stanford University
[17:21:58]    Author: Joseph Coffland <joseph@cauldrondevelopment.com>

...
.....

In the mean time, you may want to try initializing the client from scratch. Close the client. Delete the queue.dat, unitinfo.txt, client.cfg, and any fahcore files, and the \work folder.

Sure. Where do I find these things?

Restart the client, and it will go into the config screens. Set up your username and team number as desired, and go into the advanced menu. Add -verbosity 9 as a parameter in the last entry so we get more log info. When it starts, it should download a new core and work unit.

7im wrote:Hello Willyw, welcome to the forum.

Yes, there are quoting options. There is a Quote button to quote the whole post, or you can copy and paste a a part, and then use the

tags. Tags are on the preview page.

Yep. The Quote button has appeared now.
Thanks

Those files are in the same place as the fahlog.txt file. Same folder where you installed the client. The graphical client installes to C:\program files\Folding@home\

Actually, it installed to:
C:\Program Files (x86)\Folding@home\Folding@home-x86
I see Folding@home.exe in there....

None of the things mentioned, are in that directory.

Ah, yes. Sorry. Start\Programs\Folding@home\ and select the link to Data Files for Experts.

Or, as seen in your fahlog.txt file... Launch directory: C:\Users\*********\AppData\Roaming\Folding@home-x86

See this thread which is about the same problem.

The thread John Weatherman cites has a simple solution: Install the Console client instead of the Systray client. While it isn't as pretty as the Systray client, the Console client usually gives absolutely no problems once installed and configured. You can simply copy the client file into the folder of your choice, create a shortcut to it, set the shortcut to Run as Administrator, and run it. Copy the shortcut to your Startup folder if you want to start it automatically, or use the Run as a Service option in the config menu to keep it out of sight and mind.

Once you figure it all out, you can install a second instance in a separate folder and run both -- one for each CPU core.

jrweiss wrote:The thread John Weatherman cites has a simple solution: Install the Console client instead of the Systray client. While it isn't as pretty as the Systray client, the Console client usually gives absolutely no problems once installed and configured. You can simply copy the client file into the folder of your choice, create a shortcut to it, set the shortcut to Run as Administrator, and run it. Copy the shortcut to your Startup folder if you want to start it automatically, or use the Run as a Service option in the config menu to keep it out of sight and mind.

Once you figure it all out, you can install a second instance in a separate folder and run both -- one for each CPU core.

I don't get all the don't use the systray client stuff - i have 2 classic systray clients setup on my E6600 and they work fine together with ZERO issues

This was the problem with 2 systray (GUI) clients - from Wiki - "It is also important to give each Folding@home client its own Machine ID, which can best be done with the No-Nonsense Console client. The console client is recommended because the Machine ID can be set to a value other than 1. The Graphical (GUI) client for Windows is hard-coded to use a Machine ID of 1. The Machine ID can be set by the console client in the Advanced configuration section of the client setup.

Because of the Machine ID limitation of the GUI client, you can run only one GUI client in a multiple client scenario. All the other clients have to be console clients."
Not having used the systray client for a while, I assume that now it must be possible to change the machine id.
The problem that Willyw and others have had is just with the b4 core and seems to occur mostly on AMD cpus. See this thread.

Welcome to the foldingforum, Willyw.

I think those trying to help you have pretty much agreed that you've encountered some kind of bad interaction between the ProtoMol core and the systray client. That problem has been encountered before, but I don't think there's a fix for it, though the developers do have an open bug report on it.

Are you ruining more than one client on that machine?

I do believe that we all agree that you won't see the problem if you switch from the systray client to the console client, at least until the developers can fix the basic problem.

bruce wrote:Welcome to the foldingforum, Willyw.

Thank you.

I think those trying to help you have pretty much agreed that you've encountered some kind of bad interaction between the ProtoMol core

ahhh... umm... I saw that term "ProtoMol" in the log, but that's all I know about it. By "core", what do you mean? ... is it the version of the Folding client that I'm running?

A friend asked me to join, months ago, so I did.
I simply downloaded the version he recommended, and let 'er rip. I haven't gotten "into it". While it might be very interesting to learn more about it, I just haven't had the time. I have tried to run it some daily though.... the "every little bit counts" theory.

and the systray client.

This refers to the Windows version that I'm running... right?

That problem has been encountered before, but I don't think there's a fix for it, though the developers do have an open bug report on it.

Here's a question for you:
Has something changed?
In other words, I've run this for a few months now. Almost daily, if not actually daily. No problems. Well... I think I saw it said a bad packet or something like that once, and that it was uploading early. It did, then it downloaded new stuff, and proceeded to continue perking right along. That was quite some time ago though.
This that I've reported, is new.
When something new happens, with something that has been working fine, logically one looks for what could have changed.
Why else would it work for so long, then quit working normally?

Are you ruining more than one client on that machine?

No.
One.

I do believe that we all agree that you won't see the problem if you switch from the systray client to the console client, at least until the developers can fix the basic problem.

I can start over, and figure it out... a new install of a different program... if necessary.
However, in the interest of simplicity and speed (right now, that's more important to me), I was hoping for a quick fix. "Do this : .... "

While I appreciate all the bits of info I've received here, and the poster's time in replying here, I really didn't want to take the time to really read all the info in some of those links for detail.
(Since I had changed nothing, I was kind of hoping it was something well known, with a simple "Do this:...." type of fix.)
As I skimmed around in the links provided, I saw that somebody mentioned to open Task Manager, with Folding running, and kill every instance of it. That this would cause it to d/l a new packet, etc.
So, I did that.
And, it did ... as best as I could tell from the log... start over again with a new packet.
This was yesterday.
Remember... it got stuck at 2% before... and yesterday it progressed on up to 20 something percent, before I had to go, and quit the program.

Today, I've started it again.
It seems to my untrained eye, to be running normally.
It is at 28% completed right now.

It seems that you are getting reports of this.... I hope with my blathering on in this post, that maybe I've said something that is useful to the powers that be, that are trying to solve it.

Unless you strongly recommend that I un-install the graphical client that I'm again using, and recommend that I then install the command line client - I'll go back to the way I've done it for so long... just click it, let it sit in the try all day running, and pretty much forget about it.

Again, thank you all for your time.

The "quick fix: do this" is to simply replace the Systray client with the Console client. You shouldn't even lose the work it has already done. If the Uninstall process leaves all the data files, then you simply have to download the console client into the same folder and configure/run it. It should take less than 5 minutes. After that it should run as I described above.

Since you only have 2% of the current work unit completed, you can choose to delete it all, install the Console client in a different folder, and allow the Console client to download a new core and work unit.