| Bug #4549 | Mysql signal 11 on startup | ||
|---|---|---|---|
| Submitted: | 14 Jul 2004 19:38 | Modified: | 4 Aug 2004 16:53 |
| Reporter: | Richard Thomas | Email Updates: | |
| Status: | Duplicate | Impact on me: | |
| Category: | MySQL Server: Packaging | Severity: | S1 (Critical) |
| Version: | 4.1.3 | OS: | Linux (Fedora Core 2) |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[21 Jul 2004 2:31]
Matthew Lord
Hi, Is this on x86_64 bit hardware? We have not had any problems and cannot repeat this on x86 hardware but we have had problems on x86_64 machines with the rpms and there are other bug reports filed for this problem. Best Regards
[22 Jul 2004 18:38]
Richard Thomas
No this is on a quad xeon
[4 Aug 2004 16:36]
Helge Jung
Just as a note before a developer starts to search a bug which possibly doesn't exist any more: This bug seems to have the same effects as http://bugs.mysql.com/bug.php?id=4844 and http://bugs.mysql.com/bug.php?id=4407. I had the same problems (mysqld crashing right after the start) and it got solved by the patch supplied at the very bottom of Bug #4407.
[4 Aug 2004 16:53]
Matthew Lord
This looks like a duplicate of 4407 and was reported solved with the same patch.
Description: Installed the rpms from dev.mysql.com, mysql will not start. 040713 21:07:18 Warning: Asked for 196608 thread stack, but got 126976 mysqld got signal 11; This could be because you hit a bug. It is also possible that this binary or one of the libraries it was linked against is corrupt, improperly built, or misconfigured. This error can also be caused by malfunctioning hardware. We will try our best to scrape up some info that will hopefully help diagnose the problem, but since we have already crashed, something is definitely wrong and this may fail. key_buffer_size=268435456 read_buffer_size=1044480 max_used_connections=0 max_connections=100 threads_connected=0 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 466543 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x85a0ad8 Attempting backtrace. You can use the following information to find out where mysqld died. If you see no messages after this, something went terribly wrong... Cannot determine thread, fp=0xfefff018, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x808bd47 0x82c79d8 0x82c8f47 0x82ca28f 0x826eef4 0x80fae2a 0x80e6789 0x80e80fe 0x808d389 0x82d74f4 0x8048101 Stacktrace 0x808bd47 _ZN18Item_func_add_time7val_strEP6String + 839 0x82c79d8 rtree_page_mbr + 1960 0x82c8f47 sp_get_linestring_mbr + 23 0x82ca28f myrg_rrnd + 95 0x826eef4 mlog_write_initial_log_record + 164 0x80fae2a _ZN4JOIN4execEv + 474 0x80e6789 _Z7yyparsePv + 41705 0x80e80fe _Z7yyparsePv + 48222 0x808d389 _ZN20Item_func_dayofmonthC2EP4Item + 89 0x82d74f4 qsort2 + 1044 0x8048101 _start + 1 How to repeat: Fedora core 2 latest updates Install 4.1.3 Try to start