On Sun, 9 Oct 2016, Ruediger Pluem wrote:
On 10/08/2016 09:28 PM, Niklas Edmundsson wrote:
Hi all.
httpd 2.4.23, built from httpd-2.4.23.tar.bz2 and httpd-2.4.23-deps.tar.bz2 on
Ubuntu 14.04.5 LTS (trusty).
While fiddling with enabling https on ftp.acc.umu.se I stumbled on the
following coredump when reloading the server with
-k graceful after renewing/updating the certificate. Has anyone seen anything
like it before? I'm at a loss figuring out
which end I should start prodding to make sense of this...
frame 0 of the coredump seems to be garbage, and I can't find any obvious NULL
pointer or similar in frame 1...
<snip>
What are the values of
mc->stapling_cache
mc->stapling_cache->init
(gdb) p mc->stapling_cache->init
$2 = (apr_status_t (*)(ap_socache_instance_t *, const char *,
const struct ap_socache_hints *, server_rec *, apr_pool_t *)) 0x0
Gaah. I was obviously too tired when I looked into this :/
Anyhow, I think I know what lead to this as well.
- I was testing the https httpd.conf file by copying it to an offlined
frontend machine.
- Between me copying it there and cert-update/reload happening it got
overwritten by the maintenance task syncing the configs of all
frontends to our default config.
- As our old default config only loaded mod_ssl.so, and NOT
mod_socache_shmcb.so, it makes sense to find a NULL pointer there.
So, the config was definitely broken on reload. Would have been nice
if it had barfed in a more polite way than segfault though ;-)
/Nikke
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ {acc,hpc2n}.umu.se | [email protected]
---------------------------------------------------------------------------
"My pride has had terrible consequences for the galaxy." - Obi-Wan
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
