Bug #12225 | MySQL crash on Linux embedded-server [mysqld got signal 11; ] | ||
---|---|---|---|
Submitted: | 27 Jul 2005 20:49 | Modified: | 5 Sep 2005 22:59 |
Reporter: | Jimmy Muliawan | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Embedded Library ( libmysqld ) | Severity: | S1 (Critical) |
Version: | mysql Ver 11.15 Distrib 3.23.41 | OS: | Linux (RH Linux (ker: vmlinuz-2.4.7-10)) |
Assigned to: | CPU Architecture: | Any |
[27 Jul 2005 20:49]
Jimmy Muliawan
[27 Jul 2005 20:57]
MySQL Verification Team
We need a repeatable test case. If we create it on our own we can't get the behavior reported.
[27 Jul 2005 21:08]
Jimmy Muliawan
Well, we reproduced it on one of our embedded voice mail product (in Linux). Basically, we use mysql as the database for the voicemail and some web interfaces. The load test procedure involves leaving and retrieving fax messages via phone interfaces (requires some special hardwares). So, it'll be a little tough to reproduce it without the hardwares. Does the backtrace info provide any useful information? I have a tarball of /var/lib/mysql, I'll try to attach it somewhere in this bug note.
[27 Jul 2005 21:09]
Jimmy Muliawan
partial log from mysqld.log
Attachment: mysql-log.txt (text/plain), 10.20 KiB.
[28 Jul 2005 12:56]
MySQL Verification Team
Thank you very much for your error log. This, unfortunately, does not help at all. What we need is a repeatable test case. A repeatable test case is a series of SQL commands that always lead to the problem, in your case, a crash. You can read more about how to make one in our manual.
[28 Jul 2005 18:47]
Jimmy Muliawan
We're trying to determine the SQL command sequences before mysql crashed. Is there any logging that we can turn on (for mysql) to log each SQL command being issued? Let us know if there's any other useful logging that we can turn on. We will try to reproduce the problem (with loggings turned on).
[2 Aug 2005 13:48]
MySQL Verification Team
You can use the general query log, using i.e: static char *server_args[] = {"--log=path_file_name"} or to use it in your embedded server group in my.cnf
[2 Aug 2005 20:00]
Jimmy Muliawan
I checked my.cnf file on the server: [mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid So, we already have the general err-log in /var/log/mysqld.log (the log that I gave to you before). Is there any more specific log to turn on?
[3 Aug 2005 7:45]
Aleksey Kishkin
Jimmy, it's completely different log (log for error messages). Miguel asked for setup the log for queries. BTW, why the subject of this bug report contains embedded server, if the error log and stack trace refers to mysqld (dedicated server)?
[3 Aug 2005 17:55]
Jimmy Muliawan
Hi, could you show me the step-by-step instruction on how to turn on this log (log for queries) in my.cnf file? Let me clarify, it's actually a dedicated server on a voice board (containing small PC section), plugged to one of the slot in a PBX. So it's basically a PC inside a switch box.
[5 Aug 2005 22:59]
MySQL Verification Team
Could you please verify if the bug below can apply to your case: http://bugs.mysql.com/bug.php?id=11871 Thanks in advance.
[5 Sep 2005 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".