Why do I keep getting assigned to 129.74.85.48?

[Teddy]

Coz the stupid client refuses to go to any other server for work so the machine is stuck there sitting idle.
I dicked around with the settings usual crap small/normal or big units, advmethods on/off changed machineid , delete work folder, queue.dat etc refuses to shift off that server.

Code: Select all

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

                       Folding@Home Client Version 6.23

                          http://folding.stanford.edu

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

Launch directory: C:\Folding 1
Executable: C:\Folding 1\Folding@home-Win32-x86.exe
Arguments: -advmethods -forceasm -verbosity 9 

Warning:
 By using the -forceasm flag, you are overriding
 safeguards in the program. If you did not intend to
 do this, please restart the program without -forceasm.
 If work units are not completing fully (and particularly
 if your machine is overclocked), then please discontinue
 use of the flag.

[09:38:05] - Ask before connecting: No
[09:38:05] - User name: Teddy2(OCAU) (Team 24)
[09:38:05] - User ID: 7578C8C000D44B71
[09:38:05] - Machine ID: 9
[09:38:05] 
[09:38:05] Loaded queue successfully.
[09:38:05] - Preparing to get new work unit...[09:38:05] - Autosending finished units... [May 14 09:38:05 UTC]

[09:38:05] Trying to send all finished work units
[09:38:05] + Attempting to get work packet
[09:38:05] + No unsent completed units remaining.
[09:38:05] - Will indicate memory of 2046 MB
[09:38:05] - Autosend completed[09:38:05] - Detect CPU.
 Vendor: GenuineIntel, Family: 6, Model: 15, Stepping: 11
[09:38:05] - Connecting to assignment server
[09:38:05] Connecting to http://assign.stanford.edu:8080/
[09:38:06] Posted data.
[09:38:06] Initial: 4A81; - Successful: assigned to (129.74.85.48).
[09:38:06] + News From Folding@Home: Welcome to Folding@Home
[09:38:06] Loaded queue successfully.
[09:38:06] Connecting to http://129.74.85.48:8080/
[09:38:07] - Couldn't send HTTP request to server
[09:38:07] + Could not connect to Work Server
[09:38:07] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.
[09:38:15] + Attempting to get work packet
[09:38:15] - Will indicate memory of 2046 MB
[09:38:15] - Connecting to assignment server
[09:38:15] Connecting to http://assign.stanford.edu:8080/
[09:38:16] Posted data.
[09:38:16] Initial: 4A81; - Successful: assigned to (129.74.85.48).
[09:38:16] + News From Folding@Home: Welcome to Folding@Home
[09:38:16] Loaded queue successfully.
[09:38:16] Connecting to http://129.74.85.48:8080/
[09:38:17] - Couldn't send HTTP request to server
[09:38:17] + Could not connect to Work Server
[09:38:17] - Attempt #2  to get work failed, and no other work to do.
Waiting before retry.
[09:38:29] + Attempting to get work packet
[09:38:29] - Will indicate memory of 2046 MB
[09:38:29] - Connecting to assignment server
[09:38:29] Connecting to http://assign.stanford.edu:8080/
[09:38:30] Posted data.
[09:38:30] Initial: 4A81; - Successful: assigned to (129.74.85.48).
[09:38:30] + News From Folding@Home: Welcome to Folding@Home
[09:38:30] Loaded queue successfully.
[09:38:30] Connecting to http://129.74.85.48:8080/
[09:38:31] - Couldn't send HTTP request to server
[09:38:31] + Could not connect to Work Server
[09:38:31] - Attempt #3  to get work failed, and no other work to do.
Waiting before retry.

Its a shambles Stanford, no wonder so many of my team get disheartened....

Not happy

Teddy

[^w^ing]

I'm on the same boat. I wanted to try out the new protomol core now when the guru meditation issue seems to be resolved. But after adding advmethods, the AS kept assigning me to 134.139.127.32 and 129.74.85.48, both kept refusing me. So I removed advmethods and got assigned to 171.64.65.62 successfully right away.

[codysluder]

The word "soon" is overused on this forum (and always with a ) but when an important feature like that is fixed, the new projects and FahCore will be distributed soon unless some other serious problem turns up during testing. The Pande Group is just as anxious to get you running those projects as you are anxious to get them.

[7im]

Changing Machine ID will sometimes bump you to a different server.

[Teddy]

Changing Machine ID will sometimes bump you to a different server.

Tried that see my original post

It has been sitting there all night refusing to go to any other server other than 48.
The other core of the Dual core machine is happily folding away after many restarts.
Perhaps I should try the SMP client on this Dual Core machine?
The GPU client is happily crunching away!

I moved away from the SMP client cause that too had server issues so I thought the classic client surely that will be happy as this is the longest running client guess not...
& Yes I know servers have issues from time to time but this is ridiculous...

Teddy

[7im]

Sorry, missed that. The next trick is to deleted the System ID out of the Registry, and let the client download a new one.

Note, you don't want to do this if you have other clients with active work units. Changing the System ID may cause the other WUs to not get credit. Do it after all WUs are done.

[^w^ing]

The word "soon" is overused on this forum (and always with a ) but when an important feature like that is fixed, the new projects and FahCore will be distributed soon unless some other serious problem turns up during testing. The Pande Group is just as anxious to get you running those projects as you are anxious to get them.

how is that relevant to anything that was posted in this thread?

[codysluder]

The word "soon" is overused on this forum (and always with a ) but when an important feature like that is fixed, the new projects and FahCore will be distributed soon unless some other serious problem turns up during testing. The Pande Group is just as anxious to get you running those projects as you are anxious to get them.

how is that relevant to anything that was posted in this thread?

You were the one who was anxious to be assigned the new protomol core and the WUs that invoke it. The AS can't assign you to protomol WUs until they're ready to distribute. At the time you asked, Protomol was listed as belonging to both server 129.74.85.15 and 129.74.85.48. (Now I see that 129.74.85.48 has disappeared.)

I'm on the same boat. I wanted to try out the new protomol core now when the guru meditation issue seems to be resolved. But after adding advmethods, the AS kept assigning me to 134.139.127.32 and 129.74.85.48, both kept refusing me. So I removed advmethods and got assigned to 171.64.65.62 successfully right away.

[^w^ing]

the fixed protomol core itself was out for a while already when I switched to advmethods but thats beside the point. The problem wasn't the core but the work servers to whose the AS kept assigning me to (protomol related or not), as they kept refusing my client, so I couldn't get any WU (again, be it protomol WU or any other WU).