Folding Forum

autogrog wrote:Got 1 wu last evening. Both servers (128.143.199.96 & .97) can be pinged, but are not accessible from the client nor a browser since last night. No upload or download attempts are working.

Is there any estimate as to when these will be fixed?

Same:

18:31:00:WU00:FS00:Uploading 11.18MiB to 128.143.199.97
18:31:00:WU00:FS00:Connecting to 128.143.199.97:8080
18:31:00:WU01:FS00:Starting
18:31:23:WARNING:WU00:FS00:Exception: Failed to send results to work server: Transfer failed

autogrog wrote:The server stats page says 128.143.199.96 & .97 are accepting, but my 6.34 client disagrees as do others above:

[22:05:53] Connecting to http://assign.stanford.edu:8080/
[22:05:54] Posted data.
[22:05:54] Initial: 0000; + Could not authenticate Assignment Server response
[22:05:54] Connecting to http://assign2.stanford.edu:80/
[22:05:55] Posted data.
[22:05:55] Initial: 0000; + Could not authenticate Assignment Server 2 response
[22:05:55] + Couldn't get work instructions.

Placing these 2 url's in Firefox returns the successful connect page, and pinging these IP address shows success as well??

Exactly what I have got from 2 machines today when switching back to SMP from BA units

These 2 servers are down again. The response to the url in a browser this morning is:
401 HTTP UNAUTHORIZED /

autogrog wrote:These 2 servers are down again. The response to the url in a browser this morning is:
401 HTTP UNAUTHORIZED /

Depending on the version of the WS code, that is the expected message. It does at least mean you could reach the server over the network. Older WS code would give either a blank page or one with an "OK" in the top left.

I cannot connect to .96, but do get the refused message from .97. Have no further information on what the problem is.

Both servers are nolonger working. After successfully uploading a completed WU last evening, the following is all that my system is getting:

[00:46:05] Connecting to http://assign.stanford.edu:8080/
[00:46:05] Posted data.
[00:46:05] Initial: 0000; + Could not authenticate Assignment Server response
[00:46:05] Connecting to http://assign2.stanford.edu:80/
[00:46:06] Posted data.
[00:46:06] Initial: 0000; + Could not authenticate Assignment Server 2 response
[00:46:06] + Couldn't get work instructions.
[00:46:06] - Attempt #1 to get work failed, and no other work to do.

They are both still broken:

[17:32:42] Connecting to http://assign.stanford.edu:8080/
[17:32:42] Posted data.
[17:32:42] Initial: 0000; + Could not authenticate Assignment Server response
[17:32:42] Connecting to http://assign2.stanford.edu:80/
[17:32:43] Posted data.
[17:32:43] Initial: 0000; + Could not authenticate Assignment Server 2 response
[17:32:43] + Couldn't get work instructions.
[17:32:43] - Attempt #1 to get work failed, and no other work to do.

failing for the last 6+ hours on multiple workstations.

Checking the logs for both servers from the serverstat page shows that both are up and have been accepting some work and giving out some assignments. Since you are running version 6 of the client, have you tried deleting the machinedependent.dat file and restarting the client?

Please note that there have been significant problems with the projects on this server. See viewtopic.php?f=18&t=27431

Until those projects are fixed (and I'm not sure of their current state), taking the server off-line prevents the problems reported in that other topic. If and when the projects have been regenerate/fixed, you'll just have to run projects from other servers. The problems injected by the loss of the RAID have required (or still will require) a lot of work.

I've seen no official word from the Pande Group either way but they're aware of the issues.

Joe_H wrote:Checking the logs for both servers from the serverstat page shows that both are up and have been accepting some work and giving out some assignments. Since you are running version 6 of the client, have you tried deleting the machinedependent.dat file and restarting the client?

Yes, but it still takes moeew than 20 retries before a WU is downloaded. The serverstat page appearantly gives erroneous info.

That may just mean there are few WU's on the server in queues that assign to version 6 clients. Half the entries on serverstat for this WS show a requirement of a minimum of version 7. To see that, mover your mouse pointer over the "i" in blue at the far right of the column.

A slight digression but since the cores have not changed substantially in years, why the version changes on the client side? is it a WS requirement due to the backend code changes? Given that v6 has not been declared EOL yet, it should still have access to all work, especially on the cpu side of things where cores have remained static, gpu is a different story due to core 18/19 etc.

New server code only supports newer features in the V7 client, like the bad WU reporting noted in the thread about bad WUs from the 75xx projects.

And if you haven't seen the posts about the diminishing availability of work for v6 clients over the last few years, the changing Min client version Info on the Server Status page was another indication.

Not EOL just yet, as there are some servers still supporting v6 clients, and will continue for some unknown length of time. But the recommendations to upgrade to V7 has been ongoing for years now. Not sure how that can be said any more plainly. The v6 client has been on the way out since V7 was released. Plan accordingly.
Edit by Mod: Spelling fixed.