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.
Cause:
Running corosync-objctl with parameter
Consequence:
Error reloading DB 11.
Reloading was added by mistake to fix bz#773720. Result WAS to trigger change, but also to trigger reload of configuration file. This is ok for corosync/openais itself, because no plugin failed. Sadly, with cman preconfig plugin loaded, this results in error (because version number of file was not changed).
Fix:
Remove reload and properly handle change of logging object in confdb.
Result:
No longer "Error reloading DB 11.", but it's perfectly possible to change logging level in runtime.
Created attachment 647757[details]
Proposed patch - part 1 - Track changes for confdb logging object
This makes possible to track changes in logging object (and it's
sub objects) for changes, so reload is no longer needed.
Created attachment 647758[details]
Proposed patch - part 2 - Don't call reload on corosync-objctl actions
confdb reload is used only for reloading of file, not for triggering
changes.
"Unit test":
Unit test results:
corosync.conf snippet:
logging {
debug: on
....
post patch:
[root@rhel6-node2 coro]# corosync -f
Apr 24 08:05:14 corosync [MAIN ] Corosync Cluster Engine ('1.4.3-dirty'): started and ready to provide service.
.... lots of log ....
Apr 24 08:05:14 corosync [TOTEM ] releasing messages up to and including 18
[root@rhel6-node2 ~]# corosync-objctl |grep logging
...
logging.debug=on
...
notice in the logs (debugging output):
Apr 24 08:06:15 corosync [CONFDB] lib_init_fn: conn=0x145ce40
Apr 24 08:06:15 corosync [CONFDB] exit_fn for conn=0x145ce40
[root@rhel6-node2 ~]# corosync-objctl -w logging.debug=off
[root@rhel6-node2 ~]#
[root@rhel6-node2 ~]# corosync-objctl |grep logging
....
logging.debug=off
....
and there are no more CONFDB lib_init/exit_fn entries.
NOTE I used CONFDB in the example but it applies to all logging.
This works with corosync standalone and also with cman.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2013-0497.html