After an update to Fedora (which updated the openjdk environment) OpenMeetings would no longer start via the systemd service script, but it would start via the command line.

Looking in <OpenMeetingsLogDir>/catalina.out showed the java machine was not found.

Traced this to the line in the .service file:

Environment=JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64

Changed it to:

Environment=JAVA_HOME=/usr/lib/jvm/java-11-openjdk-11.0.11.0.9-0.fc34.x86_64

Then OpenMeetings was again able to start from systemd.


Attachment: OpenPGP_signature
Description: OpenPGP digital signature

Reply via email to