The external Python process crashed for unknown reasons

[eddy0620]

Hi,
I used knime to loop start to create some plots with python script, but it crashed as below.
How to fix this issue?

The external Python process crashed for unknown reasons while KNIME set up the Python environment. See log for details.
2022-12-06 08:46:33,105 : ERROR : KNIME-Worker-194-Python Script 5:2314 : : Node : Python Script : 5:2314 : Execute failed: The external Python process crashed for unknown reasons while KNIME set up the Python environment. See log for details.

org.knime.python2.kernel.PythonIOException: The external Python process crashed for unknown reasons while KNIME set up the Python environment. See log for details.

at org.knime.python2.kernel.Python2KernelBackend.(Python2KernelBackend.java:357)

at org.knime.python2.kernel.Python2KernelBackendFactory.createBackend(Python2KernelBackendFactory.java:66)

at org.knime.python2.kernel.PythonKernelQueue$KeyedPooledPythonKernelFactory.createKernel(PythonKernelQueue.java:407)

at org.knime.python2.kernel.PythonKernelQueue$KeyedPooledPythonKernelFactory.populateHolder(PythonKernelQueue.java:396)

at org.knime.python2.kernel.PythonKernelQueue$KeyedPooledPythonKernelFactory.passivateObject(PythonKernelQueue.java:390)

at org.knime.python2.kernel.PythonKernelQueue$KeyedPooledPythonKernelFactory.passivateObject(PythonKernelQueue.java:1)

at org.apache.commons.pool2.impl.GenericKeyedObjectPool.returnObject(GenericKeyedObjectPool.java:483)

at org.knime.python2.kernel.PythonKernelQueue.lambda$1(PythonKernelQueue.java:318)

at java.base/java.lang.Thread.run(Unknown Source)

Caused by: java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Accept timed out

at java.base/java.util.concurrent.FutureTask.report(Unknown Source)

at java.base/java.util.concurrent.FutureTask.get(Unknown Source)

at org.knime.python2.kernel.Python2KernelBackend.(Python2KernelBackend.java:351)

… 8 more

Caused by: java.net.SocketTimeoutException: Accept timed out

at java.base/sun.nio.ch.NioSocketImpl.timedAccept(Unknown Source)

at java.base/sun.nio.ch.NioSocketImpl.accept(Unknown Source)

at java.base/java.net.ServerSocket.implAccept(Unknown Source)

at java.base/java.net.ServerSocket.platformImplAccept(Unknown Source)

at java.base/java.net.ServerSocket.implAccept(Unknown Source)

at java.base/java.net.ServerSocket.implAccept(Unknown Source)

at java.base/java.net.ServerSocket.accept(Unknown Source)

at java.base/java.util.concurrent.FutureTask.run(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)

at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

… 1 more

[eddy0620]

when I try to create new python2 environment it still alarm as below:

[mlauber71]

@eddy0620 could you provide us with some more information about your system and knime version? Also a log file in debug mode:

Files Corrupted During File Transfer

@djarrett I could not initially find any problems. You could get rid of the vernalis error messages by installing RDKit. Could you create a LOG in DEBUG mode? Open the existing log and delete the content: [image] or delete the file from the workspace directory {workspace_directory}/.metadata/knime/knime.log activate the DEBUG level. Make sure that it would not contain any sensitive informations and remember to set it back to WARN after you are finished: [image] You might want to include f…

Then: has this job ever run successfully or does it Airways crash. Is it possible to provide a minimal example where this crash happens without spelling any secrets?

Then a new knime version 4.7 with much improved python support is about to be released this week. It could be worth to try that also.

The name "python2“ in three knime path error message has nothing to do with the old Python 2 version. I think it will get renamed. You are right to stick to Python 3 except if you explicitly know that you need a very special old version.