Page 1 of 1
140.163.4.231 not actually downloading work
Posted: Sat Jan 07, 2017 2:57 pm
by HaloJones
Any client connecting to 140.163.4.231 for a new unit starts to download but barely moves past the 1st 1%. The client is then stuck permanently in a READY state.
Re: 140.163.4.231 not actually downloading work
Posted: Sun Jan 08, 2017 7:31 am
by JohnChodera
Thanks for the heads-up. I'm investigating.
Is this the only server you're having trouble with? I'm showing lots of WUs moving in and out of the server (plfah1-1.mskcc.org) just fine.
Re: 140.163.4.231 not actually downloading work
Posted: Sun Jan 08, 2017 7:32 am
by JohnChodera
I've restarted the work server just in case.
I wonder if this might be some sort of network congestion issue on our end.
Re: 140.163.4.231 not actually downloading work
Posted: Sun Jan 08, 2017 10:43 am
by HaloJones
Stil having issues
Code: Select all
08:24:48:WU01:FS01:0x21:Completed 4950000 out of 5000000 steps (99%)
08:24:49:WU00:FS01:Connecting to 171.67.108.45:80
08:24:49:WU00:FS01:Assigned to work server 140.163.4.242
08:24:49:WU00:FS01:Requesting new work unit for slot 01: RUNNING gpu:0:GM204 [GeForce GTX 970] from 140.163.4.242
08:24:49:WU00:FS01:Connecting to 140.163.4.242:8080
08:24:50:WU00:FS01:Downloading 5.31MiB
08:27:09:WU01:FS01:0x21:Completed 5000000 out of 5000000 steps (100%)
08:27:11:WU01:FS01:0x21:Saving result file logfile_01.txt
08:27:11:WU01:FS01:0x21:Saving result file checkpointState.xml
08:27:11:WU01:FS01:0x21:Saving result file checkpt.crc
08:27:11:WU01:FS01:0x21:Saving result file log.txt
08:27:11:WU01:FS01:0x21:Saving result file positions.xtc
08:27:12:WU01:FS01:0x21:Folding@home Core Shutdown: FINISHED_UNIT
08:27:13:WU01:FS01:FahCore returned: FINISHED_UNIT (100 = 0x64)
08:27:13:WU01:FS01:Sending unit results: id:01 state:SEND error:NO_ERROR project:13500 run:0 clone:915 gen:71 core:0x21 unit:0x000000898ca304f457a358da3a41df62
08:27:13:WU01:FS01:Uploading 7.31MiB to 140.163.4.244
08:27:13:WU01:FS01:Connecting to 140.163.4.244:8080
08:27:19:WU01:FS01:Upload 18.82%
08:27:25:WU01:FS01:Upload 63.29%
08:27:33:WU01:FS01:Upload complete
08:27:33:WU01:FS01:Server responded WORK_ACK (400)
08:27:33:WU01:FS01:Final credit estimate, 63355.00 points
08:27:33:WU01:FS01:Cleaning up
This one is 140.163.4.242. Starts the download but two hours later it hasn't got the data to restart. Client just says READY.
Five different rigs all running Nvidia GPU clients have all had this at one time or another over the last 24 hours.
Re: 140.163.4.231 not actually downloading work
Posted: Sun Jan 08, 2017 5:03 pm
by bruce
When was the last time you reset your router (and then restarted FAH if it seems appropriate)?
Re: 140.163.4.231 not actually downloading work
Posted: Mon Jan 09, 2017 1:29 pm
by HaloJones
Router is reset regularly, FAH on all five rigs has now had this problem independently and across several days. Servers not sending work all begin 140.163.4. It also appears I'm not the only one who has had this problem as there is another similar thread now.
I know you're trying to help but I do not believe this is at my end or I would not have raised a thread here. You know I'm not a beginner at this stuff.
Re: 140.163.4.231 not actually downloading work
Posted: Mon Jan 09, 2017 7:36 pm
by JohnChodera
Thanks for the updates. I wonder if we're having network problems on our end. I'll investigate that possibility.
Re: 140.163.4.231 not actually downloading work
Posted: Mon Jan 16, 2017 3:58 am
by JohnChodera
Is the issue still persisting? Is there any way to tell if others are having this issue as well?
Re: 140.163.4.231 not actually downloading work
Posted: Mon Jan 16, 2017 7:34 pm
by bruce
@halojones:
I'd say you've run into the known issue in FAHClient V7.4.4 (though you have not posted the information that would show if you're running V7.4.4 or Beta V7.4.16). V7.4.4 is known to have problems never recovering from an internet interruption .. at least until you restart the client. Post the first two pages of your log, showing your configuration, including the client version you're running.
Resetting your router WITHOUT RESTARTING FAHCient V7.4.4 can cause the problem you're reporting.