Bug 451740 - system-config-services seems to fail to start all services in correct runlevel [NEEDINFO]
Summary: system-config-services seems to fail to start all services in correct runlevel
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-services
Version: 9
Hardware: i686
OS: Linux
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-06-17 01:46 UTC by James Tanis
Modified: 2009-07-14 16:05 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2009-07-14 16:05:30 UTC
Type: ---
nphilipp: needinfo? (incoming-bugzilla)

Attachments (Terms of Use)

Description James Tanis 2008-06-17 01:46:34 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b5) Gecko/2008043010 Fedora/3.0-0.60.beta5.fc9 Firefox/3.0b5

Description of problem:
This is a definitely an "Apollo 13" bug; a bug that happened early and didn't manifest itself for a long time, but when it did, the effect was quite dramatic. So first the dramatic effect: after installing my machine with F9, I started firefox and all my configuration/bookmarks/etc were **gone**. Quite disturbing. The cause: firefox couldn't deal with my configuration because it couldn't obtain the file locks across NFS (my $HOME is NFS mounted). It couldn't do this because rpc.statd was dead. rpc.statd was dead because it couldn't register with rpcbind (nee portmap). It couldn't register with rpcbind because rpc.statd was starting *before* rpcbind. It was starting before rpcbind because, despite the configuration in /etc/init.d, rpcbind was only configured to start in runleves 2, 4, and 5. Specifically it was *not* starting runlevel 3. Now my situation is definitely odd because my graphics card was not recognized during the install and so I had to use the all the anaconda system-config scripts. In particular system-config-services. 

I'm calling this a medium level bug, not because it in-and-of-itself is so bad, but because under certain circumstances (like an NFS mounted $HOME) it can have profoundly disturbing effects.

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

How reproducible:
Didn't try

Steps to Reproduce:

Actual Results:

Expected Results:

Additional info:

Comment 1 Doug Chapman 2008-06-24 16:18:45 UTC
This wasn't seen on ia64.  Moving to i686 since that appears to be where the
user saw it.

Comment 2 Nils Philippsen 2008-07-01 09:08:21 UTC
James, have you actually used system-config-services to change anything w.r.t.
the rpcbind service?

Comment 3 Bug Zapper 2009-06-10 01:39:37 UTC
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '9'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 9's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 9 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 

Comment 4 Bug Zapper 2009-07-14 16:05:30 UTC
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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