Page 1 of 1

171.67.108.17 - Could not transmit unit...

Posted: Sat Jan 29, 2011 2:29 pm
by FearTec
[14:23:38] + Attempting to send results [January 29 14:23:38 UTC]
[14:23:38] - Reading file work/wuresults_01.dat from core
[14:23:38] (Read 262064 bytes from disk)
[14:23:38] Connecting to http://171.67.108.17:8080/
[14:23:38] - Couldn't send HTTP request to server
[14:23:38] (Got status 503)
[14:23:38] + Could not connect to Work Server (results)
[14:23:38] (171.67.108.17:8080)
[14:23:38] + Retrying using alternative port
[14:23:38] Connecting to http://171.67.108.17:80/
[14:23:39] - Couldn't send HTTP request to server
[14:23:39] (Got status 503)
[14:23:39] + Could not connect to Work Server (results)
[14:23:39] (171.67.108.17:80)
[14:23:39] Could not transmit unit 01 to Collection server; keeping in queue.
[14:23:39] + Sent 0 of 1 completed units to the server
[14:23:39] - Autosend completed
[14:23:45] + Attempting to get work packet
[14:23:45] - Will indicate memory of 8175 MB
[14:23:45] - Connecting to assignment server
[14:23:45] Connecting to http://assign-GPU.stanford.edu:8080/
[14:23:46] Posted data.
[14:23:46] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[14:23:46] + Couldn't get work instructions.
[14:23:46] - Attempt #2 to get work failed, and no other work to do.
Waiting before retry.
[14:23:58] + Attempting to get work packet
[14:23:58] - Will indicate memory of 8175 MB
[14:23:58] - Connecting to assignment server
[14:23:58] Connecting to http://assign-GPU.stanford.edu:8080/
[14:23:59] Posted data.
[14:23:59] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[14:23:59] + Couldn't get work instructions.
[14:23:59] - Attempt #3 to get work failed, and no other work to do.
Waiting before retry.
[14:24:26] + Attempting to get work packet
[14:24:26] - Will indicate memory of 8175 MB
[14:24:26] - Connecting to assignment server
[14:24:26] Connecting to http://assign-GPU.stanford.edu:8080/
[14:24:27] Posted data.
[14:24:27] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[14:24:27] + Couldn't get work instructions.
[14:24:27] - Attempt #4 to get work failed, and no other work to do.
Waiting before retry.
[14:25:09] + Attempting to get work packet
[14:25:09] - Will indicate memory of 8175 MB
[14:25:09] - Connecting to assignment server
[14:25:09] Connecting to http://assign-GPU.stanford.edu:8080/
[14:25:10] Posted data.
[14:25:10] Initial: 0000; + No appropriate work server was available; will try again in a bit.
[14:25:10] + Couldn't get work instructions.
[14:25:10] - Attempt #5 to get work failed, and no other work to do.
Waiting before retry.

Re: 171.67.108.17 - Could not transmit unit...

Posted: Sat Jan 29, 2011 2:34 pm
by bollix47
171.67.108.17 is a collection server that's used when the work server cannot be contacted. Collection servers are usually very busy and it often takes many attempts to get a WU to return to them.

If you look further back in the log you will see the actual work server that isn't able to receive the WU.

This could be related to:

viewtopic.php?f=50&t=17427&p=173072#p173072

Problems with 171.67.108.17 ?

Posted: Sun Jan 08, 2012 8:18 pm
by ManxDave
I cant seem to send my WU. I assume when it come back online the WU will be sent automatically.

Re: Problems with 171.67.108.17 ?

Posted: Sun Jan 08, 2012 9:05 pm
by bollix47
viewtopic.php?p=161539#p161539

Re: Problems with 171.67.108.17 ?

Posted: Sun Jan 08, 2012 9:15 pm
by ManxDave
Thanks. Obviously only a very temporary prolem as it has now submitted.

Re: Problems with 171.67.108.17 ?

Posted: Sun Jan 08, 2012 10:49 pm
by gwildperson
ManxDave wrote:Thanks. Obviously only a very temporary prolem as it has now submitted.
Not really. You need to report a different server. Your WU is failing to upload to two different servers. Half a page above the messages that say you have a problem with 171.67.108.17 you'll find more messages that say something else failed. That's what needs to be reported.