Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionAllison Matlack
2011-06-10 13:22:15 UTC
Need to integrate kbase article "What are the debug options that can be enabled for RHEL6 clustering?" into official product docs.
Link to kbase article: https://access.redhat.com/kb/docs/DOC-53585
Logging options are currently defined in the annotated cluster schema (plus in the Conga section). The plans are to expand the logging section of the ccs command documentation, but the basic cluster.conf options are defined in that file.
Reassigning to me.
The bug was originally filed as being Version 6.3, which is what I was referring to in Comment 3. I thought I had moved the flag to 6.2, but it looks as if what I did was remove the 6.2 flag and then check the 6.2 flag again instead of the 6.3 flag.
[Adding Chris Feist to the cc list since resolving this bug will involve adding some ccs documentation about logging.]
The debug options are mostly part of the logging options. These are my plans to expand the documentation regarding debug and logging:
- As noted, the logging options are defined specifically in the annotated cluster schema, and the Conga chapter includes a section on configuring logging with Conga. The debug option per se is noted as something you can set -- to enable debugging messages in the log file. There's not much more to document about it, I don't think.
- The ccs chapter currently does not mention logging at all. I will add a new section on configuring logging with ccs with the --setlogging, --addlogging, and --rmlogging options of the ccs command.
- The chapter on the cluster.conf file does not explicitly document configuring logging with the logging tag. I will add a small section about this, to parallel the section in the ccs chapter, including the sample section of cluster.conf that is currently in the kBase article..
- The kBase article includes a summary of enabling dlm debug logging. Configuration for dlm is, so far, not part of the Cluster Administration manual. It seems pretty internal -- something more for a developer than a system administrator. I will pursue whether we really want to document this in the Cluster Administration manual, but I think that at most we should just refer to the annotated schema for information about enabling dlm logging. Even there, that would involve documenting dlm in the first place and that's what I'm not certain about.