Discussion related to cado-nfs

[Ed Hall <ed_ka2fwj@yahoo.com>]

Dear Team,

Here are a few more details from a test I did a few minutes ago.  This was the command line:

$ ../cado-nfs/cado-nfs.py 2893836611129328476311266994581154460132719000725437370101466776630575223258227195892838354605208491 server.whitelist=<whitelist> server.port=<port#> server.ssl=no tasks.polyselect.threads=4 tasks.wutimeout=1800 tasks.workdir=$HOME/Math/factorMain/alicado name=alicado server.linger_before_quit=600 --server
. . .
Info:werkzeug: <client IP> - - [23/Apr/2025 15:24:41] "GET /workunit HTTP/1.1" 404 -
Info:API server: Shutting down server
Info:Complete Factorization / Discrete logarithm: Total cpu/elapsed time for entire Complete Factorization 9338.07/311.195
144602880603554932124801 81740101239801297859098900793861 244828454448053076559542969852669875255442031

Note, there is no "linger" happening.

Here is the client command used (from within a script)::

./cado-nfs-client.py --clientid=${mach}.g --single --exit-on-server-gone --bindir=build/$HOSTNAME/ --override t $cpus --server=${server}
. . .
Long after the server had shut down (hours later). . .

Error:root: Download failed with hard error, HTTPConnectionPool(host='<host>.local', port=port#): Max retries exceeded with url: /workunit (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f82733272b0>: Failed to establish a new connection: [Errno 111] Connection refused'))
Error:root: Waiting 10.0 seconds before retrying (I have been waiting for 49.375 seconds)
Error:root: Going to next backup server: <same as original server>

Note, that this loop continues with varying times.  Also note that for this run "--exit-on-server-gone" did not trip, either.

Thanks for any help.

Sincerely,
Ed hall