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.
DescriptionChristine Caulfield
2013-10-11 08:04:37 UTC
Description of problem:
If I enable votequorum logging in corosync.conf as below, the log messages come tagged as [QUORUM] instead of [VOTEQ]
logging {
to_syslog: yes
logger_subsys {
subsys: VOTEQ
debug: on
}
}
Version-Release number of selected component (if applicable):
7.0
How reproducible:
Every time
Steps to Reproduce:
1. Add logging stanza to corosync.conf
2. Enable debug logging in rsyslog.conf
3. read syslog file
Actual results:
votequorum log messages come out prefixed with [QUORUM]
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] got nodeinfo message from cluster node 4
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] nodeinfo message[0]: votes: 0, expected: 0 flags: 0
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] total_votes=4, expected_votes=4
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 1 state=1, votes=1, expected=4
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 2 state=1, votes=1, expected=4
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 3 state=1, votes=1, expected=4
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 4 state=1, votes=1, expected=4
Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] lowest node id: 1 us: 2
Expected results:
Log messages should match the subsystem requested in corosync.conf. In this case [VOTEQ ]
Additional info:
Comment 2Christine Caulfield
2013-10-11 15:56:52 UTC
I have narrowed this down to what I think is a libqb bug (or maybe a feature).
it seems the file matching algorithm in log.c function _cs_matches_filter_ doesn't distinguish between votequorum.c and quorum.c because the latter is contained in the former. If there are some quorum.c filters defined AFTER votequorum.c filters then they get applied and the tags get set to 1 [QUORUM] instead of 7 [VOTEQ ]
Ping me on IRC if you need more information.
Comment 3Christine Caulfield
2013-10-14 07:57:12 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.
Description of problem: If I enable votequorum logging in corosync.conf as below, the log messages come tagged as [QUORUM] instead of [VOTEQ] logging { to_syslog: yes logger_subsys { subsys: VOTEQ debug: on } } Version-Release number of selected component (if applicable): 7.0 How reproducible: Every time Steps to Reproduce: 1. Add logging stanza to corosync.conf 2. Enable debug logging in rsyslog.conf 3. read syslog file Actual results: votequorum log messages come out prefixed with [QUORUM] Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] got nodeinfo message from cluster node 4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] nodeinfo message[0]: votes: 0, expected: 0 flags: 0 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] total_votes=4, expected_votes=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 1 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 2 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 3 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] node 4 state=1, votes=1, expected=4 Oct 10 16:45:43 localhost corosync[9666]: [QUORUM] lowest node id: 1 us: 2 Expected results: Log messages should match the subsystem requested in corosync.conf. In this case [VOTEQ ] Additional info: