Subject: Karaf generated systemd unit file failure with RHEL 7.7


Apologies if this has been reported, but I could not find any references.

The systemd unit file has recently begun being reported as failing with the RHEL 7.7 updates. The service does start but systemd thinks it has failed.
Also, the `systemctl stop karaf.service` action is failing to stop the service.

Based on the logged messages:

Sep 10 18:24:13 ********.andrew.cmu.edu systemd[1]: Starting karaf...
Sep 10 18:24:13 ********.andrew.cmu.edu su[63432]: (to esbadmin) root on none
Sep 10 18:24:13 ********.andrew.cmu.edu karaf-service[63396]: Starting karaf...
Sep 10 18:24:13 ********.andrew.cmu.edu systemd[1]: New main PID 63464 does not belong to service, and PID file is not owned by root. Refusing.
Sep 10 18:24:13 ********.andrew.cmu.edu systemd[1]: New main PID 63464 does not belong to service, and PID file is not owned by root. Refusing.
Sep 10 18:24:13 ********.andrew.cmu.edu systemd[1]: Failed to start karaf.
Sep 10 18:24:13 ********.andrew.cmu.edu systemd[1]: Unit karaf.service entered failed state.
Sep 10 18:24:13 ********.andrew.cmu.edu systemd[1]: karaf.service failed.

My guess is this has to do with RUN_AS_USER in ./bin/karaf-service script which is called by the unit file.

Is anyone investigating this?

Thanks,

-Charles