https://bz.apache.org/bugzilla/show_bug.cgi?id=66005
--- Comment #11 from Rainer Jung <rainer.j...@kippdata.de> ---
It seems the crash happens in the second parent during the Apache startup. On
Unix/Linux Apache creates a first parent, then replaces it by another parent
and then starts the children. The first parent validates both workers without
crash. Then the pid changes and the second parent starts, which crashes.
The pool "jk_apr_pool" in common/jk_connect.c is static and only initialized,
if it is NULL. I think we use the Apache pconf pool as the parent pool. I added
debug logging lines and both parents seem to ahve the same address for pconf
and both parents create a new fresh jk_apr_pool in my system. So I see no
reason for a crash and indeed on my system it doesn't crash.
Some questions:
Am I right this happens immediately during the web server startup attempt?
Are you starting with requests immediately hitting the web server?
If so, can you retry with the web server not receiving any requests during
startup?
What MPM are you using?
What exact Apache version?
What exact APR version?
Apache and/or APR self-compiled or Linux Distro provided.
Linux Distro RHEL 8?
Since this seems to happen early during startup, could you strip down your
config to not use any other 3rd-party modules (like mod_security, PHP etc.)
just to do another crash check?
A simple patch that adds a few log lines that help us verify, that the pool
lifecycle on your system doesn't differ from mine:
diff -u common/jk_connect.c.kpdt_orig common/jk_connect.c
--- common/jk_connect.c.kpdt_orig 2022-04-15 00:34:15.139451326 +0200
+++ common/jk_connect.c 2022-04-15 00:32:54.311258693 +0200
@@ -416,10 +416,15 @@
apr_sockaddr_t *remote_sa, *temp_sa;
if (!jk_apr_pool) {
+ jk_log(l, JK_LOG_ERROR, "Creating jk_apr_pool from main pool %pp",
pool);
if (apr_pool_create(&jk_apr_pool, (apr_pool_t *)pool) !=
APR_SUCCESS) {
+ jk_log(l, JK_LOG_ERROR, "Failed creating jk_apr_pool from main
pool %pp", pool);
JK_TRACE_EXIT(l);
return JK_FALSE;
}
+ jk_log(l, JK_LOG_ERROR, "Created jk_apr_pool %pp from main pool
%pp", jk_apr_pool, pool);
+ } else {
+ jk_log(l, JK_LOG_ERROR, "Reusing jk_apr_pool %pp, main pool %pp",
jk_apr_pool, pool);
}
apr_pool_clear(jk_apr_pool);
if (apr_sockaddr_info_get(&remote_sa, host, APR_UNSPEC,
(apr_port_t)port,
This will add log lines like:
[Fri Apr 15 00:43:19.335 2022] [10189:140241031051136] [error]
jk_resolve::jk_connect.c (419): Creating jk_apr_pool from main pool 0x797478p
[Fri Apr 15 00:43:19.335 2022] [10189:140241031051136] [error]
jk_resolve::jk_connect.c (425): Created jk_apr_pool 0x81bfd8p from main pool
0x797478p
[Fri Apr 15 00:43:19.343 2022] [10189:140241031051136] [error]
ajp_validate::jk_ajp_common.c (2868): worker node1 can't resolve tomcat address
unknown.example.com
[Fri Apr 15 00:43:19.344 2022] [10189:140241031051136] [error]
jk_resolve::jk_connect.c (427): Reusing jk_apr_pool 0x81bfd8p, main pool
0x797478p
[Fri Apr 15 00:43:19.344 2022] [10189:140241031051136] [error]
ajp_validate::jk_ajp_common.c (2868): worker node2 can't resolve tomcat address
unknown.example.com
[Fri Apr 15 00:43:19.359 2022] [10192:140241031051136] [error]
jk_resolve::jk_connect.c (419): Creating jk_apr_pool from main pool 0x797478p
[Fri Apr 15 00:43:19.359 2022] [10192:140241031051136] [error]
jk_resolve::jk_connect.c (425): Created jk_apr_pool 0x7c8788p from main pool
0x797478p
[Fri Apr 15 00:43:19.359 2022] [10192:140241031051136] [error]
ajp_validate::jk_ajp_common.c (2868): worker node1 can't resolve tomcat address
unknown.example.com
[Fri Apr 15 00:43:19.360 2022] [10192:140241031051136] [error]
jk_resolve::jk_connect.c (427): Reusing jk_apr_pool 0x7c8788p, main pool
0x797478p
[Fri Apr 15 00:43:19.360 2022] [10192:140241031051136] [error]
ajp_validate::jk_ajp_common.c (2868): worker node2 can't resolve tomcat address
unknown.example.com
Thanks and regards,
Rainer
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
