Bug 143694 - Shutdown/Reboot Problem
Summary: Shutdown/Reboot Problem
Keywords:
Status: CLOSED DUPLICATE of bug 142532
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts
Version: 3.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact:
URL: http://www.veccal.ernet.in
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-12-24 11:22 UTC by Joydev Lahiri
Modified: 2014-03-17 02:51 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Joydev Lahiri 2004-12-24 11:22:12 UTC
Description of problem:
This applies to RHEL3 AS/ES/WS Update 3 and 4. While 

Rebooting/Shutdown, system hangs with the error given below.


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

probably vixie-cron 3.0.1-75.1 rpm and possibly initscripts/chkconfig.

How reproducible:
Always


Steps to Reproduce:
1.Reboot or Shutdown
2.
3.
  
Actual results:
****************TRUNCATED***********************
Sending all processes the TERM signal [OK]
Sending all processes the KILL signal [OK]
Turning off swap                      [OK]
Turning of quotas                     [OK]
Unmounting file system: umount2: Device or Resource busy
umount:/var: device is busy           [FAILED]
****************TRUNCATED************************
The [FAILED] message is repeated 3 to 30 (approx) times,
resulting in an inordinately long reboot/shutdown times.


Expected results:
Clean normal reboot/ shutdown


Additional info:
In some systems downgrading vixie-cron-3.0.1-75.1 rpm to
3.0.1-74 rpm helps but not always.

Comment 1 Joydev Lahiri 2004-12-24 12:52:09 UTC
Reported by
Joydev Lahiri <joy.in>

Comment 2 Bill Nottingham 2004-12-24 19:01:35 UTC

*** This bug has been marked as a duplicate of 142532 ***

Comment 3 Red Hat Bugzilla 2006-02-21 19:07:47 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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