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.
Description of problem:
The syslog logfile /var/log/messages is flooded with similar messages (just different PID) - actually repeated all 20s:
Sep 10 13:53:09 rhlios2 pacemakerd[28246]: notice: crm_add_logfile: Additional logging available in /var/log/cluster/corosync.log
in old RHEL6.5 this message was not seen.
Version-Release number of selected component (if applicable):
RHEL 6.7
pacemaker-1.1.12-8.el6.x86_64
How reproducible:
always
Steps to Reproduce:
resource agents are calling the "pacemakerd -$" periodically,
And each call still generates the additional line into the messages file.
So the problem is the combination of the postgres & mysql resource agent scripts (using the common "ocf-shellfuncs" )
and the new implementation of the pacemakerd logging output.
- Either the "pacemakerd" skips the line in the logging when only called with "-$" to get the installed version
- or the script function "ocf_local_nodename()" inside the common part of included "ocf-shellfuncs" may not call the "pacemakerd -$"
You can easily check when calling manually the "pacemakerd -$" --> this always generates a logging message in RHEL 6.7,
if you do the same call in RHEL 6.5 no entry in /var/log/messages is written.
Actual results:
Expected results:
Additional info:
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.
https://rhn.redhat.com/errata/RHBA-2016-0856.html