On 14/05/2026 07:50, Loquens, Ladislav (Trask solutions a.s.) wrote:
Hello Mark and team,

I would like to kindly inquire about the fix for the Tomcat Daemon issue 
mentioned below - 
https://github.com/apache/commons-daemon/commit/36bdde050c5c27c113f2a194ab8844f0fd79e92f.
 I have been informed that the issue will be resolved in Tomcat Daemon 1.5.2, 
yet the latest Tomcat releases (9.0.118, 10.1.55) still include the old Daemon 
version 1.5.1 (since 9.0.115).

Could you please let me know when Tomcat with Daemon 1.5.2 will be released?

Once Commons Daemon 1.5.2 has been released. And no, before you ask, there is no planned date for that release at the moment.

Mark


Thank you very much. Best regards,

Ladislav



INTERNAL
-----Original Message-----
From: Mark Thomas <[email protected]>
Sent: Tuesday, March 24, 2026 9:33 AM
To: [email protected]
Subject: [SA-DKIM Failure] Re: daemon.sh scritp wrote lock PID error since 
Tomcat 9.0.115 version

https://github.com/apache/commons-daemon/commit/36bdde050c5c27c113f2a194ab8844f0fd79e92f

Will be included in Daemon 1.5.2

Mark


On 24/03/2026 08:29, Loquens, Ladislav (Trask solutions a.s.) wrote:


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: [email protected] For
additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected] For additional 
commands, e-mail: [email protected]

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to