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.
DescriptionRadka Brychtova
2016-02-16 16:45:03 UTC
Created attachment 1127636[details]
Crash report from abrt - mysqld
Description of problem:
After running test for mysql, abrt catch the core dump in mysqld and mysqltest.
Version-Release number of selected component (if applicable):
pkg_arch: x86_64
pkg_epoch: 0
pkg_fingerprint: 199E 2F91 FD43 1D51
pkg_name: mysql-server
pkg_release: 5.el6_6
pkg_vendor: Red Hat, Inc.
pkg_version: 5.1.73
How reproducible:
100%
Steps to Reproduce:
Test (/CoreOS/mysql/testsuite) execute :
sudo -u mysql ./mysql-test-run --vardir=$TmpDir --force 2>&1 | tee $LogFile
Actual results:
worker[1] Trying to dump core for [mysqltest - pid: 11751, winpid: 11751]
worker[1] Trying to dump core for [mysqld.1 - pid: 11480, winpid: 11480]
worker[1] Trying to dump core for [mysqld.2 - pid: 11683, winpid: 11683]
Expected results:
no core dump
Additional info:
Add attachment with abrt result
Created attachment 1127636 [details] Crash report from abrt - mysqld Description of problem: After running test for mysql, abrt catch the core dump in mysqld and mysqltest. Version-Release number of selected component (if applicable): pkg_arch: x86_64 pkg_epoch: 0 pkg_fingerprint: 199E 2F91 FD43 1D51 pkg_name: mysql-server pkg_release: 5.el6_6 pkg_vendor: Red Hat, Inc. pkg_version: 5.1.73 How reproducible: 100% Steps to Reproduce: Test (/CoreOS/mysql/testsuite) execute : sudo -u mysql ./mysql-test-run --vardir=$TmpDir --force 2>&1 | tee $LogFile Actual results: worker[1] Trying to dump core for [mysqltest - pid: 11751, winpid: 11751] worker[1] Trying to dump core for [mysqld.1 - pid: 11480, winpid: 11480] worker[1] Trying to dump core for [mysqld.2 - pid: 11683, winpid: 11683] Expected results: no core dump Additional info: Add attachment with abrt result