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" heartbeat resource (/usr/lib/ocf/resource.d/heartbeat/mysql) seems to generally work. E.g. '/usr/lib/ocf/resource.d/heartbeat/mysql start' will start an instance of MariaDB. However it does that by running 'mysqld_safe' directly and not through calling the mariadb service.
Version-Release number of selected component (if applicable):
3.9.5-54.el7_2.17
How reproducible:
Consistent.
Steps to Reproduce:
Create a service. From that service, run:
/usr/lib/ocf/resource.d/heartbeat/mysql stop
/usr/lib/ocf/resource.d/heartbeat/mysql start
(Or similar manipulations)
Actual results:
An instance of MariaDB running in the same cgroup of your service, regardless of the mariadb service.
Expected results:
The MariaDB service stopped and started.
Additional info:
My initial workaround (currently in a copy of that script, due to packaging concerns, but really belongs in /usr/lib/ocf/lib/heartbeat/mysql-common.sh) is:
# Redefine functions from mysql-common.sh:
mysql_common_start() {
systemctl start mariadb
}
mysql_common_stop() {
systemctl stop mariadb
}
mysql_common_status() {
local loglevel=$1
if systemctl is-active --quiet mariadb; then
return $OCF_SUCCESS;
else
ocf_log $loglevel "MySQL not running"
return $OCF_NOT_RUNNING;
fi
}
Comment 6Oyvind Albrigtsen
2017-11-01 16:06:33 UTC
Closing as this change would require a full rewrite of the configuration parsing, which in turn might not be backwards compatible either.
Description of problem: The "mysql" heartbeat resource (/usr/lib/ocf/resource.d/heartbeat/mysql) seems to generally work. E.g. '/usr/lib/ocf/resource.d/heartbeat/mysql start' will start an instance of MariaDB. However it does that by running 'mysqld_safe' directly and not through calling the mariadb service. Version-Release number of selected component (if applicable): 3.9.5-54.el7_2.17 How reproducible: Consistent. Steps to Reproduce: Create a service. From that service, run: /usr/lib/ocf/resource.d/heartbeat/mysql stop /usr/lib/ocf/resource.d/heartbeat/mysql start (Or similar manipulations) Actual results: An instance of MariaDB running in the same cgroup of your service, regardless of the mariadb service. Expected results: The MariaDB service stopped and started. Additional info: My initial workaround (currently in a copy of that script, due to packaging concerns, but really belongs in /usr/lib/ocf/lib/heartbeat/mysql-common.sh) is: # Redefine functions from mysql-common.sh: mysql_common_start() { systemctl start mariadb } mysql_common_stop() { systemctl stop mariadb } mysql_common_status() { local loglevel=$1 if systemctl is-active --quiet mariadb; then return $OCF_SUCCESS; else ocf_log $loglevel "MySQL not running" return $OCF_NOT_RUNNING; fi }