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:
xinetd attempts to open sockets with PF_INET6 by default, even on systems with IPv6 module disabled ('options ipv6 disabled=1' in /etc/modprobe.d/*)
This causes xinetd to kill long running clients with xinetd is reloaded because xinetd appears to believe the config has changed for the service.
Version-Release number of selected component (if applicable):
xinetd-2.3.14-39.el6_4.x86_64
How reproducible:
100%
Steps to Reproduce:
1. enable telnet, or some other connection service in xinetd
2. disable IPv6 (blacklist the module, or options ipv6 disabled=1)
3. reboot
4. telnet (or connect to enabled service)
5. send SIGHUP (or 'service xinetd reload')
Actual results:
telnet connection is dropped because the telnet process receives SIGKILL
Expected results:
telnet connection stays up because telnet config didn't change
Additional info:
IPv6 by default was added in https://bugzilla.redhat.com/show_bug.cgi?id=195265
It looks like now if IPv6 is disabled xinetd gets confused thinking the running config doesn't match the defined service and will always send a SIGKILL (would send SIGTERM if the service were type = INTERNAL). This is not desired behavior as the telnet (or whatever defined service) configuration has not changed.
Clarification was added to the man pages via: https://bugzilla.redhat.com/show_bug.cgi?id=1075152 but that misses the point. The work-around would be to set 'flags = IPv4' to the service or 'bind = 0.0.0.0' to the main xinetd.conf (as documented on our portal: https://access.redhat.com/solutions/706163 ) Maybe that should be added to the man page, as it is more relevant...
However customer feels that xinetd should handle this situation gracefully
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/RHBA-2016-0851.html
Description of problem: xinetd attempts to open sockets with PF_INET6 by default, even on systems with IPv6 module disabled ('options ipv6 disabled=1' in /etc/modprobe.d/*) This causes xinetd to kill long running clients with xinetd is reloaded because xinetd appears to believe the config has changed for the service. Version-Release number of selected component (if applicable): xinetd-2.3.14-39.el6_4.x86_64 How reproducible: 100% Steps to Reproduce: 1. enable telnet, or some other connection service in xinetd 2. disable IPv6 (blacklist the module, or options ipv6 disabled=1) 3. reboot 4. telnet (or connect to enabled service) 5. send SIGHUP (or 'service xinetd reload') Actual results: telnet connection is dropped because the telnet process receives SIGKILL Expected results: telnet connection stays up because telnet config didn't change Additional info: IPv6 by default was added in https://bugzilla.redhat.com/show_bug.cgi?id=195265 It looks like now if IPv6 is disabled xinetd gets confused thinking the running config doesn't match the defined service and will always send a SIGKILL (would send SIGTERM if the service were type = INTERNAL). This is not desired behavior as the telnet (or whatever defined service) configuration has not changed. Clarification was added to the man pages via: https://bugzilla.redhat.com/show_bug.cgi?id=1075152 but that misses the point. The work-around would be to set 'flags = IPv4' to the service or 'bind = 0.0.0.0' to the main xinetd.conf (as documented on our portal: https://access.redhat.com/solutions/706163 ) Maybe that should be added to the man page, as it is more relevant... However customer feels that xinetd should handle this situation gracefully