[Cado-nfs-discuss] Help starting out using two machines

Emmanuel Thomé Emmanuel.Thome at inria.fr
Mon Mar 9 17:24:00 CET 2020


On Mon, Mar 09, 2020 at 06:59:17AM -0400, David Willmore wrote:
> It looks like the git version of the code tickled a bug in python's
> libraries.  The clients now fail with:
> ./cado-nfs-client.py:724: DeprecationWarning: cafile, capath and
> cadefault are deprecated, use a custom context instead.  return
> urllib_request.urlopen(request, cafile=cafile)
> 
> and then 404 with no work found.  This even happens with the normal
> invocation of the script.

I'll try to reproduce this. At least the warning could/should be fixed,
but I think that it should be harmless. After all, it's only a warning
(my guess is that python --version is a python3.x on your machine. While
cado-nfs-client _should_ cope equally with python2 and python3, since its
shebang says python only, we don't test it that often with python3).

I'm skeptical about the link between the warning and the 404 that you
get. Do you have a precise summary of what you did, including the server
output ?

E.

> 
> OS: Fedora 31
> 
> Specific libraries and package versions available as requested.
> 
> On Mon, Mar 9, 2020 at 4:42 AM Emmanuel Thomé <Emmanuel.Thome at inria.fr> wrote:
> >
> > On Sun, Mar 08, 2020 at 08:46:11PM -0400, David Willmore wrote:
> > > When built from git and run on the example from the make file, I run
> > > into a problem:
> > > [willmore at blade1 cado-nfs]$ ./cado-nfs.py
> > > 90377629292003121684002147101760858109247336549001090677693
> > [...]
> > > Info:HTTP server: serving at https://blade1:38715 (0.0.0.0)
> > [...]
> > > And there it sits.  Nothing is running.  There are ten instances of
> > > cado_nfs_client.py on the machine in a sleep state--clearly waiting
> > > for something on their network sockets. Hmm, okay, it's not using port
> > > 8001 for some reason.  I wonder if the firewall is that strict. .....
> > > Yes, yes it is.  It's blocking the seemingly random port that the
> > > script now picks.  Updating the firewall after the script runs isn't
> > > enough.  Is there a way to tell the script to stop picking random
> > > ports?
> >
> > ./cado-nfs.py 90377629292003121684002147101760858109247336549001090677693 server.port=8001
> >
> > And then if you want to take care of running the clients by yourself, run
> > the server with
> >
> > ./cado-nfs.py 90377629292003121684002147101760858109247336549001090677693 server.port=8001 --server
> >
> > As per ./scripts/cadofactor/README.md , if you supply a parameter file,
> > there's no default behaviour that starts clients. E.g. this is equivalent
> > to the former:
> >
> > ./cado-nfs.py 90377629292003121684002147101760858109247336549001090677693 server.port=8001 ./parameters/factor/params.c60
> >
> > Best,
> >
> > E.
> >


More information about the Cado-nfs-discuss mailing list