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.
DescriptionRaoul Scarazzini
2015-12-24 15:50:49 UTC
We are doing a lot of debugging on a pacemaker remote node, and we've noticed that not all the logs are stored, as we would expect, into the file /var/log/pacemaker.log.
For example, we added this to a resource agent code:
ocf_log info "Starting nova-compute with --verbose and --debug from ${NOVA_HOST}"
And we don't have any track of this lines into the log above. But we can reach it while looking into journalctl:
# journalctl |grep -i Starting\ nov
Dec 24 09:38:23 overcloud-novacompute-0.localdomain NovaCompute(nova-compute)[29800]: INFO: Starting nova-compute with --verbose and --debug from overcloud-novacompute-0
It might make sense to consolidate the logs in a single place, for usability purposes.
The system log (via journalctl) is the "single place". By default, Pacemaker sends log messages of severity "notice" and greater to the system log, as well as all enabled log messages to pacemaker.log. This allows system administrators to look only at journalctl in most cases, with pacemaker.log available for reporting to us with bugs (or for advanced sysadmins to look at).
Resource agents are independent programs in their own packages, so they control their own logging, independently of Pacemaker. The ocf_log macro is quite complex to handle various log configurations.
If PCMK_debug is enabled for lrmd in /etc/sysconfig/pacemaker, ocf_log will send debug messages to pacemaker.log (or whatever is configured as the pacemaker detail log). So that might be what you're looking for.
We are doing a lot of debugging on a pacemaker remote node, and we've noticed that not all the logs are stored, as we would expect, into the file /var/log/pacemaker.log. For example, we added this to a resource agent code: ocf_log info "Starting nova-compute with --verbose and --debug from ${NOVA_HOST}" And we don't have any track of this lines into the log above. But we can reach it while looking into journalctl: # journalctl |grep -i Starting\ nov Dec 24 09:38:23 overcloud-novacompute-0.localdomain NovaCompute(nova-compute)[29800]: INFO: Starting nova-compute with --verbose and --debug from overcloud-novacompute-0 It might make sense to consolidate the logs in a single place, for usability purposes.