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 'mysql_common_start()' function within the file "/usr/lib/ocf/lib/heartbeat/mysql-common.sh" is utilized by pacemaker to start 'ocf:heartbeat:mysql' resources. There are situations when MySQL fails to start and the error is sent to standard error/standard out and is not logged into the MySQL error log. The problem is pacemaker isn't seeing the standard error when the 'ocf:heartbeat:mysql' resource fails to start because the 'ocf:heartbeat:mysql' resource itself is sending all standard error and standard output to '/dev/null':
######
${OCF_RESKEY_binary} --defaults-file=$OCF_RESKEY_config \
--pid-file=$OCF_RESKEY_pid \
--socket=$OCF_RESKEY_socket \
--datadir=$OCF_RESKEY_datadir \
--log-error=$OCF_RESKEY_log \
--user=$OCF_RESKEY_user $OCF_RESKEY_additional_parameters \
$mysql_extra_params >/dev/null 2>&1 &
pid=$!
######
The above snippet is from the 'mysql_common_start()' function within the file "/usr/lib/ocf/lib/heartbeat/mysql-common.sh". You can see that at the end of the startup line that all standard error is redirecting to standard out, and then that is sent to '/dev/null'.
The customer had System Admins spend hours trying to track down why a MySQL resource wasn't starting on a PCS Cluster, but the real error was being lost to '/dev/null'. The error was a very basic configuration issue, and MySQL was logging the error to standard error. The output from MySQL was telling you exactly what was wrong, however they weren't able to capture this error because it was sent to '/dev/null', resulting in hours of troubleshooting an issue that should have taken less than a minute to resolve.
Version-Release number of selected component (if applicable):
resource-agents-4.1.1-12.el7_6.8.x86_64
How reproducible:
Anytime an 'ocf:heartbeat:mysql' resource produces standard error/standard out.
Steps to Reproduce:
Start the mysql resource in any condition that would produce stderr/stdout
Actual results:
stderr goes to /dev/null
Expected results:
The ask is that the output from the attempt to start the 'ocf:heartbeat:mysql' resource be sent anywhere except '/dev/null'. It can go to a logfile, to syslog, or anywhere you choose, just not '/dev/null' as this makes troubleshooting for System Administrators very difficult.
Additional info:
Red Hat Enterprise Linux 7 shipped it's final minor release on September 29th, 2020. 7.9 was the last minor releases scheduled for RHEL 7.
From intial triage it does not appear the remaining Bugzillas meet the inclusion criteria for Maintenance Phase 2 and will now be closed.
From the RHEL life cycle page:
https://access.redhat.com/support/policy/updates/errata#Maintenance_Support_2_Phase
"During Maintenance Support 2 Phase for Red Hat Enterprise Linux version 7,Red Hat defined Critical and Important impact Security Advisories (RHSAs) and selected (at Red Hat discretion) Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available."
If this BZ was closed in error and meets the above criteria please re-open it flag for 7.9.z, provide suitable business and technical justifications, and follow the process for Accelerated Fixes:
https://source.redhat.com/groups/public/pnt-cxno/pnt_customer_experience_and_operations_wiki/support_delivery_accelerated_fix_release_handbook
Feature Requests can re-opened and moved to RHEL 8 if the desired functionality is not already present in the product.
Please reach out to the applicable Product Experience Engineer[0] if you have any questions or concerns.
[0] https://bugzilla.redhat.com/page.cgi?id=agile_component_mapping.html&product=Red+Hat+Enterprise+Linux+7
Description of problem: The 'mysql_common_start()' function within the file "/usr/lib/ocf/lib/heartbeat/mysql-common.sh" is utilized by pacemaker to start 'ocf:heartbeat:mysql' resources. There are situations when MySQL fails to start and the error is sent to standard error/standard out and is not logged into the MySQL error log. The problem is pacemaker isn't seeing the standard error when the 'ocf:heartbeat:mysql' resource fails to start because the 'ocf:heartbeat:mysql' resource itself is sending all standard error and standard output to '/dev/null': ###### ${OCF_RESKEY_binary} --defaults-file=$OCF_RESKEY_config \ --pid-file=$OCF_RESKEY_pid \ --socket=$OCF_RESKEY_socket \ --datadir=$OCF_RESKEY_datadir \ --log-error=$OCF_RESKEY_log \ --user=$OCF_RESKEY_user $OCF_RESKEY_additional_parameters \ $mysql_extra_params >/dev/null 2>&1 & pid=$! ###### The above snippet is from the 'mysql_common_start()' function within the file "/usr/lib/ocf/lib/heartbeat/mysql-common.sh". You can see that at the end of the startup line that all standard error is redirecting to standard out, and then that is sent to '/dev/null'. The customer had System Admins spend hours trying to track down why a MySQL resource wasn't starting on a PCS Cluster, but the real error was being lost to '/dev/null'. The error was a very basic configuration issue, and MySQL was logging the error to standard error. The output from MySQL was telling you exactly what was wrong, however they weren't able to capture this error because it was sent to '/dev/null', resulting in hours of troubleshooting an issue that should have taken less than a minute to resolve. Version-Release number of selected component (if applicable): resource-agents-4.1.1-12.el7_6.8.x86_64 How reproducible: Anytime an 'ocf:heartbeat:mysql' resource produces standard error/standard out. Steps to Reproduce: Start the mysql resource in any condition that would produce stderr/stdout Actual results: stderr goes to /dev/null Expected results: The ask is that the output from the attempt to start the 'ocf:heartbeat:mysql' resource be sent anywhere except '/dev/null'. It can go to a logfile, to syslog, or anywhere you choose, just not '/dev/null' as this makes troubleshooting for System Administrators very difficult. Additional info: