469,271 Members | 1,484 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,271 developers. It's quick & easy.

read_const error 127 - then MySQL dies

Hi all,

The following keeps happening and I can't pinpoint a query that is
causing it. It did not happen in 3.23.x, but started upon upgrading to
4.0.14. The operating system/hardware information is as follows:

RedHat 8.0 - kernel 2.4.18SMP
4x Xeon Processors
4x 80GB SCSI drives (hardware RAID-10)

The following is a log exerpt:

030808 15:22:09 read_const: Got error 127 when reading table ****
mysqld got signal 11;
This could be because you hit a bug. It is also possible that this
or one of the libraries it was linked against is corrupt, improperly
or misconfigured. This error can also be caused by malfunctioning
We will try our best to scrape up some info that will hopefully help
the problem, but since we have already crashed, something is definitely
and this may fail.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections
= 2184184 K
bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

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=0x98a4ad98, backtrace may not be correct.
Stack range sanity check OK, backtrace follows:
New value of fp=(nil) failed sanity check, terminating stack trace!
Please read http://www.mysql.com/doc/en/Using_stack_trace.html and
follow instructions on how to resolve the stack trace. Resolved
stack trace is much more helpful in diagnosing the problem, so please do
resolve it
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort...
thd->query at 0x89af670 = SELECT * FROM order_data WHERE viewed='' ORDER
BY order_num DESC
The manual page at http://www.mysql.com/doc/en/Crashing.html contains
information that should help you find out what is causing the crash.

Number of processes running now: 0
030808 15:22:19 mysqld restarted
030808 15:22:20 InnoDB: Database was not shut down normally.
InnoDB: Starting recovery from log files...
InnoDB: Starting log scan based on checkpoint at
InnoDB: log sequence number 5 4012008225
InnoDB: Doing recovery: scanned up to log sequence number 5 4012079335
030808 15:22:20 InnoDB: Starting an apply batch of log records to the
InnoDB: Progress in percents: 31 32 33 34 35 36 37 38 39 40 41 42 43 44
45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68
69 70 71 72 73 74 75
InnoDB: Apply batch completed
InnoDB: Last MySQL binlog file position 0 1058709429, file name
030808 15:22:21 InnoDB: Flushing modified pages from the buffer pool...
030808 15:22:21 InnoDB: Started
/usr/sbin/mysqld-max: ready for connections.
Version: '4.0.14-Max-log' socket: '/var/lib/mysql/mysql.sock' port:
This happens often. Any ideas? Thanks.

Richard Gabriel <rg******@coresense.com>

MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/my***********...ie.nctu.edu.tw

Jul 19 '05 #1
0 1794

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

7 posts views Thread by Julien - Marseille | last post: by
3 posts views Thread by Noyb | last post: by
reply views Thread by Jamie Krasnoo | last post: by
reply views Thread by Jamie Krasnoo | last post: by
2 posts views Thread by I appreciate your help.... anony | last post: by
3 posts views Thread by jehugaleahsa | last post: by
3 posts views Thread by Jeff | last post: by
15 posts views Thread by Lawrence Krubner | last post: by
reply views Thread by zhoujie | last post: by
reply views Thread by suresh191 | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.