Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
Apache crashes when installing 6.5 master+replica and 5.11 Client.
In discussing with Rob and team, it was decided to remove extra restart
Version-Release number of selected component (if applicable):
ipa-server-3.0.0-37.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. Used beaker to install the environment using quickinstall for QE tests
Actual results:
Crash is detetcted
Expected results:
No crash
Additional info:
Email from Rob:
I found this in /var/log/messages
May 19 09:13:34 pogolinux-01 setsebool: The httpd_can_network_connect
policy boolean was changed to on by root
May 19 09:13:34 pogolinux-01 setsebool: The httpd_manage_ipa policy
boolean was changed to on by root
May 19 09:13:35 pogolinux-01 kernel: httpd[19488]: segfault at 30 ip
00007f333682a7c7 sp 00007fffe606d050 error 4 in
libapr-1.so.0.3.9[7f3336816000+2b000]
May 19 09:13:35 pogolinux-01 kernel: httpd[19489]: segfault at 30 ip
00007f333682a7c7 sp 00007fffe606f6d0 error 4 in
libapr-1.so.0.3.9[7f3336816000+2b000]
May 19 09:13:35 pogolinux-01 kernel:
May 19 09:13:35 pogolinux-01 abrt[19523]: Not saving repeating crash in
'/usr/sbin/httpd'
May 19 09:13:36 pogolinux-01 abrt[19524]: Saved core dump of pid 19488
(/usr/sbin/httpd) to /var/spool/abrt/ccpp-2014-05-19-09:13:35-19488
(73166848 bytes)
May 19 09:13:36 pogolinux-01 abrtd: Directory
'ccpp-2014-05-19-09:13:35-19488' creation detected
My initial thought was that Apache was restarted in the middle of
initialization. Based on the core it looked like it blew up on a python
import. The ipareplica-install.log doesn't confirm this though. We
restart the server after configuring SELinux and that is what is
failing. Fortunately we restart it again a few steps later and that is
fine which is why the install is successful. While I wonder why it is
blowing up, it may mean we can drop an HTTP restart and save a few seconds.
One redundant restart was removed from ipa-replica-install.
Bug can be verified as SanityOnly, with just regression testing that
# ipa-replica-install
and
# ipa-replica-install --setup-ca
still work.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHSA-2015-0442.html