129.74.246.143 out of work

[inpsyght]

server 129.74.246.143 has been out of work for approx 48hrs.

how does one manually force the F@H client to get work from another server?

[Joe_H]

That server does not appear to be out of work according to the information on the Server Status page. Please post your log file including the beginning section, system information and current configuration. Information on how to post a log is available from the Welcome to the Forum Topic.

[EXT64]

Are you on client v6? Usually the fix-all for getting WUs on v6 is to delete the unitinfo, queue, and machinedependent.dat files.

[Asterix]

I have the same problem running the version 6.23 console client on Win7.

Here's my log:

Code: Select all

C:\Users\xxxx\Documents\Miscellaneous\FAH3>[email protected] -verbosity 9

Note: Please read the license agreement ([email protected] -license). Further
use of this software requires that you have read and accepted this agreement.



--- Opening Log file [April 14 16:55:15 UTC]


# Windows CPU Console Edition #################################################
###############################################################################

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory: C:\Users\xxxx\Documents\Miscellaneous\FAH3
Executable: [email protected]
Arguments: -verbosity 9

[16:55:15] - Ask before connecting: No
[16:55:15] - Proxy: 192.168.198.45:8080
[16:55:15] - User name: Asterix (Team 0)
[16:55:15] - User ID: 58EBE4F07ACBFEAE
[16:55:15] - Machine ID: 3
[16:55:15]
[16:55:15] Loaded queue successfully.
[16:55:15] - Preparing to get new work unit...
[16:55:15] - Autosending finished units... [April 14 16:55:15 UTC]
[16:55:15] + Attempting to get work packet
[16:55:15] Trying to send all finished work units
[16:55:15] - Will indicate memory of 8182 MB
[16:55:15] + No unsent completed units remaining.
[16:55:15] - Detect CPU.[16:55:15] - Autosend completed
 Vendor: GenuineIntel, Family: 6, Model: 14, Stepping: 5
[16:55:15] - Connecting to assignment server
[16:55:15] Connecting to http://assign.stanford.edu:8080/
[16:55:15] Posted data.
[16:55:15] Initial: 4A81; - Successful: assigned to (129.74.246.143).
[16:55:15] + News From Folding@Home: Welcome to Folding@Home
[16:55:15] Loaded queue successfully.
[16:55:15] Connecting to http://129.74.246.143:8080/
[16:55:15] Posted data.
[16:55:15] Initial: 0000; - Error: Bad packet type from server, expected work assignment
[16:55:15] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.

I go through a proxy, which isn't a problem. I can get to the assignment server just fine with a browser.

Deleting unitinfo.txt and queue.dat didn't help any. That's the first thing I tried.

Asterix

[Joe_H]

The 6.23 client is no longer supported, and most servers require at least a higher version to assign a WU. You should upgrade to at least the 6.34 version, Version 7 is recommended for most users.

[inpsyght]

using v6.23 on win 7 64bit
have had this issue once before (see viewtopic.php?f=18&t=24725)

Code: Select all

--- Opening Log file [April 13 00:02:43 UTC] 


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

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory: C***********************


[00:02:43] - Ask before connecting: No
[00:02:43] - User name: inpsyght (Team 24)
[00:02:43] - User ID: **************************
[00:02:43] - Machine ID: 1
[00:02:43] 
[00:02:43] Loaded queue successfully.
[00:02:44] Initialization complete
[00:02:44] - Preparing to get new work unit...
[00:02:44] + Attempting to get work packet
[00:02:44] - Connecting to assignment server
[00:02:47] - Successful: assigned to (129.74.246.143).
[00:02:47] + News From Folding@Home: Welcome to Folding@Home
[00:02:47] Loaded queue successfully.
[00:02:48] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[00:02:54] + Attempting to get work packet
[00:02:54] - Connecting to assignment server
[00:02:55] - Successful: assigned to (129.74.246.143).
[00:02:55] + News From Folding@Home: Welcome to Folding@Home
[00:02:55] Loaded queue successfully.
[00:02:56] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[00:03:12] + Attempting to get work packet
[00:03:12] - Connecting to assignment server
[00:03:13] - Successful: assigned to (129.74.246.143).
[00:03:13] + News From Folding@Home: Welcome to Folding@Home
[00:03:13] Loaded queue successfully.
[00:03:13] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.
[00:03:45] + Attempting to get work packet
[00:03:45] - Connecting to assignment server
[00:03:46] - Successful: assigned to (129.74.246.143).
[00:03:46] + News From Folding@Home: Welcome to Folding@Home
[00:03:46] Loaded queue successfully.
[00:03:46] - Attempt #4  to get work failed, and no other work to do.
Waiting before retry.
[00:04:27] + Attempting to get work packet
[00:04:27] - Connecting to assignment server
[00:04:28] - Successful: assigned to (129.74.246.143).
[00:04:28] + News From Folding@Home: Welcome to Folding@Home
[00:04:28] Loaded queue successfully.
[00:04:29] - Attempt #5  to get work failed, and no other work to do.
Waiting before retry.
[00:05:57] + Attempting to get work packet
[00:05:57] - Connecting to assignment server
[00:05:58] - Successful: assigned to (129.74.246.143).
[00:05:58] + News From Folding@Home: Welcome to Folding@Home
[00:05:58] Loaded queue successfully.
[00:05:59] - Attempt #6  to get work failed, and no other work to do.
Waiting before retry.
[00:08:52] + Attempting to get work packet
[00:08:52] - Connecting to assignment server
[00:08:53] - Successful: assigned to (129.74.246.143).
[00:08:53] + News From Folding@Home: Welcome to Folding@Home
[00:08:53] Loaded queue successfully.
[00:08:54] - Attempt #7  to get work failed, and no other work to do.
Waiting before retry.
[00:14:19] + Attempting to get work packet
[00:14:19] - Connecting to assignment server
[00:14:20] - Successful: assigned to (129.74.246.143).
[00:14:20] + News From Folding@Home: Welcome to Folding@Home
[00:14:20] Loaded queue successfully.
[00:14:21] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[00:25:02] + Attempting to get work packet
[00:25:02] - Connecting to assignment server
[00:25:03] - Successful: assigned to (129.74.246.143).
[00:25:03] + News From Folding@Home: Welcome to Folding@Home
[00:25:03] Loaded queue successfully.
[00:25:04] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.
[00:46:27] + Attempting to get work packet
[00:46:27] - Connecting to assignment server
[00:46:28] - Successful: assigned to (129.74.246.143).
[00:46:28] + News From Folding@Home: Welcome to Folding@Home
[00:46:28] Loaded queue successfully.
[00:46:28] - Attempt #10  to get work failed, and no other work to do.
Waiting before retry.
[01:29:21] + Attempting to get work packet
[01:29:21] - Connecting to assignment server
[01:29:22] - Successful: assigned to (129.74.246.143).
[01:29:22] + News From Folding@Home: Welcome to Folding@Home
[01:29:22] Loaded queue successfully.
[01:29:23] - Attempt #11  to get work failed, and no other work to do.
Waiting before retry.
[02:17:28] + Attempting to get work packet
[02:17:28] - Connecting to assignment server
[02:17:29] - Successful: assigned to (129.74.246.143).
[02:17:29] + News From Folding@Home: Welcome to Folding@Home
[02:17:30] Loaded queue successfully.
[02:17:30] - Attempt #12  to get work failed, and no other work to do.
Waiting before retry.
[03:05:39] + Attempting to get work packet
[03:05:39] - Connecting to assignment server
[03:05:40] - Successful: assigned to (129.74.246.143).
[03:05:40] + News From Folding@Home: Welcome to Folding@Home
[03:05:40] Loaded queue successfully.
[03:05:41] - Attempt #13  to get work failed, and no other work to do.
Waiting before retry.
[03:53:44] + Attempting to get work packet
[03:53:44] - Connecting to assignment server
[03:53:45] - Successful: assigned to (129.74.246.143).
[03:53:45] + News From Folding@Home: Welcome to Folding@Home
[03:53:45] Loaded queue successfully.
[03:53:46] - Attempt #14  to get work failed, and no other work to do.
Waiting before retry.
[04:41:54] + Attempting to get work packet
[04:41:54] - Connecting to assignment server
[04:41:55] - Successful: assigned to (129.74.246.143).
[04:41:55] + News From Folding@Home: Welcome to Folding@Home
[04:41:55] Loaded queue successfully.
[04:41:56] - Attempt #15  to get work failed, and no other work to do.
Waiting before retry.
[05:30:09] + Attempting to get work packet
[05:30:09] - Connecting to assignment server
[05:30:10] - Successful: assigned to (129.74.246.143).
[05:30:10] + News From Folding@Home: Welcome to Folding@Home
[05:30:11] Loaded queue successfully.

[Joe_H]

Minimum client version listed for that server on the Server Status page is 6.34. As was recommended the other time you had this issue, please upgrade to at least version 6.34 of the client.

[inpsyght]

i will NOT be changing client version.
The new client (V7) does not allow me to tune the workload so that it is only using the free processor cycles (thus not costing me any extra money via power watt consumption)

Since my last post in AUG 2013, i've gone from rank 65000 to rank 60000, using this set-up at approx 12 hrs per day on a i5 ivy bridge cpu.
All the wu's my system has been assigned get done quickly, often in a 1/4 to 1/2 the time for deadline.

That means that at no extra cost to me, i'm still donating useful work and being within the top 20% of donators.
I'd be surprised if there is no more work for a set-up like this to do???

please advise how i can switch assignment servers??

[Joe_H]

You can't. Your system was connected to an AS, then directed to the Work Server that the AS was best able to determine might have work for your system. That assignment is under PG control, not something you can change to the extent you indicate you want to.

Also, while V7 is recommended, I specifically stated that you should upgrade to at least version 6.34. That version is still available on the Old Software Downloads page. In any case, V7 is as configurable as V6 to use that portion of your system's resources you want it to, you do not have to accept its default settings.

[P5-133XL]

No one is saying you need to go to v7. What was said is to move from v6.23 to v6.34+. You can still run v6, just a slightly more recent version of it.

That being said, I'm not sure what you mean by not being able to tune the workload with v7. I'm curious, what specifically are you doing that you think v7 can't do?

[Asterix]

The 6.34 client gives me the exact same error when I'm assigned 129.74.246.143.

Code: Select all

Initial: 0000; - Error: Bad packet type from server, expected work assignment

One 6.23 client I'm running did finally get a WU at about 1100UTC, but only after a 502 error gave me another server. 171.64.65.80 gave me a WU.

So, we keep coming back to 129.74.246.143 isn't playing nicely with either the 6.34 or 6.23 client.

[7im]

You will continue to have more and more problems getting work using an out dated client like 6.23. It has been clearly stated that v6.34 is the minimum supported version as a CPU / SMP client. And v6.41 for GPU.

If you choose to run an older version, we cannot help you. If you don't answer the question about how you "tune" the workload, we can't help your there either.

Eventually v6 client is going away. You have an option to learn V7 now at your leisure, or later when v6 get switch off.

[Asterix]

Yes, but 6.34 gave me the same error as 6.23.

A more useful error would be something like, "Your client is too old - no work units are available for it. Please upgrade." Rather than "Bad packet type from server."

I've now upgraded to 7.4.4 on my machines that Fold. You guys sure didn't make it easy to find the V7 console client that does not require full installation. The V6 clients are still right up front when I went looking for a console-only client. I can't be the only one who wants one.

[7im]

Yes, but 6.34 gave me the same error as 6.23.

A more useful error would be something like, "Your client is too old - no work units are available for it. Please upgrade." Rather than "Bad packet type from server."

I've now upgraded to 7.4.4 on my machines that Fold. You guys sure didn't make it easy to find the V7 console client that does not require full installation. The V6 clients are still right up front when I went looking for a console-only client. I can't be the only one who wants one.

The developers spend their limited time improving the current software, not adding new error messaging to a nearly obsolete client.

You'll be happy to know, the V7 client does have onscreen messaging like that, if you run the GUI. If you are savy enough to run the command line client, you probably don't need newbie reminders to upgrade.

For your reference: Windows Install Guide - Command Line Option

[Jesse_V]

Reported on #folding@home

<ChristW> I upgraded to 7.4.4 yesterday and today, but keep on getting no work units. Anything I can do to check what's wrong?
<ChristW> It seems as if the 'assigned server' is somehow wrong, is 129.74.246.143 'reasonable'?
<Jesse_V> is this for the CPU or for the GPU?
<ChristW> I _assume_ for the CPU...
<ChristW> 06:27:22:Enabled folding slot 00: READY cpu:1
<ChristW> 06:27:25:WU00:FS00:Assigned to work server 129.74.246.143
<ChristW> 06:27:25:WU00:FS00:Requesting new work unit for slot 00: READY cpu:1 from 129.74.246.143
<ChristW> 06:27:25:WU00:FS00:Connecting to 129.74.246.143:8080
<ChristW> 06:27:26:ERROR:WU00:FS00:Exception: Server did not assign work unit
<Jesse_V> odd
<ChristW> If I go to that URL (129.74.246.143:8080), I get '401 HTTP UNAUTHORIZED /'