471,897 Members | 2,235 Online
Bytes | Software Development & Data Engineering Community
Post +

Home Posts Topics Members FAQ

Join Bytes to post your question to a community of 471,897 software developers and data experts.

FULLTEXT crashing mysql 4.0.14

I'm setting up a database server on a Dell Poweredge 2650, dual 1.8GHZ pentium
with 1GB of memory and RAID5 drives. I've installed RedHat 9, and updated the
kernel to 2.4.20-19.9smp. I've installed the RPM binary distribution of MySQL
4.0.14 right from the MySQL website. The only thing I have done is disable
InnoDb in my my.cnf file.

Database Table:
I have a database with 21.4 million records. One field is a VARCHAR(255) field
on which I have created a FULLTEXT index.

Most single word full text searches work perfectly and quickly. Occasionally,
when someone enters several words (without any operators), MySQL will crash
with the following in the error log (see below). This is totally consistent,
and MySQL will crash on the same submitted search text each time. Then other,
more complex terms will work. But I can make MySQL crash every time with the
query below in the error log. I've already rebuilt the fulltext index with
myisamchk, and there are no writes to this table at all - it's totally read

I'm not sure what to do next - I don't want to have my database crashing every
hour when someone submits a valid search term that trips up the database.

Any help would be most appreciated.



030813 12:37:09 mysqld started
/usr/sbin/mysqld: ready for connections.
Version: '4.0.14-standard-log' socket: '/var/lib/mysql/mysql.sock' port: 3306
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.

It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections =
225791 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=0xbff3e528, 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 0x84b2668 = SELECT denom,series,serial_number,notes,MATCH (notes)
AGAINST ('\"traded this bill\"') AS score FROM temp_bill_note_search WHERE
MATCH (notes) AGAINST ('\"traded this bill\"' IN BOOLEAN MODE) order by score
desc limit 0, 20
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
030813 12:48:24 mysqld restarted
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software

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 1380

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Phil Powell | last post: by
reply views Thread by Ralph Guzman | last post: by
reply views Thread by Henry Hank | last post: by
reply views Thread by Matt W | last post: by
reply views Thread by Phil Powell | last post: by
reply views Thread by Robert Oschler | last post: by
1 post views Thread by Robert Oschler | last post: by
reply views Thread by YellowAndGreen | last post: by

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.