128.59.74.4 in Reject
Posted: Tue Feb 24, 2009 2:54 pm
I have two WUs trying to upload results to 128.59.74.4 in Reject mode. The Associated CS will not accept them either. I have three more comming due this morning to the same server.
Project: 3856 (Run 240, Clone 0, Gen 22)
and
Project: 3859 (Run 7985, Clone 0, Gen 8)
after 675 and 748 attemps to send overnight, I stopped them when I came in the office.
Username for these WUs is "Martin_UM_P4", team 96377 "Mactin".
BTW, I am having trouble obtaing WUs for the pas few weeks, nothing dramatic, but it can take some time to get to the AS and once assigned, it can take some more time to get a WU from busy servers. This behaviour was only seen with classic WUs until yesterday where it spread to my SMP machine at home.
Thanks
Project: 3856 (Run 240, Clone 0, Gen 22)
Code: Select all
[13:12:18] + Attempting to send results [February 24 13:12:18 UTC]
[13:12:18] - Reading file work/wuresults_01.dat from core
[13:12:18] (Read 1356362 bytes from disk)
[13:12:18] Connecting to http://128.59.74.4:8080/
[13:12:19] - Couldn't send HTTP request to server
[13:12:19] + Could not connect to Work Server (results)
[13:12:19] (128.59.74.4:8080)
[13:12:19] + Retrying using alternative port
[13:12:19] Connecting to http://128.59.74.4:80/
[13:12:20] - Couldn't send HTTP request to server
[13:12:20] + Could not connect to Work Server (results)
[13:12:20] (128.59.74.4:80)
[13:12:20] - Error: Could not transmit unit 01 (completed February 24) to work server.
[13:12:20] - 675 failed uploads of this unit.
[13:12:20] + Attempting to send results [February 24 13:12:20 UTC]
[13:12:20] - Reading file work/wuresults_01.dat from core
[13:12:20] (Read 1356362 bytes from disk)
[13:12:20] Connecting to http://171.65.103.100:8080/
[13:12:20] - Couldn't send HTTP request to server
[13:12:20] (Got status 503)
[13:12:20] + Could not connect to Work Server (results)
[13:12:20] (171.65.103.100:8080)
[13:12:20] + Retrying using alternative port
[13:12:20] Connecting to http://171.65.103.100:80/
[13:12:23] Posted data.
[13:12:23] Initial: 0000; - Server reports packet it received specified a data size of 0.
[13:12:23] (May be due to corruption during network transmission or a corrupted file.)
[13:12:23] Could not transmit unit 01 to Collection server; keeping in queue.
[13:12:23] + Sent 0 of 1 completed units to the server
[13:12:23] - Failed to send all units to server
[13:12:23] ***** Got a SIGTERM signal (2)
[13:12:23] Killing all core threads
Project: 3859 (Run 7985, Clone 0, Gen 8)
Code: Select all
[13:10:44] + Attempting to send results [February 24 13:10:44 UTC]
[13:10:44] - Reading file work/wuresults_01.dat from core
[13:10:44] (Read 871488 bytes from disk)
[13:10:44] Connecting to http://128.59.74.4:8080/
[13:10:45] - Couldn't send HTTP request to server
[13:10:45] + Could not connect to Work Server (results)
[13:10:45] (128.59.74.4:8080)
[13:10:45] + Retrying using alternative port
[13:10:45] Connecting to http://128.59.74.4:80/
[13:10:46] - Couldn't send HTTP request to server
[13:10:46] + Could not connect to Work Server (results)
[13:10:46] (128.59.74.4:80)
[13:10:46] - Error: Could not transmit unit 01 (completed February 24) to work server.
[13:10:46] - 748 failed uploads of this unit.
[13:10:46] + Attempting to send results [February 24 13:10:46 UTC]
[13:10:46] - Reading file work/wuresults_01.dat from core
[13:10:46] (Read 871488 bytes from disk)
[13:10:46] Connecting to http://171.65.103.100:8080/
[13:10:46] - Couldn't send HTTP request to server
[13:10:46] (Got status 503)
[13:10:46] + Could not connect to Work Server (results)
[13:10:46] (171.65.103.100:8080)
[13:10:46] + Retrying using alternative port
[13:10:46] Connecting to http://171.65.103.100:80/
[13:10:46] - Couldn't send HTTP request to server
[13:10:46] (Got status 503)
[13:10:46] + Could not connect to Work Server (results)
[13:10:46] (171.65.103.100:80)
[13:10:46] Could not transmit unit 01 to Collection server; keeping in queue.
[13:10:46] + Sent 0 of 1 completed units to the server
[13:10:46] - Failed to send all units to server
[13:10:46] ***** Got a SIGTERM signal (2)
[13:10:46] Killing all core threads
Username for these WUs is "Martin_UM_P4", team 96377 "Mactin".
BTW, I am having trouble obtaing WUs for the pas few weeks, nothing dramatic, but it can take some time to get to the AS and once assigned, it can take some more time to get a WU from busy servers. This behaviour was only seen with classic WUs until yesterday where it spread to my SMP machine at home.
Thanks