The first time your client uploads the WU, you'll get credit but no credit if you try to upload it again. Then it will say"GOT_ALREADY"
What does your log show in the hour before 2013-12-29 21:05 GMT? Your log seems to start about two hours after it was actually uploaded.
Hi Hisui (team 0),
Your WU (P8569 R0 C3 G362) was added to the stats database on 2013-12-29 13:07:19 for 6644.99 points of credit.
Previous logs are stored in the logs subdirectory of FAH's data directory, renamed to the date and time. I would be interested in that segment of whichever log it happens to be in and a narrative of what happened. Under ordinary circumstances, when a WU is successfully uploaded, the local copy is deleted so the client doesn't try to upload it again. Obviously the server did note a successful upload but the client didn't delete it. My theory is that sometimes the confirmation message gets lost so you'll get this scenario.
Obviously it's better for the client to try again any time that the completion of the upload is uncertain, even if it leads to complaints like yours. Your report of connection issues is consistent with this explanation.
Well, at the rate the uploading was progressing, the upload should have finished about 20:14:13 and there's no indication whether it was successful or not. (The messages about "lost lifeline" and "Server connection ended" are not related to the upload and happened hours later.)
Nothing there to disprove my theory, but also every reason for you to wonder if the upload was successful or not -- and for the client to retry later. At that time, the server did report that the earlier upload had been successful.
I'm not sure how the software could do any better error recovery, given that the connection failed at the very end of the upload.
I have experienced this issue when my connection drops. The WU is usually successfully transferred (when the uploaded percentage is higher than 95%) but I would lose the connection before my FAHClient ever gets the acknowledgement or the points estimate being printed in the log. The second upload would be a GOT_ALREADY (434) and the WU deleted. I highly doubt that anything can be done about it since the root cause is the internet connection, something that F@H has no control over.
Moreover, if you do run a network intensive application/congested internet connection, there can be a situation where the packets sent by the F@H Servers are not received by your FAHClient so the download/upload is stuck. Usually, the upload restarts automatically but sometimes, a manual restart of FAHClient is needed. If the download hangs, restarting FAHClient is the only way to get it to download a new WU again. Please note that this is a known issue (https://fah.stanford.edu/projects/FAHClient/ticket/983) and will hopefully be resolved in a future release of V7.
ETA:
Now ↞ Very Soon ↔ Soon ↔ Soon-ish ↔ Not Soon ↠ End Of Time