daemon.sh scritp wrote lock PID error since Tomcat 9.0.115 version

[Loquens, Ladislav (Trask solutions a.s.)]

Hello,
we are using Apache Tomcat version 9 on Red Hat Linux with compiled Apache 
daemon (jsvc) + Java 17 Temurin.
Since Tomcat version 9.0.115 (and version 9.0.116) the start command wrote an 
lock PID file error (also the Tomcat server start successful):

/opt/tomcat/tomcat_current/bin/daemon.sh --java-home /opt/java/java_current 
--catalina-base /opt/tomcat/servers/SAMPLE --tomcat-user tuser start
wait_child: Failed to lock PID file 
[/opt/tomcat/servers/SAMPLE/logs/catalina-daemon.pid] with file descriptor [3] 
for reading due to [9]

The stop command doesn't work (tomcat is still running) and wrote the same lock 
PID file error:

/opt/tomcat/tomcat_current/bin/daemon.sh --java-home /opt/java/java_current 
--catalina-base /opt/tomcat/servers/SAMPLE --tomcat-user tuser stop
get_pidf: Failed to lock PID file 
[/opt/tomcat/servers/SAMPLE/logs/catalina-daemon.pid] with file descriptor [3] 
for reading due to [9]

The same start/stop commands run successful without any issues on version 
9.0.113 (and older).
The access right on filesystem are set correct - tuser have read/write 
permissions.
We are using the different CATALINA_HOME (/opt/tomcat/tomcat_current) and 
CATALINA_BASE (/opt/tomcat/servers/SAMPLE) for many different Tomcat instances.

Could you please check the daemon.sh/jsvc in version 9.0.115 (and newer) or 
help me know what I am wrong?

Thank you very much, best regards,

Ladislav


INTERNAL

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org