Daren Cotter writes:
> Sorry to post AGAIN, but I have new info. I was monitoring the Error Log,
> and when I run the query that crashes MySQL, I get the following error:
>
>
> mysqld got signal 11;
> The manual section 'Debugging a MySQL server' tells you how to use a
> stack trace and/or the core file to produce a readable backtrace that may
> help in finding out why mysqld died
> Attemping backtrace. You can use the following information to find out
> where mysqld died. If you see no messages after this, something went
> terribly wrong
> stack range sanity check, ok, backtrace follows
> 0x4008407e
> 0x8098525
> 0x80972ba
> 0x808c6b3
> 0x80aa19b
> 0x80d7c73
> 0x80d6b17
> 0x80cf2da
> 0x80b5e6b
> 0x80b9015
> 0x80b52d3
> 0x80b4949
> stack trace successful
>
> Number of processes running now: 0
> 010312 19:08:50 mysqld restarted
> /usr/libexec/mysqld: ready for connections
>
>
> I attempted to run my own Stack Trace, but when I try to create a symbol
> file like the manual says, I get an error:
>
> %: nm -n libexec/mysqld > /tmp/mysqld.sym
> nm: /usr/libexec/mysqld: no symbols
>
> I'm really on ends with this. The only thing I can possibly think it may be,
> is that on my previous server, the table types were ISAM, and on the new
> server, the table types are MyISAM. I notice the error on queries that work
> with the TIMESTAMP field, so is there possibly some incompatibility with
> this, and if so, how can I fix it?
>
> This is one query that is causing the error:
>
> SELECT (lots of info that is not causing error),
> CONCAT(SUBSTRING(MONTHNAME(signup_date),1,3), ' ', DAYOFMONTH(signup_date),
> ', ', YEAR(signup_date)) as signup_date,
> CONCAT(SUBSTRING(MONTHNAME(last_update),1,3), ' ', DAYOFMONTH(last_update),
> ', ', YEAR(last_update), ' ', HOUR(last_update), ':', MINUTE(last_update))
> AS last_update, CONCAT(SUBSTRING(MONTHNAME(last_login),1,3), ' ',
> DAYOFMONTH(last_login), ', ', YEAR(last_login), ' ', HOUR(last_login), ':',
> MINUTE(last_login)) AS last_login, (more info not causing error) FROM
> members WHERE member_id = 10010
>
>
> I know that certain info is not causing the error, as I modified the query
> and it worked fine.
>
Hi!
If running the above query always causes segmentation fault, please
upload your members MyISAM table (xipped), with the above query to :
ftp://support.mysql.com/pub/mysql/Incoming
so that we can test it.
Many thanks in advance.
Regards,
Sinisa
____ __ _____ _____ ___ == MySQL AB
/*/\*\/\*\ /*/ \*\ /*/ \*\ |*| Sinisa Milivojevic
/*/ /*/ /*/ \*\_ |*| |*||*| mailto:[EMAIL PROTECTED]
/*/ /*/ /*/\*\/*/ \*\|*| |*||*| Larnaca, Cyprus
/*/ /*/ /*/\*\_/*/ \*\_/*/ |*|____
^^^^^^^^^^^^/*/^^^^^^^^^^^\*\^^^^^^^^^^^
/*/ \*\ Developers Team
---------------------------------------------------------------------
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
