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:
User is running pcsd.
Consequence:
/var/log/pcsd/pcsd.log is missing most of the messages which should have been logged.
Fix:
Make pcsd write to pcsd.log synchronously.
Result:
pcsd.log contains all the logged messages.
Description of problem:
After pcsd starts up and the startup sequence is logged, only incoming HTTP requests are logged. All the other log messages are buffered in memory and are logged at pcsd clean exit.
Version-Release number of selected component (if applicable):
pcs-0.9.165-6.el7
How reproducible:
always, easily
Steps to Reproduce:
Observer /var/log/pcsd/pcsd.log to see only incoming requests are logged.
Example: run 'pcs status pcsd' in a cluster and see what is being logged.
Actual results:
Only incoming requests are logged:
::ffff:192.168.122.161 - - [21/Feb/2019:12:14:18 +0100] "GET /remote/check_auth HTTP/1.1" 200 69 0.0088
::ffff:192.168.122.161 - - [21/Feb/2019:12:14:18 +0100] "GET /remote/check_auth HTTP/1.1" 200 69 0.0089
rh76-node1 - - [21/Feb/2019:12:14:18 CET] "GET /remote/check_auth HTTP/1.1" 200 69
- -> /remote/check_auth
Expected results:
Other messages are logged as well:
I, [2019-02-21T12:14:07.387480 #510] INFO -- : Running: /usr/sbin/corosync-cmapctl totem.cluster_name
I, [2019-02-21T12:14:07.387528 #510] INFO -- : CIB USER: hacluster, groups:
I, [2019-02-21T12:14:07.396624 #510] INFO -- : Return Value: 0
::ffff:192.168.122.151 - - [21/Feb/2019:12:14:07 +0100] "GET /remote/check_auth HTTP/1.1" 200 101 0.0108
::ffff:192.168.122.151 - - [21/Feb/2019:12:14:07 +0100] "GET /remote/check_auth HTTP/1.1" 200 101 0.0109
rh75-node1 - - [21/Feb/2019:12:14:07 CET] "GET /remote/check_auth HTTP/1.1" 200 101
- -> /remote/check_auth
Additional info:
This got broken upstream in version pcs-0.9.165.
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://access.redhat.com/errata/RHBA-2019:2244