Red Hat Bugzilla – Bug 159767
service operations on non-existent services are processed anyway
Last modified: 2009-04-16 16:17:26 EDT
Description of problem: If a service doesn't exist and we try to enable it, it will fail. That's fine -- except that rgmanager goes through the hassle of a full start sequence, and spits out really ugly log messages while it's trying to start the nonexistent service. Ex: clusvcadm -e "fehjre" Jun 7 16:49:59 red clurgmgrd[4174]: <notice> Stopping service fehjre Jun 7 16:49:59 red clurgmgrd[4174]: <crit> #12: RG fehjre failed to stop; intervention required clusvcadm -e "fehjre" Jun 7 16:49:59 red clurgmgrd[4174]: <notice> Service fehjre is failed Jun 7 16:50:09 red clurgmgrd[4174]: <notice> Starting stopped service fdsafdsa Jun 7 16:50:09 red clurgmgrd[4174]: <warning> #68: Failed to start fdsafdsa; return value: 1 clusvcadm -d "fdsafdsa" Jun 7 16:50:09 red clurgmgrd[4174]: <notice> Stopping service fdsafdsa Jun 7 16:50:09 red clurgmgrd[4174]: <crit> #12: RG fdsafdsa failed to stop; intervention required
Created attachment 116664 [details] Fixes behavior and makes error reporting more readable.
[root@red ~]# clusvcadm -d rhjkdfsafdsahjk Member red disabling rhjkdfsafdsahjk...failed: Service does not exist
Fixes in CVS
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2005-738.html