Folding Forum

Posted: **Tue Aug 06, 2013 10:17 am**

This has been going for a few hours now.
Is this a server issue?

[22:55:44] Folding@home Core Shutdown: FINISHED_UNIT
[22:55:48] CoreStatus = 64 (100)
[22:55:48] Sending work to server
[22:55:48] Project: 7049 (Run 0, Clone 718, Gen 4)
[22:55:48] - Read packet limit of 540015616... Set to 524286976.


[22:55:48] + Attempting to send results [August 5 22:55:48 UTC]
[23:00:50] + Results successfully sent
[23:00:50] Thank you for your contribution to Folding@Home.

[23:00:54] - Preparing to get new work unit...
[23:00:54] + Attempting to get work packet
[23:00:54] - Connecting to assignment server
[23:00:56] - Successful: assigned to (143.89.28.72).
[23:00:56] + News From Folding@Home: Welcome to Folding@Home
[23:00:56] Loaded queue successfully.
[23:00:56] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[23:01:08] + Attempting to get work packet
[23:01:08] - Connecting to assignment server
[23:01:09] - Successful: assigned to (143.89.28.72).
[23:01:09] + News From Folding@Home: Welcome to Folding@Home
[23:01:10] Loaded queue successfully.
[23:01:10] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[23:01:28] + Attempting to get work packet
[23:01:28] - Connecting to assignment server
[23:01:29] - Successful: assigned to (143.89.28.72).
[23:01:29] + News From Folding@Home: Welcome to Folding@Home
[23:01:29] Loaded queue successfully.
[23:01:29] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[23:01:59] + Attempting to get work packet
[23:01:59] - Connecting to assignment server
[23:02:00] - Successful: assigned to (143.89.28.72).
[23:02:00] + News From Folding@Home: Welcome to Folding@Home
[23:02:00] Loaded queue successfully.
[23:02:01] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[23:02:48] + Attempting to get work packet
[23:02:48] - Connecting to assignment server
[23:02:49] - Successful: assigned to (143.89.28.72).
[23:02:49] + News From Folding@Home: Welcome to Folding@Home
[23:02:49] Loaded queue successfully.
[23:02:50] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[23:04:15] + Attempting to get work packet
[23:04:15] - Connecting to assignment server
[23:04:16] - Successful: assigned to (143.89.28.72).
[23:04:16] + News From Folding@Home: Welcome to Folding@Home
[23:04:16] Loaded queue successfully.
[23:04:17] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[23:07:10] + Attempting to get work packet
[23:07:10] - Connecting to assignment server
[23:07:11] - Successful: assigned to (143.89.28.72).
[23:07:11] + News From Folding@Home: Welcome to Folding@Home
[23:07:11] Loaded queue successfully.
[23:07:12] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[23:12:42] + Attempting to get work packet
[23:12:42] - Connecting to assignment server
[23:12:42] - Successful: assigned to (143.89.28.72).
[23:12:42] + News From Folding@Home: Welcome to Folding@Home
[23:12:43] Loaded queue successfully.
[23:12:43] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[23:23:28] + Attempting to get work packet
[23:23:28] - Connecting to assignment server
[23:23:29] - Successful: assigned to (143.89.28.72).
[23:23:29] + News From Folding@Home: Welcome to Folding@Home
[23:23:29] Loaded queue successfully.
[23:23:30] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[06:42:51] + Attempting to get work packet
[06:42:51] - Connecting to assignment server
[06:42:52] + Could not connect to Assignment Server
[06:42:54] + Could not connect to Assignment Server 2
[06:42:54] + Couldn't get work instructions.
[06:42:54] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[07:13:28] Opening http://fah-web.stanford.edu/cgi-bin/main.py?qtype=userpage&username=inpsyght...
[07:25:46] + Attempting to get work packet
[07:25:46] - Connecting to assignment server
[07:25:47] - Successful: assigned to (143.89.28.72).
[07:25:47] + News From Folding@Home: Welcome to Folding@Home
[07:25:47] Loaded queue successfully.
[07:25:48] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[08:13:52] + Attempting to get work packet
[08:13:52] - Connecting to assignment server
[08:13:53] - Successful: assigned to (143.89.28.72).
[08:13:53] + News From Folding@Home: Welcome to Folding@Home
[08:13:53] Loaded queue successfully.
[08:13:54] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[09:02:01] + Attempting to get work packet
[09:02:01] - Connecting to assignment server
[09:02:02] - Successful: assigned to (143.89.28.72).
[09:02:02] + News From Folding@Home: Welcome to Folding@Home
[09:02:02] Loaded queue successfully.
[09:02:02] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[09:50:09] + Attempting to get work packet
[09:50:09] - Connecting to assignment server
[09:50:10] - Successful: assigned to (143.89.28.72).
[09:50:10] + News From Folding@Home: Welcome to Folding@Home
[09:50:10] Loaded queue successfully.
[09:50:10] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.

Posted: **Tue Aug 06, 2013 10:25 am**

What version of the client? Please post the first 50 lines of the log showing the client starting.

Posted: **Tue Aug 06, 2013 10:29 am**

Thanks for the report. It looks like the server is not externally accessible (i.e. neither responds to pings or to http requests) even though the server status page claims they are up. I'll send a report to the server owner (looks like all his servers are not responding).

In the meantime your client will keep requesting work, if the assignment server gets notified that these servers are offline, it will start sending you to a different work server.

Posted: **Tue Aug 06, 2013 12:08 pm**

No probs, thanks for the quick reply!

Posted: **Tue Aug 06, 2013 1:21 pm**

Has it switched servers yet? If not, let's see that log.

Posted: **Wed Aug 07, 2013 12:01 am**

Unfortunately, the server is not yet issuing work units.
See log file below (just prior to the server problem) as requested.

Code: Select all

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

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory:


[07:38:44] - Ask before connecting: No
[07:38:44] - User name: 
[07:38:44] - User ID: 
[07:38:44] - Machine ID: 1
[07:38:44] 
[07:38:44] Loaded queue successfully.
[07:38:44] Initialization complete
[07:38:44] 
[07:38:44] + Processing work unit
[07:38:44] Core required: FahCore_a4.exe
[07:38:44] Core found.
[07:38:44] Working on queue slot 06 [August 3 07:38:44 UTC]
[07:38:44] + Working ...
[07:38:45] 
[07:38:45] *------------------------------*
[07:38:45] Folding@Home Gromacs GB Core
[07:38:45] Version 2.27 (Dec. 15, 2010)
[07:38:45] 
[07:38:45] Preparing to commence simulation
[07:38:45] - Ensuring status. Please wait.
[07:38:54] - Looking at optimizations...
[07:38:54] - Working with standard loops on this execution.
[07:38:54] - Previous termination of core was improper.
[07:38:54] - Files status OK
[07:38:54] - Expanded 135563 -> 308460 (decompressed 227.5 percent)
[07:38:54] Called DecompressByteArray: compressed_data_size=135563 data_size=308460, decompressed_data_size=308460 diff=0
[07:38:54] - Digital signature verified
[07:38:54] 
[07:38:54] Project: 7049 (Run 0, Clone 718, Gen 4)
[07:38:54] 
[07:38:54] Entering M.D.
[07:39:00] Using Gromacs checkpoints
[07:39:00] Mapping NT from 1 to 1 
[07:39:00] Resuming from checkpoint
[07:39:00] Verified work/wudata_06.log
[07:39:00] Verified work/wudata_06.trr
[07:39:00] Verified work/wudata_06.xtc
[07:39:00] Verified work/wudata_06.edr
[07:39:00] Completed 13158790 out of 25000000 steps  (52%)

Posted: **Wed Aug 07, 2013 12:35 am**

The availability of work units for this older version of the client (v6.23) is diminishing. You can extend the life of folding by upgrading to the command line client, version 6.34, or upgrading to the latest version, 7.3.6, if you like a GUI interface.

See also http://folding.typepad.com/news/2012/07 ... oject.html

Posted: **Wed Aug 07, 2013 2:53 am**

The availability of WUs for CPUs with a single core is also diminishing. I have not seen an end-of-life announcement but I do know that CPUs with a single core are becoming relatively rare and compared to other hardware, the science they produce is an increasingly small amount of what FAH needs. I have a couple of "old" computers that will only fold single-threaded projects and it's getting harder to get assignments -- and I'm running V7, which as 7im suggests, can process a number of projects which will not be assigned to a V6 client.

I do not know if the projects on a specific server are being assigned to single-core computers, but many projects are limited to more powerful systems. The science done by a single computer which has eight cpu-cores is much more valuable than the science done by eight single-core computers. In the case of 143.89.28.72, however, the computer is not assigning any WUs. I'll send another message to the owner of that server.

Posted: **Wed Aug 07, 2013 2:59 am**

I have now been assigned to another work server and have successfully begun new work unit.

7im - i tried version 7 about a year ago but the CPU usage slider is substandard compared to version 6.23.... does v6.34 command line have the same CPU usage parameter as v6.23?
To clarify why this is important, when i built my latest PC i measured a baseline 120w power consumption at idle, then installed F@H and aimed to find the CPU usage where the power consumption is still 120w.
On my Ivy Bridge CPU, this translates as about 25% of cpu capacity ( 1 core?) before the wattage use starts to rise.
So these are truly 'spare' cpu cycles that i donate - it means i pay for the same power consumption whether i run F@H or not.
From what i could tell, version 7 does not have this same type of adjustability.

Posted: **Wed Aug 07, 2013 3:23 am**

Your question about the %CPU setting isn't really a client issue but rather an change in how the FahCore deals with that setting. Yes, the %CPU usage function has been hidden in V7 but that's because the functionality is no longer supported by almost every FahCore that processes the WUs, not because the Client doesn't support it. If you happen to be assigned a WU that uses FahCore_78 it will still work but there are very few projects still running on a core from that era. If you happen to run with more than one CPU, the setting only applies to a single core while the other cores run at 100%.

FahCore_78 is being phased out. FahCore_a4 can handle either single an multi-core processing and it is being used on all newer projects.

Posted: **Wed Aug 07, 2013 3:54 am**

the log file i supplied above states that i am running core a4, so i guess that should enable me to keep donating under my current setup?

regardless of which work unit. my system always reports that F@H is utilising 25% of my total CPU, unless i adjust the %CPU parameter.
When i tried v7, i couldn't seem to find a way to limit the exact CPU usage in the same manner.

Over the past year i have seen my rank go from 150000th to 65000th, folding with the setup described above for about 12hrs per day.
As the front page states, there are currently ~260000 active processors, so logically my single core donation is still doing enough work to be considered useful.
I sure hope that the F@H project will continue to find use for and accept CPU donations from people happy to give their free cycles, but unwilling to be required to actually donate money (in the form of extra power watts consumed)

Posted: **Wed Aug 07, 2013 4:27 am**

The log you posted says you're configured for a single core, whether that's a hardware limitation or one you've imposed yourself. Yes, all contributions are considered useful, and will be until there's an end-of-life announcement. I'm just suggesting that IMHO, it seems to be likely that it might happen soon. Apparently when 143.89.28.72 is off-line, there may be appreciable periods of time when no other server has projects that can be assigned to uniprocessor clients (at least that's what your report says has been currently true).

The ~260000 number gives zero information about how many are uniprocessor clients, how many are SMP clients, and how many are GPU clients (/slots). If you know how to determine those percentages, let me know.

A parameter setting will reduce the CPU utilization from one core to less than one core. If you want to do that, use the parameter cpu-usage and set it to a percentage. If you're configured for, say 2 cores, I think it will adjust the utilization between 1 and 2 CPUs but SMP performance drops off very rapidly when all of the CPUs are not synchronized.

Your CPU far exceeds the capabilities of my "old" systems. The most recent project that you returned was
Your WU (P7049 R0 C718 G4) was added to the stats database on 2013-08-05 16:02:59 for 1985.11 points of credit.

Project 7049 has a preferred deadline of 33.3 days and you completed it in 5.36 days, which earned you a bonus in addition to the 1804.65 baseline points.

Posted: **Wed Aug 07, 2013 5:13 am**

V7 and v6 use the exact same fahcores, which do all the work, so the CPU usage setting works exactly the same in both client versions.

Posted: **Wed Aug 07, 2013 6:04 am**

viewtopic.php?f=24&t=14714&start=180#p247226

Folding Forum

143.89.28.72 not issuing WU

143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU

Re: 143.89.28.72 not issuing WU