I’m playing around with a server trial on a Azure VM and really struggle to make it work.
The deployment went fine, I can connect to the web portal, but when I try to run an example workflow, I get a “RMI executor could not be started”. Hmm, ok? So the forum suggest to update the server to 4.10+ (the azure deployment is 4.9.2), fine…
The KNIME Server (KS) would only be configured as a service if you had followed the installation documentation [1] to do so; otherwise, after completing installation, the installer will run the startup script (see “Starting/stopping KNIME Server” on that same documentation page) after completing installation.
So, if you’re not seeing TomEE as a dedicated service, then that may be why. Please check if it was configured for autostart, and proceed accordingly.
Thank you for your follow-up on this issue. I’m glad that you were able to get it working. I agree, sometimes some of the configuration pieces in Linux/UNIX aren’t always obvious, but once you learn how they work, you can readily apply them in other environments.
I have created a feature request, designated [SRV-3008], for an option in the installer to detect OS/distro and configure the runlevel/service scripts automatically.
If you have any other questions, please let us know, and good work completing the upgrade!