This all makes perfect sense to me, not sure what it is you're questioning:
client log for port 12006 wrote: [2017-09-22 06:39:17 W(] 27: Getting work from server prpnet.primegrid.com at port 12006
[2017-09-22 06:39:18 W(] 27: PRPNet server is version 5.4.0
[2017-09-22 20:13:49 W(] 27: 27*2^6761330+1 is not prime. Residue C2BE76B41CB710A5
[2017-09-22 20:13:49 W(] Total Time: 34:19:26 Total Work Units: 3 Special Results Found: 0
[2017-09-22 20:13:50 W(] 27: Returning work to server prpnet.primegrid.com at port 12006
[2017-09-22 20:13:51 W(] 27: INFO: Test for 27*2^6761330+1 was accepted
[2017-09-22 20:13:51 W(] 27: INFO: All 1 test results were accepted
It took 13:34:36 to test a candidate with 2,035,365 digits.
client log for port 12002 wrote: [2017-09-22 20:13:51 W(] Due to changes in the prpclient.ini file, work classes have been reloaded
[2017-09-23 01:20:51 W(] FPS: 243931!+1 is not prime. Residue FE20AD443C06BC26
[2017-09-23 01:20:51 W(] Total Time: 39:26:28 Total Work Units: 4 Special Results Found: 0
[2017-09-23 01:20:52 W(] FPS: Returning work to server prpnet.primegrid.com at port 12002
[2017-09-23 01:20:53 W(] FPS: INFO: Test for 243931!+1 was accepted
[2017-09-23 01:20:53 W(] FPS: INFO: All 1 test results were accepted
[2017-09-23 01:20:53 W(] FPS: Getting work from server prpnet.primegrid.com at port 12002
OK, yes, the server didn't tell you it was getting work from port 12002. Nonetheless you're testing a factorial candidate, which can only have come from port 12002 and is being reported back to port 12002. That candidate has 1,208,187 digits so it's much smaller than the k=27 candidate above. PFGW took 5:07 to run that test. It took a shorter time to test a smaller candidate. That also sounds OK. Is there something I'm missing here? |