I have an unusual problem. Something is currently broken on one of my fastest SMP machines which is preventing me from connecting to send results.
I have quite a few machines running F@H in he office, but I only run SMP on three that I have direct control over. On one of these, I have been getting the following sorts of messages:
[18:16:29] + Attempting to send results [April 27 18:16:29 UTC]
[18:16:29] - Reading file work/wuresults_05.dat from core
[18:16:29] (Read 22078106 bytes from disk)
[18:16:29] Connecting to http://171.64.65.64:8080/
[18:16:29] - Couldn't send HTTP request to server
[18:16:29] + Could not connect to Work Server (results)
[18:16:29] (171.64.65.64:8080)
[18:16:29] + Retrying using alternative port
[18:16:29] Connecting to http://171.64.65.64:80/
[18:16:29] - Couldn't send HTTP request to server
[18:16:29] + Could not connect to Work Server (results)
[18:16:29] (171.64.65.64:80)
[18:16:29] - Error: Could not transmit unit 05 (completed April 25) to work server.
[18:16:29] - 14 failed uploads of this unit.
On the other machine, also running SMP, I am having no difficulties connecting to the same server.
[15:44:34] Trying to send all finished work units
[15:44:34] + No unsent completed units remaining.
[15:44:34] - Preparing to get new work unit...
[15:44:34] + Attempting to get work packet
[15:44:34] - Will indicate memory of 1024 MB
[15:44:34] - Connecting to assignment server
[15:44:34] Connecting to http://assign.stanford.edu:8080/
[15:44:35] Posted data.
[15:44:35] Initial: 40AB; - Successful: assigned to (171.64.65.64).
[15:44:35] + News From Folding@Home: Welcome to Folding@Home
[15:44:35] Loaded queue successfully.
[15:44:35] Connecting to http://171.64.65.64:8080/
[15:44:38] Posted data.
[15:44:38] Initial: 0000; - Receiving payload (expected size: 2436771)
[15:44:58] - Downloaded at ~118 kB/s
[15:44:58] - Averaged speed for that direction ~106 kB/s
[15:44:58] + Received work.
[15:44:58] Trying to send all finished work units
[15:44:58] + No unsent completed units remaining.
[15:44:58] + Closed connections
This started happening a couple of weeks ago, and I haven't been able to upload a result from machine #1 since then, while machine #2 has worked flawlessly throughout, even when connecting to the same server.
I have no difficulty DOWNLOADING new units (or cores, or anything), just uploading, and just from this one machine.
Out of curiousity, and as a troubleshooting step, I took the queue and work files from the machine that CANNOT connect and transferred them to a machine that CAN ... and suddenly it couldn't connect to send the results either. And once I restored the original queue and work files machine #2 worked fine again. So it's not anything in the machine's configuration. Could there be something in the queue itself that is causing this problem?
Any insight would be appreciated. I've got my heavy hitter out of the lineup, and farmpuma is getting away.