Error The platform metadata area could not be written: /opt/knime_workspace/.metadata

Hola,

Estoy instalando knime server y knime executor y al arrancar el executor no consigo que arranque. He mirado los logs que me está generando en /opt/knime_executor/configuration y he visto el siguiente mensaje de error:

!MESSAGE FrameworkEvent ERROR

java.lang.IllegalStateException: The platform metadata area could not be written: /opt/knime_workspace/.metadata

¿A qué se debe? ¿Cómo pudo coregirlo?

Muchas gracias de antemano

Hi @gonzalfb Welcome to the KNIME Community Forum!

Can you let us know the OS type and version of the machine where you installed your KNIME Server?

First, your should check the /opt/knime_workspace/.metadata folder mentioned in the error if it exists and/or what permissions these folders have.

Also note that separate workspaces need to be configured for the KNIME Server and its Executor, can you check in case you have configured both workspaces into one (/knime_workspace)? Workspaces can be configured in the executor’s service (within install-executor-as-service.bat on Windows, or override.conf on Linux accessible via $systemctl edit knime-executor.service).

Hi Dora,

The machine where I have installed linux is: SUSE Linux Enterprise Server 15 SP4.

The /opt/knime_workspace/.metadata folder exists and it has the following permissions
image

Regarding the workspace configuration this is what I have in both service configuration for the server and the executor.

Server:


Executor:

Is there anything incorrect or missing in my configuration?

Thank you for your help.

Hi @gonzalfb
Thank you for the screenshots. Can you try changing the owner and owner group of /opt to knime:users, same as seen on /opt/knime_workspace in your first screenshot? Users at the moment might not have execute rights, causing your !MESSAGE FrameworkEvent ERROR.

Hi Dora,

Thank you for your fast reply and your help. The owner and owner group of /opt should be root. I have another installation of knime on another server and the owner and owner group of /opt is root and everything is working correctly. I don’t think this is what is causing the issue. There has to be some configuration that I have missed or not configured properly. However, I have checked all the possible configuration files I could think of and I can’t figure out where the issue is…

Hi @gonzalfb
Can I ask where your executor workspace is located on your other installation? Is it also under /opt ?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.