Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 160461 - "rhgb-client --update" hangs during boot (the boot process block at 'starting network')
Summary: "rhgb-client --update" hangs during boot (the boot process block at 'starting...
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: rhgb
Version: 4.0
Hardware: i686
OS: Linux
Target Milestone: ---
: ---
Assignee: Ray Strode [halfline]
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2005-06-15 10:01 UTC by David Tonhofer
Modified: 2012-06-20 16:16 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2012-06-20 16:16:36 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description David Tonhofer 2005-06-15 10:01:38 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Description of problem:
When booting in graphical mode (/etc/sysconfig/init:GRAPHICAL=yes)
the boot process goes up to 'starting networking', then hangs (the little
rotary icon stops moving ;-)

When booting in text mode (/etc/sysconfig/init:GRAPHICAL=no) or having
clicked 'show details' once X comes up and starts to show the boot
progress bar, the boot process proceeds normally.


When the boot 'hangs' it is actually waiting for "rhgb-client". Once the
rotary icon stopped moving during 'starting networking', I could SSH into
the machine (the network was up) and get the process list.

One can see process "/usr/bin/rhgb-client --update=rawdevices"
doing nothing in particular. GDB shows a not very informative backtrace:

#0  0x0056a7a2 in _dl_sysinfo_int80 () from /lib/
#1  0x0064ab01 in connect () from /lib/tls/
#2  0x08048fcb in ?? ()
#3  0x00000004 in ?? ()
#4  0x096f8a68 in ?? ()
#5  0x0000006e in ?? ()
#6  0xbfe7d65c in ?? ()
#7  0x00000004 in ?? ()
#8  0x00000000 in ?? ()

A kill of that process brings us one step forward, a new rghb-client 
process shows up which hangs in turn:

/usr/bin/rhgb-client --update=gpm
/usr/bin/rhgb-client --update=crond


These processes are only started in graphical boot according to 

update_boot_stage() {
  if [ "$GRAPHICAL" = "yes" -a -x /usr/bin/rhgb-client ]; then
    /usr/bin/rhgb-client --update="$1"
  return 0

This explains the differing behaviour in graphical and non-graphical boot.

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

How reproducible:

Steps to Reproduce:
1. Start machine in graphical boot 
2. Boot process proceeds up to networking

Actual Results:  Boot process hangs at "starting networking"

Expected Results:  Boot process should continue normally or timeout in rhgb-client

Additional info:

Possible hardware dependency:

This problem has only been encounterd on a Fujitsu-Siemens
Primery L100 (a weird machine if ever ever saw one), RHN sid=1005558364.

There is no problem on a Fujitsu-Siemens Primergy RX300 S2 on the same

Here is the extract from the log of a successful boot:

Jun 14 13:12:10 rei2 sysstat: Calling the system activity data collector (sadc):
Jun 14 13:12:10 rei2 sysstat:
Jun 14 13:12:10 rei2 rc: Starting sysstat:  succeeded
Jun 14 13:12:29 rei2 smartd: smartd startup succeeded
Jun 14 13:12:10 rei2 readahead_early: Starting background readahead:
Jun 14 13:12:11 rei2 rc: Starting readahead_early:  succeeded
Jun 14 13:12:16 rei2 kudzu:  succeeded
Jun 14 13:12:19 rei2 iptables:  succeeded
Jun 14 13:12:20 rei2 rc: Starting pcmcia:  succeeded
Jun 14 13:12:29 rei2 acpid: acpid startup succeeded
Jun 14 13:12:20 rei2 sysctl: net.ipv4.ip_forward = 0
Jun 14 13:12:20 rei2 sysctl: net.ipv4.conf.default.rp_filter = 1
Jun 14 13:12:20 rei2 sysctl: net.ipv4.conf.default.accept_source_route = 0
Jun 14 13:12:20 rei2 sysctl: kernel.sysrq = 0
Jun 14 13:12:20 rei2 sysctl: kernel.core_uses_pid = 1
Jun 14 13:12:20 rei2 network: Setting network parameters:  succeeded
Jun 14 13:12:20 rei2 network: Bringing up loopback interface:  succeeded
Jun 14 13:12:22 rei2 network: Bringing up interface eth0:  succeeded
Jun 14 13:12:25 rei2 network: Bringing up interface eth1:  succeeded
Jun 14 13:12:34 rei2 cups: cupsd startup succeeded
Jun 14 13:12:34 rei2 sshd:  succeeded

Comment 1 Jiri Pallich 2012-06-20 16:16:36 UTC
Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. 
Please See

If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue.

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