Error when opening workflow as Job on Server

[frapas31]

Hi,

I’m facing this error when I try opening a workflow as a job on Server:

Error occurred while loading workflow into memory: An error occurred during the creation of a job for ‘/Users/xxxxuser/test/test_connection’: Could not extract workflow archive ‘http://xxxxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data’ for da9d95c4-958a-48cf-8f85-24e49e63db1b: Server returned HTTP response code: 502 for URL: http://xxxxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data

This error happens every time I open a workflow as a Job after the first opening (that runs ok).

I’m on KNIME AP 4.6 connected on HTTPS Port 8443 to a KNIME Server 4.15 and Executor 4.6.0.

What can I do? Thanks.

Regards.

[thor]

This error seems to come from the executor meaning that it’s not able to load the workflow from server. The “502” error indicates that there is something between the executor and the server (proxy, firewall, …) that intercepts the request. Without knowing more about your setup and log files this is hard to diagnose, though.

[frapas31]

Server is LARGE and installed on a single node.
That’s what my KNIME Executor Log says:

ERROR pool-4-thread-2 LoadWorkflowTask Could not extract workflow archive ‘http://xxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data’ for da9d95c4-958a-48cf-8f85-24e49e63db1b: Server returned HTTP response code: 502 for URL: http://xxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data
java.io.IOException: Server returned HTTP response code: 502 for URL: http://xxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at com.knime.enterprise.executor.amqp.actions.LoadWorkflowTask.prepareWorkflow(LoadWorkflowTask.java:361)
at com.knime.enterprise.executor.amqp.actions.LoadWorkflowTask.loadWorkflow(LoadWorkflowTask.java:172)
at com.knime.enterprise.executor.amqp.actions.LoadWorkflowTask.lambda$0(LoadWorkflowTask.java:130)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)
ERROR pool-4-thread-3 LoadWorkflowTask Could not extract workflow archive ‘http://xxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data’ for cc32991b-38bf-49c7-8165-54b696c9ffb8: Server returned HTTP response code: 502 for URL: http://xxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data
java.io.IOException: Server returned HTTP response code: 502 for URL: http://xxxx:8080/knime/rest/v4/repository/Users/xxxxuser/test/test_connection:data
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream0(Unknown Source)
at java.base/sun.net.www.protocol.http.HttpURLConnection.getInputStream(Unknown Source)
at com.knime.enterprise.executor.amqp.actions.LoadWorkflowTask.prepareWorkflow(LoadWorkflowTask.java:361)
at com.knime.enterprise.executor.amqp.actions.LoadWorkflowTask.loadWorkflow(LoadWorkflowTask.java:172)
at com.knime.enterprise.executor.amqp.actions.LoadWorkflowTask.lambda$0(LoadWorkflowTask.java:130)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.base/java.lang.Thread.run(Unknown Source)

Please let me know if I can provide further informations, thanks.

[marvin_kickuth]

Hi @frapas31,

thanks for sharing the executor log file. We probably still need to dig deeper into the setup – maybe the server’s canonical address and proxy rules cause the executor to access it via a proxy, even though it is running locally.
I suggest opening a support ticket by sending a mail to support@knime.com. Ideally, you could link to this forum thread and grab a set of log files from the server (WebPortal → Monitoring → Logs) so that we can get right to it. It would also be interesting to know how the update to 4.15 was performed.

Kind regards
Marvin