Subject: Discussion related to cado-nfs
List archive
- From: Pierrick Gaudry <pierrick.gaudry@loria.fr>
- To: "Patrick R. St." <xorlogic@outlook.com>
- Cc: "cado-nfs-discuss@lists.gforge.inria.fr" <cado-nfs-discuss@lists.gforge.inria.fr>
- Subject: Re: [Cado-nfs-discuss] client won't start on second host
- Date: Sun, 22 Mar 2015 13:34:48 +0100
- List-archive: <http://lists.gforge.inria.fr/pipermail/cado-nfs-discuss/>
- List-id: A discussion list for Cado-NFS <cado-nfs-discuss.lists.gforge.inria.fr>
Dear Patrick,
The combination of
1- SSL certificate (can be disabled)
2- Python 2 on the client side (this is supposed to be supported, but
python 3 is preferred)
3- Client started by the main script (can be started by hand)
might have been only rarely tested.
With the hope to isolate a bit the problem, could you try again with only
some of 1-, 2-, or 3- ?
To disable SSL, try to pass server.ssl=no on the command-line.
Pierrick
On Fri, Mar 20, 2015 at 10:34:47AM -0400, Patrick R. St. wrote:
> Hello,
>
> I am trying to run a factorization with CADO-NFS on several machines, but
> it is not able to start the client on the second machine. Running CADO-NFS
> only on localhost works, my SSH config seems to be good and from what I
> know I followed the README instructions fine.
>
> The command I have run:
>
> ./factor.sh 1264140330139699975151910140167392338710257567267977216954497
> -h localhost,192.168.0.113
>
> And the error it outputs when it tries to connect to the other machine
> (CADO-NFS would still start to factor after with only localhost):
>
> Warning:Command: Process with PID 17969 finished with return code 1
>
> Warning:Client Launcher: Starting client on host 192.168.0.113 failed.
>
> Warning:Client Launcher: Stderr: INFO:root:Starting client 192.168.0.113
>
> INFO:root:Python version is 2.7.6
>
> INFO:root:Downloading certificate from andsto:8001
>
> Traceback (most recent call last):
>
> File "/home/xor/cado-nfs-2.1.1/scripts/cadofactor/wuclient2.py", line
> 1563, in <module>
>
> if not get_missing_certificate(certfilename, netloc,
> SETTINGS["CERTSHA1"]):
>
> File "/home/xor/cado-nfs-2.1.1/scripts/cadofactor/wuclient2.py", line
> 1347, in get_missing_certificate
>
> retrytime=retrytime)
>
> File "/home/xor/cado-nfs-2.1.1/scripts/cadofactor/wuclient2.py", line
> 1315, in get_ssl_certificate
>
> ca_certs=None)
>
> File "/usr/lib/python2.7/ssl.py", line 548, in get_server_certificate
>
> s.connect(addr)
>
> File "/usr/lib/python2.7/ssl.py", line 433, in connect
>
> self._real_connect(addr, False)
>
> File "/usr/lib/python2.7/ssl.py", line 420, in _real_connect
>
> socket.connect(self, addr)
>
> File "/usr/lib/python2.7/socket.py", line 224, in meth
>
> return getattr(self._sock,name)(*args)
>
> socket.gaierror: [Errno -2] Name or service not known
>
> Any idea what could be causing this? Thanks!
>
> _______________________________________________
> Cado-nfs-discuss mailing list
> Cado-nfs-discuss@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/cado-nfs-discuss
- [Cado-nfs-discuss] client won't start on second host, Patrick R. St., 03/20/2015
- Re: [Cado-nfs-discuss] client won't start on second host, Pierrick Gaudry, 03/22/2015
- [Cado-nfs-discuss] client won't start on second host, Patrick R. St., 03/25/2015
- Re: [Cado-nfs-discuss] client won't start on second host, Pierrick Gaudry, 03/22/2015
Archive powered by MHonArc 2.6.19+.