CADO-NFS error (exit code -6) - Page 2

EdH · 2020-08-21, 14:56

I swapped over to a newer commit (Aug 5) and remembered why I wasn't using it - It won't communicate properly with clients:

Code:

ERROR:root:Invalid workunit file: Error: key STDOUT not recognized

I wonder if this is a conflict between commits and clients have to be closer to the server, In which case, I won't be able to use later commits because I still have some Core2 machines. . .

RedGolpe · 2020-08-21, 15:12

It seems the good guys at INRIA are already looking into my report. They don't seem to require more information for now.

EdH · 2020-08-21, 16:20

I'll read the posts when I get my digest version. For now, I'm going to run my September commit and see what shows up later. I'll check the latest git again later on and see if the client communication issue has disappeared.

2020-08-21, 14:56	#12
EdH "Ed Hall" Dec 2009 Adirondack Mtns 3614₁₀ Posts	I swapped over to a newer commit (Aug 5) and remembered why I wasn't using it - It won't communicate properly with clients: Code: ERROR:root:Invalid workunit file: Error: key STDOUT not recognized I wonder if this is a conflict between commits and clients have to be closer to the server, In which case, I won't be able to use later commits because I still have some Core2 machines. . .

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CADO-NFS error (exit code -9)	RedGolpe	CADO-NFS	6	2020-09-01 12:29
Is there an error code listing for msieve?	EdH	Msieve	2	2019-11-14 22:58
CADO-NFS Square Root Error	Ferrier	CADO-NFS	3	2019-11-01 23:51
Error Code 40	storm5510	Software	19	2016-11-14 15:59
HRF3.TXT now has computer-id and error code	GP2	Data	2	2003-10-09 06:46

2020-08-21, 15:12	#13
RedGolpe Aug 2006 Monza, Italy 73 Posts	It seems the good guys at INRIA are already looking into my report. They don't seem to require more information for now.

2020-08-21, 16:20	#14
EdH "Ed Hall" Dec 2009 Adirondack Mtns 2·13·139 Posts	I'll read the posts when I get my digest version. For now, I'm going to run my September commit and see what shows up later. I'll check the latest git again later on and see if the client communication issue has disappeared.