I would like to comment that I have the same problem. We used to run (and now still do) MariaDB-server-5.3.2-102.el5.x86_64.rpm, I installed 3 days ago, MariaDB-server-5.3.5-113.el5.x86_64.rpm on a CentOS 5 series server. Within 1 day of running, there was a query done once a day which caused the following crash:
No swap space was every used, the system has 8GB of RAM - I doubt that the system could not allocate 64MB or 151MB as it indicates below. I am afraid that the problem exists past the 5.3.2 release. To be clear, the problem does not exist in 5.3.2 - I have been running that for the last 6 months without a single hickup - and I have been very pleased with that stability.
Steffen
120301 11:56:12 Percona XtraDB (http://www.percona.com) 1.0.17-13.0 started; log sequence number 1403936934864
120301 11:56:12 [Note] Event Scheduler: Loaded 0 events
120301 11:56:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.3.5-MariaDB-ga-mariadb113-log' socket: '/var/lib/mysql/mysql.sock' port: 3306 (MariaDB - http://mariadb.com/)
120302 8:28:05 [ERROR] mysqld: Out of memory (Needed 67372056 bytes)
120302 8:28:05 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
120304 8:27:17 [ERROR] mysqld: Out of memory (Needed 158575640 bytes)
120304 8:27:17 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
2d2d2d d:2d:2d [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.
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: 5.3.5-MariaDB-ga-mariadb113-log
key_buffer_size=2147483648
read_buffer_size=2097152
max_used_connections=135
max_threads=251
thread_count=71
connection_count=71
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 3128499 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2aab98687540
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 = 514010f8 thread_stack 0x48000
/usr/sbin/mysqld(my_print_stacktrace+0x2e) [0xa0a26e]
/usr/sbin/mysqld(handle_fatal_signal+0x427) [0x741dc7]
/lib64/libpthread.so.0 [0x358540eb10]
/usr/sbin/mysqld(create_internal_tmp_table(st_table*, st_key*, st_maria_columndef*, st_maria_columndef**, unsigned long long)+0x218) [0x68a888]
/usr/sbin/mysqld(mysql_derived_create(THD*, st_lex*, TABLE_LIST*)+0xc4) [0x78d404]
/usr/sbin/mysqld(mysql_handle_single_derived(st_lex*, TABLE_LIST*, unsigned int)+0xb8) [0x78e3c8]
/usr/sbin/mysqld(st_join_table::preread_init()+0xa1) [0x68b0c1]
/usr/sbin/mysqld(sub_select(JOIN*, st_join_table*, bool)+0x218) [0x69c5b8]
/usr/sbin/mysqld [0x69c983]
/usr/sbin/mysqld(JOIN::exec()+0x9da) [0x6af50a]
/usr/sbin/mysqld(mysql_select(THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*)+0x189) [0x6b1459]
/usr/sbin/mysqld(handle_select(THD*, st_lex*, select_result*, unsigned long)+0x167) [0x6b1e47]
/usr/sbin/mysqld [0x627da1]
/usr/sbin/mysqld(mysql_execute_command(THD*)+0x3b4) [0x62a254]
/usr/sbin/mysqld(mysql_parse(THD*, char*, unsigned int, char const**)+0x29a) [0x63052a]
/usr/sbin/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x52b) [0x630ebb]
/usr/sbin/mysqld(do_command(THD*)+0xf6) [0x631f86]
/usr/sbin/mysqld(handle_one_connection+0xc9) [0x6239d9]
/lib64/libpthread.so.0 [0x358540673d]
/lib64/libc.so.6(clone+0x6d) [0x35848d44bd]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2aab90a06f98): is an invalid pointer
Connection ID (thread ID): 928710
Status: NOT_KILLED
Hi,
I would like to comment that I have the same problem. We used to run (and now still do) MariaDB- server- 5.3.2-102. el5.x86_ 64.rpm, I installed 3 days ago, MariaDB- server- 5.3.5-113. el5.x86_ 64.rpm on a CentOS 5 series server. Within 1 day of running, there was a query done once a day which caused the following crash:
No swap space was every used, the system has 8GB of RAM - I doubt that the system could not allocate 64MB or 151MB as it indicates below. I am afraid that the problem exists past the 5.3.2 release. To be clear, the problem does not exist in 5.3.2 - I have been running that for the last 6 months without a single hickup - and I have been very pleased with that stability.
Steffen
120301 11:56:12 Percona XtraDB (http:// www.percona. com) 1.0.17-13.0 started; log sequence number 1403936934864 MariaDB- ga-mariadb113- log' socket: '/var/lib/ mysql/mysql. sock' port: 3306 (MariaDB - http:// mariadb. com/)
120301 11:56:12 [Note] Event Scheduler: Loaded 0 events
120301 11:56:12 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.3.5-
120302 8:28:05 [ERROR] mysqld: Out of memory (Needed 67372056 bytes)
120302 8:28:05 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
120304 8:27:17 [ERROR] mysqld: Out of memory (Needed 158575640 bytes)
120304 8:27:17 [ERROR] Out of memory; check if mysqld or some other process uses all available memory; if not, you may have to use 'ulimit' to allow mysqld to use more memory or you can add more swap space
2d2d2d d:2d:2d [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: 5.3.5-MariaDB- ga-mariadb113- log size=2147483648 size=2097152 connections= 135 size)*max_ threads = 3128499 K bytes of memory
key_buffer_
read_buffer_
max_used_
max_threads=251
thread_count=71
connection_count=71
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x2aab98687540 mysqld( my_print_ stacktrace+ 0x2e) [0xa0a26e] mysqld( handle_ fatal_signal+ 0x427) [0x741dc7] libpthread. so.0 [0x358540eb10] mysqld( create_ internal_ tmp_table( st_table* , st_key*, st_maria_ columndef* , st_maria_ columndef* *, unsigned long long)+0x218) [0x68a888] mysqld( mysql_derived_ create( THD*, st_lex*, TABLE_LIST*)+0xc4) [0x78d404] mysqld( mysql_handle_ single_ derived( st_lex* , TABLE_LIST*, unsigned int)+0xb8) [0x78e3c8] mysqld( st_join_ table:: preread_ init()+ 0xa1) [0x68b0c1] mysqld( sub_select( JOIN*, st_join_table*, bool)+0x218) [0x69c5b8] mysqld( JOIN::exec( )+0x9da) [0x6af50a] mysqld( mysql_select( THD*, Item***, TABLE_LIST*, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_ lex_unit* , st_select_ lex*)+0x189) [0x6b1459] mysqld( handle_ select( THD*, st_lex*, select_result*, unsigned long)+0x167) [0x6b1e47] mysqld( mysql_execute_ command( THD*)+0x3b4) [0x62a254] mysqld( mysql_parse( THD*, char*, unsigned int, char const**)+0x29a) [0x63052a] mysqld( dispatch_ command( enum_server_ command, THD*, char*, unsigned int)+0x52b) [0x630ebb] mysqld( do_command( THD*)+0xf6) [0x631f86] mysqld( handle_ one_connection+ 0xc9) [0x6239d9] libpthread. so.0 [0x358540673d] libc.so. 6(clone+ 0x6d) [0x35848d44bd]
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 = 514010f8 thread_stack 0x48000
/usr/sbin/
/usr/sbin/
/lib64/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/mysqld [0x69c983]
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/mysqld [0x627da1]
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/usr/sbin/
/lib64/
/lib64/
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (2aab90a06f98): is an invalid pointer
Connection ID (thread ID): 928710
Status: NOT_KILLED
Optimizer switch: index_merge= on,index_ merge_union= on,index_ merge_sort_ union=on, index_merge_ intersection= on,index_ merge_sort_ intersection= off,index_ condition_ pushdown= on,derived_ merge=on, derived_ with_keys= on,firstmatch= on,loosescan= on,materializat ion=on, in_to_exists= on,semijoin= on,partial_ match_rowid_ merge=on, partial_ match_table_ scan=on, subquery_ cache=on, mrr=off, mrr_cost_ based=off, mrr_sort_ keys=off, outer_join_ with_cache= on,semijoin_ with_cache= on,join_ cache_increment al=on,join_ cache_hashed= on,join_ cache_bka= on,optimize_ join_buffer_ size=off, table_eliminati on=on
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.