Bug #26126 | "Unknown error" during a long running query. | ||
---|---|---|---|
Submitted: | 6 Feb 2007 21:20 | Modified: | 26 Jul 2008 13:54 |
Reporter: | Mark Protas | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S2 (Serious) |
Version: | 4.1.22 | OS: | Linux (Linux, 2.6.9 kernel) |
Assigned to: | CPU Architecture: | Any | |
Tags: | unknown error |
[6 Feb 2007 21:20]
Mark Protas
[7 Feb 2007 12:09]
Valeriy Kravchuk
Thank you for a problem report. Please, send your my.cnf file content. Do you have anything in the error logs for the periods when you get this error?
[8 Feb 2007 23:07]
Mark Protas
I have attached my my.cnf to the bug. There is nothing in the mysql error log when the "Unknown error" is encountered by my application.
[12 Apr 2007 15:55]
Valeriy Kravchuk
Please, send the results of: getconf GNU_LIBC_VERSION getconf GNU_LIBPTHREAD_VERSION from your system. I also noted thread_cache=8 in your my.cnf. Can you try to set thread_cache=0 and check if this error will be still repeatable.
[12 May 2007 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".
[9 Oct 2007 18:53]
MySQL Verification Team
i've seen this error message before, and managed to get a debug trace from server. it was caused by the select part of the 'insert .. select' getting rolled back due to a deadlock or transaction timeout. hope that's good hint to try repeat it.
[26 Jun 2008 13:54]
MySQL Verification Team
Have you tried the suggestion done by Valeriy: "I also noted thread_cache=8 in your my.cnf. Can you try to set thread_cache=0 and check if this error will be still repeatable.". Thanks in advance.
[26 Jul 2008 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".
[5 Sep 2008 22:10]
Trent Lloyd
I think this bug still has some merit to be looked at.. although it is 5.1. Is it possible to repeat this on 5.0?
[14 Oct 2008 6:53]
Trent Lloyd
See new bug abotu this issue: http://bugs.mysql.com/bug.php?id=37183