Bug 162080
Summary: | dhclient running amock and filling /var/log/messages | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Gilles Detillieux <grdetil> |
Component: | dhcp | Assignee: | Jason Vas Dias <jvdias> |
Status: | CLOSED ERRATA | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | sundaram |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | 3.0.1-44_FC3 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-09-05 08:18:01 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Gilles Detillieux
2005-06-29 19:08:53 UTC
The problem is caused by an incorrect SELinux security context for /sbin/dhclient-script - it somehow ended up with a context that did not allow it to link to the dynamic loader library, and the execve of dhclient-script therefore exited with an error. This does not occur with the default selinux-policy-targeted RPM. When dhclient-script exits with an error, then dhclient assumes the new configuration parameters were rejected due to local policy, and sends a DHCPDECLINE to the server, and then starts off a new configuration session from the initial state, sending a DHCPDISCOVER. With the latest dhcp-3.0.1-40_EL3 version in RHEL-3, fixing bug 159929, dhclient will wait a random time between 1 and 15 seconds before entering the initial state after a DHCPDECLINE is sent. The "null pointer" message is harmless - when a DHCPDECLINE occurs, the code would attempt free-ing the lease structure memory twice, which is detected by the allocation code and causes no problems - just the error message. This multiple free attempt is also removed from the code with dhcp-3.0.1-40_EL3. I am now applying the changes to the FC-3 branch and will be issuing an FC-3 update for dhcp-3.0.1-44_FC3 today . This bug is now fixed with the dhcp-3.0.1-44_FC3, today released as FC3 update 546, and available from ftp://download.fedora.redhat.com:/pub/fedora/linux/core/updates/3/i386 Please try it out and let me know of any issues - thank you. |