I am unable to run the workflow after upgrading analytics to 4.3 and it is giving no conda environment
Could you check if in the executor.epf you have the correct path to the conda environment?
What server version you had previously to the upgrade?
Any news on this? Any way I could help you?
Right now it is working by creating the executor.epf file in the executor directory of server repositary
Perfect! Glad to know.
I am currently clean reinstalling our server from 4.10.3 to 4.12.1 and since a week I am constantly failing to get conda run in the KNIME server. I was trying to follow the KNIME Python Integration Guide
Usually, we are using Miniconda 3, so I don’t know if that is a problem, since in one error message I got written Anaconda3 from KNIME even if the system has never heard from Anaconda before.
My miniconda (I am also trying anaconda3 now) just works fine if I use it in the console as knime user, but as soon as the KNIME server should use it … Since I can only access the server via console I tried the manual way and always end up with "no conda environment in the node “Conda environment propagation”, even if the configuration of the node shows me my environments with the packages just fine. Switching the preferences from manual to conda also does not help. I am not sure why starting scripts are needed, if the user knime can just use “conda”. But with those I had also no success.
Is the manual still up to date? Anaconda seems to use in the new version (Installing in silent mode — Anaconda documentation) to use
eval "$(/Users/jsmith/anaconda/bin/conda shell.YOUR_SHELL_NAME hook)"
Any help is appreciated, I am totally lost. Hopefuly its just a simple thing:
When I am switching from manual to conda in the preferences, I link to the environments directly.
Thanks a lot!
several weeks ago I had the same issue. A solution can be found in this thread: click here.
Thanks a lot Sven, I think your solution is refering to special Python nodes. I am just using the normal KNIME Python nodes and hopefully in the current version 4.12.1 it is fixed already. However, I realized that you set the Python path for python 2 and 3 and did the same - just in case that would do the trick - but didn’t help:
However, I would expect, that the Python executable is taken from the environment - maybe I am misunderstanding something here.
hi lars (@laval),
here is my section of the *.epf-File. Looks like yours in the Python configuration.
thank you and ja, that part looks the same. But on the KNIME server it is just not working for me. In the local Linux I have no problem with that. I tried now all I could think of and guess I am missing something. Maybe KNIME can check with me via Screensharing.
I already sent you a message to set up a meeting.
In order it is interesting for others, I would like to follow up on that issue. Michael found the problem on my server right away and it was different to what I expected:
I am changing from KNIME server 4.10.3 to 4.12.2 and did not realise, that the executor needs to receive the Python settings in a new way via the client-settings feature. After all of that was set up the Python-workflows worked as expected.
Thanks a lot Michael!
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.