Bug 842052
Summary: | mysqld crash during mysqldump | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Levente Farkas <lfarkas> | ||||||
Component: | mysql | Assignee: | Honza Horak <hhorak> | ||||||
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | ||||||
Severity: | low | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 6.3 | CC: | azelinka, byte, hhorak, kvolny, ohudlick, praiskup | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | mysql-5.1.71-1.el6 | Doc Type: | Bug Fix | ||||||
Doc Text: |
Cause: MySQL daemon worked with uninitialized memory when accessing non-nullable GEOMETRY types.
Consequence: Daemon could crash when mysqldump was performed.
Fix: Memory is initialized properly.
Result: mysqldump doesn't make daemon crashed any more.
|
Story Points: | --- | ||||||
Clone Of: | |||||||||
: | 1035868 (view as bug list) | Environment: | |||||||
Last Closed: | 2013-11-21 20:40:33 UTC | Type: | Bug | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 1035868 | ||||||||
Attachments: |
|
Description
Levente Farkas
2012-07-21 11:21:29 UTC
Thank you for reporting. I've gone through the discussion at [1], but I'm still not able to reproduce such failure. Are you able to reproduce it with the test case attached at [1] on a fresh datadir? If so, are there any other steps required or does it fail even on a fresh and empty DB on your machine? [1] http://bugs.mysql.com/bug.php?id=65971 it's always happened on our server. and even mysql (ie. oracle) can reproduce it (as you can see in the above bz). unfortunately the database is the commercial google maps api so i assume i can't send it to you. anyway we try to drop the database and import it then the same happened:-( so currently either mysql fix it and gives a patch or we'd have to update from 5.1 to 5.5 in which this's already fixed. Is it possible to provide your my.cnf file, please? Created attachment 600765 [details]
my.cnf
Thank you for the my.cnf file. Unfortunately, I'm still not able to reproduce the failure. I believe a better backtrace could help, so I'd like to ask you for the following: 1. install mysql-debuginfo package if not done already 2. run mysqld with "--core-file" option (otherwise no coredump is generated) 3. generate a backtrace using the coredump file and e.g. gdb's "bt full" command Please, be aware that the coredump file is usually very large and check the backtrace and hide all sensitive data if needed. Created attachment 601772 [details]
backtrace
I've finally reproduced it, using:
$ valgrind --malloc-fill=ff /usr/libexec/mysqld --core-file
and it is also possible using:
MALLOC_PERTURB_=250 /usr/libexec/mysqld --core-file
The attached file is a coredump file.
mysql has a fix for it. dare i ask for an src.rpm from rh? (In reply to comment #8) > mysql has a fix for it. dare i ask for an src.rpm from rh? The way to get the priority of this bug raised to the point where it might get fixed in RHEL6 (without any upstream fix) is to open an issue through your regular customer support contact. *** Bug 880104 has been marked as a duplicate of this bug. *** 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. http://rhn.redhat.com/errata/RHBA-2013-1647.html |