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.
Red Hat Enterprise Linux 6 is in the Production 3 Phase. During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available.
The official life cycle policy can be reviewed here:
http://redhat.com/rhel/lifecycle
This issue does not meet the inclusion criteria for the Production 3 Phase and will be marked as CLOSED/WONTFIX. If this remains a critical requirement, please contact Red Hat Customer Support to request a re-evaluation of the issue, citing a clear business justification. Note that a strong business justification will be required for re-evaluation. Red Hat Customer Support can be contacted via the Red Hat Customer Portal at the following URL:
https://access.redhat.com/
keepalived segfaults on start when trying to load a config with a host{} section under an SMTP_CHECK block. This includes the sample config: # keepalived -nRCl -f /usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.SMTP_CHECK Starting Healthcheck child process, pid=10833 Initializing ipvs 2.6 Registering Kernel netlink reflector Registering Kernel netlink command channel Opening file '/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.SMTP_CHECK'. Healthcheck child process(10833) died: Exiting Stopping Keepalived v1.2.13 (10/15,2014) # grep 10833 /var/log/messages Mar 25 14:13:19 lb1 Keepalived[10832]: Starting Healthcheck child process, pid=10833 Mar 25 14:13:19 lb1 Keepalived_healthcheckers[10833]: Registering Kernel netlink reflector Mar 25 14:13:19 lb1 Keepalived_healthcheckers[10833]: Registering Kernel netlink command channel Mar 25 14:13:19 lb1 Keepalived_healthcheckers[10833]: Opening file '/usr/share/doc/keepalived-1.2.13/samples/keepalived.conf.SMTP_CHECK'. Mar 25 14:13:19 lb1 kernel: keepalived[10833]: segfault at 0 ip 0000000000432004 sp 00007fff6aee8a40 error 6 in keepalived[400000+49000] Mar 25 14:13:19 lb1 Keepalived[10832]: Healthcheck child process(10833) died: Exiting