Bug 138869 - dhcp dumping code to screen during boot
Summary: dhcp dumping code to screen during boot
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: dhcp   
(Show other bugs)
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Jason Vas Dias
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2004-11-11 18:16 UTC by Ronan Kirby
Modified: 2013-10-20 22:46 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-01-13 18:19:54 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Ronan Kirby 2004-11-11 18:16:15 UTC
Description of problem:
During the boot process when it is bringing up the network interfaces
and, is paused waiting for a response from the dhcp server, if the
network connection drops (i.e. cable is removed) a short time later a
large amount of code/script is dumped to screen. It then displays
'Usage: ping' and the normal output of 'ping --help' before resuming
the boot process.

This does not appear in syslog etcetera. However it looks like
sections of /etc/sysconfig/network-scripts/network-functions

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Set eth0 to use dhcp and activate at boot
2. Reboot
3. As its trying to bring up eth0, remove network cable
4. Wait briefly

Actual Results:  Large amounts of script dumped to screen, then boot

Expected Results:  Notification of failure to bring up interface (i.e.
red [FAILED]).

Comment 1 Jason Vas Dias 2004-11-16 18:41:24 UTC
 If an existing unexpired lease exists in 
 /var/lib/dhcp/dhclient-$IF.leases, and a DHCPDISCOVER to the
 dhcp server times out, the dhclient-script attempts to ping 
 the default router specified in the last current lease; if this
 fails (eg. because network cable is now unplugged), it correctly
 exits and the red [ FAILED ] status does appear, with no ping usage
 message on the console; otherwise it will re-use the unexpired lease. 
 If an unexpired lease exists, and your dhcp-server did not supply an
 "routers" option with the unexpired lease, the dhclient-script will 
 get a '$new_routers' variable equal to '', causing it to 
 dump its environment and functions with the 'set $new_routers'   
 command, and will then try to ping '$1' (which is now ''), causing 
 the ping usage message to be emitted. 
 The next version of the dhclient-script will check if "$new_routers"
 is empty and not attempt the 'set $new_routers' or 'ping $1' if so.

 1. make your dhcp server always supply the routers option
 2. remove /var/lib/dhcp/dhclient*.leases on a network stop /
    before restart.
 3. set line 266 of /sbin/dhclient-script from:
    ' if [ x$reason = x$TIMEOUT ]; then
    ' to:
    ' if [ x$reason = x$TIMEOUT ] && [ "x$new_routers" != 'x' ]; then
 I'll try to get this into RHEL-4-rc1, but it is rather late; else it
 will have to wait for an update release.

Comment 2 Jason Vas Dias 2004-11-16 20:36:44 UTC
This is now fixed in dhcp-3.0.1-12_EL (RHEL-4) and dhcp-3.0.1-12 (FC4).

Comment 3 Jay Turner 2005-01-13 18:19:54 UTC
Closing out.  Please reopen if the problem is still present with recent code.

Note You need to log in before you can comment on or make changes to this bug.