171.67.108.25 Standby

[Mstenholm]

Got a small problem with this collection server - it is on standby and my 2685 can't be uploaded. That means the it is impossible to change user name in connection with the upcomming Chimp Challenge. Please get it up and running again.

[bruce]

Yes, that Collection Server has been having problems, but most of the old CSs also have problems accepting work. The CS is a last-resort after the primary Work Server fails to upload the result.

If you need help with a specific server, you need to report the primary Work Server, not the CS, and you probably need to provide more information such as a log. Please read the topic "Do this first" at the top of this forum.

[Mstenholm]

Did that (now) but both rigs uploaded eventually.

[bruce]

Please post your log.

Did they upload to the Work Server or to the Collection Server? What date-time were they uploaded?

[Brian Redoutey]

I'm having similar problems. The one server is down so it switches to this one as a backup, but it's not working either. Meanwhile I can't connect to anything that has work units, I'm running the OS X 6 client(yeah kind of off topic). The AS going wonky?

[bruce]

We really need to know the server(s) that you're having trouble with or at least the project numbers. See the second post in this topic.

There's nothing that can be done to fix the old Collection Servers that are off-line (including 171.67.108.25) so reporting problems associate with it is a waste of time. Those servers were running an old version of the Server code which is incompatible with the new server code. We can deal with problems associate with the primary Work Servers.

Although Vijay is talking about a different problem on a different server in this post, his comments about the WS code and the new hardware that will soon be on-line apply to this problem, too.

[bruce]

The AS going wonky?

No, it's not the Assignment Server either. We have to focus on the Work Server. Which server has successfully assigned work to you in the past? Has it gone off-line or is it out of WUs?

If you don't know which server that was, what projects have you completed recently?

If you're talking about your OS-X rig, the most recent project was 6065 completed yesterday which is served by 171.64.65.54.

[MilSF1]

Lovely, it appears that the two servers that I'm trying to connect to as either the AS or CS are both down.

171.64.65.54
171.67.108.25

Been attempting to hit these two servers for about 7 hrs now.

Code: Select all

Arguments: -verbosity 9 

[19:52:04] - Ask before connecting: No
[19:52:04] - User name: MilSF1 (Team 182234)
[19:52:04] - User ID: 613D620E20E8DDFC
[19:52:04] - Machine ID: 1
[19:52:04] 
[19:52:04] Loaded queue successfully.
[19:52:04] Deleting incompletely fetched item (4) from queue position #9
[19:52:04] - Warning: Could not delete all work unit files (9): Core file absent
[19:52:04] - Preparing to get new work unit...
[19:52:04] Cleaning up work directory
[19:52:04] - Autosending finished units... [May 10 19:52:04 UTC]
[19:52:04] Trying to send all finished work units
[19:52:04] + Attempting to get work packet
[19:52:04] Project: 6055 (Run 1, Clone 183, Gen 221)
[19:52:04] Passkey found


[19:52:04] - Will indicate memory of 8192 MB
[19:52:04] + Attempting to send results [May 10 19:52:04 UTC]
[19:52:04] - Detect CPU.[19:52:04] - Reading file work/wuresults_08.dat from core
 Vendor: GenuineIntel, Family: 6, Model: 14, Stepping: 5
[19:52:04] - Connecting to assignment server
[19:52:04]   (Read 3796171 bytes from disk)
[19:52:04] Connecting to http://assign.stanford.edu:8080/
[19:52:04] Connecting to http://171.64.65.54:8080/
[19:52:04] - Couldn't send HTTP request to server
[19:52:04] + Could not connect to Work Server (results)
[19:52:04]     (171.64.65.54:8080)
[19:52:04] + Retrying using alternative port
[19:52:04] Connecting to http://171.64.65.54:80/
[19:52:04] - Couldn't send HTTP request to server
[19:52:04] + Could not connect to Work Server (results)
[19:52:04]     (171.64.65.54:80)
[19:52:04] - Error: Could not transmit unit 08 (completed May 10) to work server.
[19:52:04] - 5 failed uploads of this unit.


[19:52:04] + Attempting to send results [May 10 19:52:04 UTC]
[19:52:04] - Reading file work/wuresults_08.dat from core
[19:52:04]   (Read 3796171 bytes from disk)
[19:52:04] Connecting to http://171.67.108.25:8080/
[19:52:04] - Couldn't send HTTP request to server
[19:52:04] + Could not connect to Work Server (results)
[19:52:04]     (171.67.108.25:8080)
[19:52:04] + Retrying using alternative port
[19:52:04] Connecting to http://171.67.108.25:80/
[19:52:04] - Couldn't send HTTP request to server
[19:52:04] + Could not connect to Work Server (results)
[19:52:04]     (171.67.108.25:80)
[19:52:04]   Could not transmit unit 08 to Collection server; keeping in queue.
[19:52:04] + Sent 0 of 1 completed units to the server
[19:52:04] - Autosend completed
[19:52:04] Posted data.
[19:52:04] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[19:52:04] + Couldn't get work instructions.
[19:52:04] - Attempt #1  to get work failed, and no other work to do.
Waiting before retry.

[bruce]

Welcome to foldingforum.org, MilSF1.

Well, technically, there are three servers. The Assignment Server (AS) is 171.67.108.200, the Work Server (WS) may be 171.64.65.54 or any other WS that has work for your client or from which the WU you have finished needs to be returned, and the Collection Server (CS) is permanently 171.67.108.25 off-line but is really non-essential. That's why I've been trying futilely to redirect the conversation away from 171.67.108.25. Based on last night's discussion, I contacted the owner of 171.64.65.54 asking that they fix it. That hasn't happened yet. Please see viewtopic.php?f=18&t=18612 and continue the discussion there.

[statesidecoma]

My work IS trying to send to the 171.67.108.25 Work Server and then says could not transmit to Collection Server, Confusing!?!?!? So what do I do about that? It is just being stored queue at the moment.

[bruce]

Look carefully. It tried to send four times: twice to 171.64.65.54 and twice to 171.67.108.25 (each on 2 different ports). Until server 171.64.65.54 comes back on-line, there's nothing you can do.