Code: Select all
******************************* Date: 2014-11-22 *******************************
.
.
09:28:50:WU02:FS00:0xa4:- Shutting down core
09:28:50:WU02:FS00:0xa4:
09:28:50:WU02:FS00:0xa4:Folding@home Core Shutdown: FINISHED_UNIT
09:29:01:WU02:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
09:29:02:WU02:FS00:Sending unit results: id:02 state:SEND error:NO_ERROR project:9015 run:467 clone:2 gen:51 core:0xa4 unit:0x00000042664f2de453e55e1e332f655a
09:29:02:WU02:FS00:Uploading 1.64MiB to 171.64.65.124
09:29:02:WU02:FS00:Connecting to 171.64.65.124:8080
I only noticed it on this morning's check around the clients- after a reboot it connected to 171.64.65.124 and uploaded the WU with no bother.
I'm fairly sure that it was most probably caused by some sort of OS/client/network problem at my end, but I'd be interested in comments from others.
In particular, is this what I would expect from the known bug where FAH doesn't recover gracefully from a loss of internet connection during upload? I haven't had that happen before.
Though I should add that if there were such a break it would have been very brief, there's no sign of it in the router log or my monitoring app.