| May be I'm blind, :-) but you provided dump of another table than you used | in the query. What is the structure of table 'b2posts'?
You're right, here it is: CREATE TABLE b2posts ( ID int(10) unsigned NOT NULL auto_increment, post_author int(4) NOT NULL default '0', post_date datetime NOT NULL default '0000-00-00 00:00:00', post_content text NOT NULL, post_title text NOT NULL, post_category int(4) NOT NULL default '0', post_karma int(11) NOT NULL default '0', PRIMARY KEY (ID), UNIQUE KEY ID (ID) ) TYPE=MyISAM; | What type of errors do you get? Is there anything in the | error log? What OS do you use? How did you installed MySQL: from binary | or from source? Installed from binary. Linux kernel 2.4.17. Here's the dump from the error log. Warning: long. ***Here's the query I asked about originally*** 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=6287360 read_buffer_size=520192 sort_buffer_size=524280 max_used_connections=19 max_connections=225 threads_connected=6 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 235638 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x8856320 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=0xbfdfea78, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8072b1a 0x827b7b8 0x80c817d 0x80c7010 0x80a4025 0x809d8b4 0x8096913 0x80a3a86 0x807ceda 0x8080af5 0x807bfe3 0x8081eae 0x807b1be 0x8278e9c 0x82ae29a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/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 0x88b3798 = SELECT DISTINCT * FROM b2posts WHERE 1=1 AND ID = 124 AND ((post_title LIKE '%%') OR (post_content LIKE '') OR (post_title LIKE '%%') OR (post_content LIKE '%%')) AND post_date < '2002-08-31 14:31:55' AND post_category > 0 ORDER BY post_date DESC thd->thread_id=539 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 539 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid. The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash. ***Here's another query that gave the same results*** 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=6287360 read_buffer_size=520192 sort_buffer_size=524280 max_used_connections=1 max_connections=225 threads_connected=1 It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 235638 K bytes of memory Hope that's ok; if not, decrease some variables in the equation. thd=0x872eff8 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=0xbfe7ea78, backtrace may not be correct. Stack range sanity check OK, backtrace follows: 0x8072b1a 0x827b7b8 0x809da5f 0x809d89e 0x8096913 0x80a3a86 0x807ceda 0x8080af5 0x807bfe3 0x8081eae 0x807b1be 0x8278e9c 0x82ae29a New value of fp=(nil) failed sanity check, terminating stack trace! Please read http://www.mysql.com/doc/U/s/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 0x872f8c0 = SELECT DISTINCT ibf_posts.author_id, ibf_topics.* from ibf_topics LEFT JOIN ibf_posts ON (ibf_topics.tid = ibf_posts.topic_id AND ibf_posts.author_id = '9') WHERE ibf_topics.forum_id='2' and (ibf_topics.last_post > '0' OR ibf_topics.pinned='1') and ibf_topics.approved='1' ORDER BY pinned DESC, last_post DESC LIMIT 0,15 thd->thread_id=5 Successfully dumped variables, if you ran with --log, take a look at the details of what thread 5 did to cause the crash. In some cases of really bad corruption, the values shown above may be invalid. The manual page at http://www.mysql.com/doc/C/r/Crashing.html contains information that should help you find out what is causing the crash. Here is the structure of the two tables in the second query: CREATE TABLE ibf_posts ( pid bigint(20) NOT NULL auto_increment, author_id int(10) NOT NULL default '0', author_name varchar(32) default NULL, use_sig varchar(8) default NULL, use_emo varchar(8) default NULL, ip_address varchar(32) default NULL, post_date int(10) default NULL, icon_id smallint(3) default NULL, post text, queued tinyint(1) default NULL, topic_id bigint(20) NOT NULL default '0', forum_id int(10) NOT NULL default '0', attach_id varchar(64) default NULL, attach_hits int(10) default NULL, attach_type varchar(128) default NULL, attach_file varchar(255) default NULL, post_title varchar(255) default NULL, new_topic tinyint(1) default '0', PRIMARY KEY (pid), KEY forum_id (forum_id), KEY topic_id (topic_id,author_id), KEY author_id (author_id) ) TYPE=MyISAM; CREATE TABLE ibf_topics ( tid bigint(20) NOT NULL auto_increment, title varchar(70) NOT NULL default '', description varchar(70) default NULL, state varchar(8) default NULL, posts smallint(4) default NULL, starter_id varchar(32) default NULL, start_date int(10) default NULL, last_poster_id varchar(32) default NULL, last_post int(10) default NULL, icon_id tinyint(2) default NULL, starter_name varchar(32) default NULL, last_poster_name varchar(32) default NULL, poll_state varchar(8) default NULL, last_vote int(10) default NULL, views smallint(5) default NULL, forum_id smallint(5) NOT NULL default '0', approved tinyint(1) default NULL, author_mode tinyint(1) default NULL, pinned tinyint(1) default NULL, moved_to varchar(64) default NULL, rating text, total_votes int(5) NOT NULL default '0', PRIMARY KEY (tid), KEY forum_id (forum_id) ) TYPE=MyISAM; Thanks! And let me know if you need any more info. --Matt --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
