Bug 156410 - ccs/cman/fenced all start by default and fail
ccs/cman/fenced all start by default and fail
Product: Fedora
Classification: Fedora
Component: cman (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Earl Brassow
Depends On:
Blocks: FC4Blocker 156922
  Show dependency treegraph
Reported: 2005-04-29 17:01 EDT by Bill Nottingham
Modified: 2014-03-16 22:53 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-05-22 01:09:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Bill Nottingham 2005-04-29 17:01:25 EDT
They shouldn't be running by default.
Comment 1 Jonathan Earl Brassow 2005-05-05 11:05:11 EDT
In RHEL, the packages are in a subchannel.  In FC, they are in core.  This makes the difference between 
why they should be on by default or off.

In the case of bug 156922, ccsd "spams" to syslog complaining that it can't connec to the cluster.  In 
FC, the user may never intend to set up a cluster.
Comment 2 Adam "mantis" Manthei 2005-05-05 11:43:22 EDT
If they shouldn't be running by default, then they probably shouldn't be
installed on the system.  A little more detail as to why you think your opinion
is the correct behavior would be helpfull.

The scripts are designed so that once the cluster is configured, a node will
automatically be able to become a part of it without any additional
configuration.  I do not see any justification for changing the init script
behavior at this time.  

The correct person to pawn this bug off on is either the rpm package
maintainer(s) (where chkcofig --add is being called) or the FC installer maintainer.
Comment 3 Joe Orton 2005-05-05 11:56:49 EDT
I think correct behaviour is to change the chkconfig lines in the init scripts
such that the services do not start by default in any runlevels, i.e.

# chkconfig: - 20 80

whatever tool performs cluster configuration should do "chkconfig ccsd on" or
equivalent to then enable these services in appropriate runlevels on the machine.
Comment 4 Chris Feist 2005-05-05 12:18:37 EDT
This should be fixed in ccs-0.25-0.3 and beyond.

Note: we only turn of the init scripts on new installs (so if you upgrade ccsd
will still attempt to start).  You can disable the ccsd init script manually by
running '/sbin/chkconfig ccsd off'.

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