maria-developers team mailing list archive
Mailing list archive
Re: crash - analyze table with histogram
----- On 24 Jun, 2015, at 1:33 AM, roberto roberto@xxxxxxxxxxxxx wrote:
> Hi guys, i got a crash, could someone help?
> set histogram_size=255,histogram_type=SINGLE_PREC_HB;
> ANALYZE TABLE 19_org.estoque_itens PERSISTENT FOR ALL;
> /* Erro SQL (2013): Lost connection to MySQL server during query */
If its anything like https://mariadb.atlassian.net/browse/MDEV-7362 it will be a value in one of the rows in that table.
Eliminate column by column until you find the one that caused it.
Then find the row (or just include the whole column in the bug report).
> 150623 12:31:47 [ERROR] 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.
> To report this bug, see http://kb.askmonty.org/en/reporting-bugs
> 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.
> Server version: 10.0.20-MariaDB-log
> It is possible that mysqld could use up to
> key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads =
> 3180295 K bytes of memory
> Hope that's ok; if not, decrease some variables in the equation.
> Thread pointer: 0x0x7f523b81c008
> 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...
> stack_bottom = 0x4b1410a0 thread_stack 0x48000
> sql/field.h:703(Field::set_notnull(long long))[0x610c70]
> sql/sql_parse.cc:6529(mysql_parse(THD*, char*, unsigned int,
> sql/sql_parse.cc:1310(dispatch_command(enum_server_command, THD*,
> char*, unsigned int))[0x5a1bb7]
> Trying to get some variables.
> Some pointers may be invalid and cause the dump to abort.
> Query (0x7f5190884020): is an invalid pointer
> Connection ID (thread ID): 304
> Status: NOT_KILLED
> Optimizer switch:
> The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
> information that should help you find out what is causing the crash.
> Roberto Spadim
> Mailing list: https://launchpad.net/~maria-developers
> Post to : maria-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~maria-developers
> More help : https://help.launchpad.net/ListHelp
Daniel Black, Engineer @ Open Query (http://openquery.com.au)
Remote expertise & maintenance for MySQL/MariaDB server environments.