Red Hat Bugzilla – Bug 173916
Changing debug levels in rgmanager requires fail over of service
Last modified: 2009-04-16 16:18:43 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; FunWebProducts; .NET CLR 1.1.4322; InfoPath.1)
Description of problem:
Changing debug levels in rgmanager require the init script to be modified and a restart of the service. This in turn causes the service to failover. 3.0 allowed debug levels to be changed via GUI.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.service rgmanager restart
Actual Results: NFS service failed over.
Expected Results: An effective method of changing debug levels without failing over.
Created attachment 121686 [details]
Adds support for log_level and log_facility to the <rm> tag in cluster.conf
There is no UI support for this at the moment. Log levels are integers using
standard syslog semantics:
0 - emerg
7 - debug
Log facilities are the same as listed in syslog.conf(5):
The facility is one of the following keywords: auth, authpriv, cron,
daemon, kern, lpr, mail, mark, news, security (same as auth), syslog,
user, uucp and local0 through local7. The keyword security should not
be used anymore and mark is only for internal use and therefore should
not be used in applications.
This patch ONLY affects rgmanager. cman, dlm, lock_gulmd, ccsd, clvmd, and all
other cluster components are unaffected.
Fixes in CVS ready for QA.
Branches: head, STABLE, RHEL4
see man syslog and man syslog.conf for better descriptions:
0 - emerg - System is unusable
1 - alert - Action should be taken immediately
2 - crit - Critical conditions
3 - err - Error conditions
4 - warning - Warning conditions
5 - notice - Normal, siginificant events
6 - info - Insignificant events
7 - debug - Debugging information
Possible logging facilities:
auth, authpriv, cron, daemon, kern, lpr, mail, news, syslog, user, uucp, local0,
local1, local2, local3, local4, local5, local6, local7
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.