Rather frequently, apache will coredump on one of my Fedora systems. The system in question is a PC-Engines APU2. The journald entries are: Dec 08 02:52:16 systemd-coredump[748]: Process 743 (httpd) of user 0 dumped core. Stack trace of thread 743: #0 0x00007f82989e16b0 ldap_url_parse_ext (libldap_r-2.4.so.2) #1 0x00007ffc871c6c78 n/a (n/a) Dec 08 02:52:16 systemd-coredump[747]: Process 745 (httpd) of user 0 dumped core. Stack trace of thread 745: #0 0x00007f82989e16b0 ldap_url_parse_ext (libldap_r-2.4.so.2) #1 0x00007ffc871c6c78 n/a (n/a) This will repeat until I manually issue 'systemctl restart httpd'. Today, I hit ~348 core dumps in /var/lib/systemd/coredump
Can you get a complete backtrace from the core dump? Please give the LDAP configuration.
Hi, I do have a saved backtrace. Am I able to email it to you directly? I'm not sure if it will have any confidential information within it...
Yes please do!
Core wasn't very useful... thanks for providing it. Can you reproduce with latest httpd still? If so please provide rpm -qf /etc/httpd/modules/*.so | sort -u If you have php installed this might be bug 1680481.
You might well be on to something there: # rpm -qf /etc/httpd/modules/*.so | sort -u httpd-2.4.38-2.fc29.x86_64 mod_http2-1.11.1-1.fc29.x86_64 mod_ssl-2.4.38-2.fc29.x86_64 php-7.2.15-1.fc29.x86_64 # rpm -qa | grep php- | sort php-7.2.15-1.fc29.x86_64 php-cli-7.2.15-1.fc29.x86_64 php-common-7.2.15-1.fc29.x86_64 php-fedora-autoloader-1.0.0-4.fc29.noarch php-fpm-7.2.15-1.fc29.x86_64 php-gd-7.2.15-1.fc29.x86_64 php-imap-7.2.15-1.fc29.x86_64 php-json-7.2.15-1.fc29.x86_64 php-ldap-7.2.15-1.fc29.x86_64 php-mbstring-7.2.15-1.fc29.x86_64 php-pdo-7.2.15-1.fc29.x86_64 php-pear-CAS-1.3.6-1.fc29.noarch php-pecl-imagick-3.4.3-8.fc29.x86_64 php-Smarty3-3.1.18-2.el7.centos.noarch php-Smarty3-gettext-1.1.0-2.el7.centos.noarch php-xml-7.2.15-1.fc29.x86_64
OK, if you're also using prefork then this may be the same issue - please try the packages linked from bug 1680481 comment 15 and see if that helps.
From the symptoms, I'm going to guess that this is one and the same issue. I'm happy to close as DUPLICATE for the moment - and if this turns out not to be the case, I'll reopen this report with whatever further I can gather. I did install the packages you mentioned earlier, and I haven't seen a crash since, but it seemed to be randomly triggered - so I don't have a 100% reproducible case other than observing over time... It isn't a busy web server on that system.
*** This bug has been marked as a duplicate of bug 1680481 ***