KNIME Server Error : RabbitMQHandler could not acquire enough core tokens from server

[AnotherFraudUser]

Hi,

after upgrading our small KNIME Server from 4.10 → 4.12 I cannot manage to start the Executor.
I get the
Executor> ERROR main RabbitMQHandler Could not acquire enough core tokens from server, quitting

Not quite sure why RabiitMQHandler is startet - as we do not want to setup distributed KNIME Executors

I set the knime-server.config parameter:
om.knime.enterprise.executor.embedded-broker= to true

As well as using:
-Dorg.knime.core.maxThreads=4
in the Executor .ini

KNIME Server Error : RabbitMQHandler could not acquire enough core tokens from server

Hi KNIME, I have tried to build up the Distributed Executors in accordance with the instruction : https://docs.knime.com/2018-12/server_admin_guide/index.html#knime-server-distributed-executors. However, I met an error that is “Executor> ERROR main RabbitMQHandler Could not acquire enough core tokens from server, quitting” on the way to start the executor manually. [2019-08-21_13-14-50] The KNIME server, RabbitMQ, and Executor were installed in one same machine with a partner license. Ho…

Thanks in advance for the support

[marten_kose]

Can you check the executor’s knime.ini for -Dcom.knime.enterprise.executor.msgq= parameter?

[AnotherFraudUser]

I have
com.knime.enterprise.executor.msgq=amqp://knime:20knime16@localhost:5672/

and also tried without

[AnotherFraudUser]

The Execotor .ini is as follows:

-startup
plugins/org.eclipse.equinox.launcher_1.5.700.v20200207-2156.jar
–launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.1100.v20190907-0426
-vm
plugins/org.knime.binary.jre.linux.x86_64_1.8.0.252-b09/jre/bin
executor
-vmargs
-server
-Dsun.java2d.d3d=false
-Dosgi.classloader.lock=classname
-XX:+UnlockDiagnosticVMOptions
-XX:+UnsyncloadClass
-XX:+UseG1GC
-Dsun.net.client.defaultReadTimeout=0
-XX:CompileCommand=exclude,javax/swing/text/GlyphView,getBreakSpot
-Xmx8g
-Dorg.eclipse.swt.internal.gtk.disablePrinting
-Darrow.enable_unsafe_memory_access=true
-Darrow.memory.debug.allocator=false
-Darrow.enable_null_check_for_get=false
-Djava.net.useSystemProxies=true

Server Config in:
/workflow_repository/config/knime-server.config is:
com.knime.enterprise.executor.embedded-broker=true <–also tested with false
com.knime.server.authentication.preferredType=Credentials
com.knime.server.authentication.types=Credentials
com.knime.server.canonical-address=http://serverIP:8080/
com.knime.server.executor.knime_exe=path_to_executor/knime
com.knime.server.config.watch=true
com.knime.server.default_mount_id=knime-server
com.knime.server.server_admin_groups=admin
com.knime.server.server_admin_users=knimeadmin
com.knime.server.webportal.disable_warning_messages=true

when removing all entries of:
com.knime.enterprise.executor.msgq=amqp://knime:20knime16@localhost:5672/
there is no error anymore and the executor runs…but also there is no connection between server and executor

->Server and WebPortal run okay

[marten_kose]

In knime-server.config, keep com.knime.enterprise.executor.embedded-broker=true

And in knime.ini add -Dcom.knime.enterprise.executor.msgq=amqp://knime:20knime16@localhost/

Also make sure executor starts after the server, otherwise the built in message queue won’t be available

[AnotherFraudUser]

Hi @Marten_Pfannenschmidt ,

thanks for the help!
Solution seems to be:

-Dhttp.proxyHost=proxyHost
-Dhttp.proxyPort=8800
-Dhttp.proxyUser=proxyUser
-Dhttp.proxyPassword=proxyPass
-Dhttps.proxyPort=8080
-Dhttps.proxyHost=proxyHost
-Dhttps.proxyUser=proxyUser
-Dhttps.proxyPassword=proxyPass
-Dhttp.nonProxyHosts=“localhost|127.0.0.1|serverIP”
-Dhttps.nonProxyHosts=“localhost|127.0.0.1|serverIP”

As well as changing the canonical-addres to:
com.knime.server.canonical-address=http://localhost:8080/

so the communication is not blocked by the company proxy