store | blogs | forums | twitter | facebook | wiki | downloads | support portal
Atomic Secure Linux
It is currently Mon Oct 14, 2019 8:55 am

» Feed - Atomicorp

All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 5 posts ] 
Author Message
 Post subject: mysqld 5.5.32-18.el5.art for i386 dies with signal 11
Unread postPosted: Tue Jun 18, 2013 8:17 pm 
Offline
Forum User
Forum User

Joined: Thu Feb 02, 2012 7:54 pm
Posts: 10
Location: Melbourne
130619 10:06:23 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130619 10:06:23 [Note] Plugin 'FEDERATED' is disabled.
130619 10:06:23 InnoDB: The InnoDB memory heap is disabled
130619 10:06:23 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
130619 10:06:23 InnoDB: Compressed tables use zlib 1.2.3
130619 10:06:23 InnoDB: Using Linux native AIO
130619 10:06:23 InnoDB: Initializing buffer pool, size = 512.0M
130619 10:06:23 InnoDB: Completed initialization of buffer pool
00:06:23 UTC - 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=8388608
read_buffer_size=2097152
max_used_connections=0
max_threads=300
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1239190 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0 thread_stack 0x30000
/usr/libexec/mysqld(my_print_stacktrace+0x33)[0x8421993]
/usr/libexec/mysqld(handle_fatal_signal+0x42b)[0x82d2fcb]
[0xd29420]
/lib/libz.so.1(adler32+0xe6)[0x98d796]
/usr/libexec/mysqld[0x85a1f21]
/usr/libexec/mysqld[0x8512aa7]
/usr/libexec/mysqld[0x85444f3]
/usr/libexec/mysqld[0x8544e21]
/usr/libexec/mysqld[0x84c888b]
/usr/libexec/mysqld[0x848cb8b]
/usr/libexec/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x4e)[0x82d52ee]
/usr/libexec/mysqld[0x81b4ab7]
/usr/libexec/mysqld(_Z11plugin_initPiPPci+0xb98)[0x81b8228]
/usr/libexec/mysqld[0x81293ab]
/usr/libexec/mysqld(_Z11mysqld_mainiPPc+0x6d8)[0x812c8a8]
/usr/libexec/mysqld(main+0x32)[0x8121022]
/lib/libc.so.6(__libc_start_main+0xdc)[0x9ebebc]
/usr/libexec/mysqld[0x8120f31]
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.
130619 10:06:23 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

mysql> show variables like '%size%';
+---------------------------------------------------+----------------------+
| Variable_name | Value |
+---------------------------------------------------+----------------------+
| binlog_cache_size | 32768 |
| binlog_stmt_cache_size | 32768 |
| bulk_insert_buffer_size | 8388608 |
| delayed_queue_size | 1000 |
| innodb_additional_mem_pool_size | 8388608 |
| innodb_buffer_pool_size | 536870912 |
| innodb_log_buffer_size | 8388608 |
| innodb_log_file_size | 5242880 |
| innodb_purge_batch_size | 20 |
| join_buffer_size | 131072 |
| key_buffer_size | 8388608 |
| key_cache_block_size | 1024 |
| large_page_size | 0 |
| max_binlog_cache_size | 18446744073709547520 |
| max_binlog_size | 1073741824 |
| max_binlog_stmt_cache_size | 18446744073709547520 |
| max_heap_table_size | 4194304 |
| max_join_size | 18446744073709551615 |
| max_long_data_size | 8388608 |
| max_relay_log_size | 0 |
| metadata_locks_cache_size | 1024 |
| myisam_data_pointer_size | 6 |
| myisam_max_sort_file_size | 2146435072 |
| myisam_mmap_size | 4294967295 |
| myisam_sort_buffer_size | 8388608 |
| performance_schema_events_waits_history_long_size | 10000 |
| performance_schema_events_waits_history_size | 10 |
| preload_buffer_size | 32768 |
| profiling_history_size | 15 |
| query_alloc_block_size | 8192 |
| query_cache_size | 0 |
| query_prealloc_size | 8192 |
| range_alloc_block_size | 4096 |
| read_buffer_size | 2097152 |
| read_rnd_buffer_size | 262144 |
| sort_buffer_size | 2097152 |
| sql_max_join_size | 18446744073709551615 |
| thread_cache_size | 8 |
| tmp_table_size | 4294967296 |
| transaction_alloc_block_size | 8192 |
| transaction_prealloc_size | 4096 |
+---------------------------------------------------+----------------------+
41 rows in set (0.00 sec)

mysql> show engines;
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| Engine | Support | Comment | Transactions | XA | Savepoints |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
| MyISAM | YES | MyISAM storage engine | NO | NO | NO |
| CSV | YES | CSV storage engine | NO | NO | NO |
| MRG_MYISAM | YES | Collection of identical MyISAM tables | NO | NO | NO |
| BLACKHOLE | YES | /dev/null storage engine (anything you write to it disappears) | NO | NO | NO |
| MEMORY | YES | Hash based, stored in memory, useful for temporary tables | NO | NO | NO |
| FEDERATED | NO | Federated MySQL storage engine | NULL | NULL | NULL |
| ARCHIVE | YES | Archive storage engine | NO | NO | NO |
| PERFORMANCE_SCHEMA | YES | Performance Schema | NO | NO | NO |
| InnoDB | DEFAULT | Supports transactions, row-level locking, and foreign keys | YES | YES | YES |
+--------------------+---------+----------------------------------------------------------------+--------------+------+------------+
9 rows in set (0.00 sec)

Reverting to the previous build fixed the sigsegv problem.


Top
 Profile  
Reply with quote  
 Post subject: Re: mysqld 5.5.32-18.el5.art for i386 dies with signal 11
Unread postPosted: Tue Jun 18, 2013 11:44 pm 
Offline
Forum User
Forum User

Joined: Thu Feb 02, 2012 7:54 pm
Posts: 10
Location: Melbourne
The crash seems to be particular to a specific machine, on two other Centos 5.9 32bit servers the latest 5.5.32 from your repo starts properly.
The build I'm currently using at the moment on the troubled machine is mysql-server-5.5.31-16.art rebuilt on that machine using your src.rpm.


Top
 Profile  
Reply with quote  
 Post subject: Re: mysqld 5.5.32-18.el5.art for i386 dies with signal 11
Unread postPosted: Wed Jun 19, 2013 8:45 am 
Offline
Atomicorp Staff - Site Admin
Atomicorp Staff - Site Admin

Joined: Wed Dec 31, 1969 8:00 pm
Posts: 8329
Location: earth
signal 11 is usually memory related, Id back off your my.cnf settings to a default config and run your tests again. You might have overly tweaked it.


Top
 Profile  
Reply with quote  
 Post subject: Re: mysqld 5.5.32-18.el5.art for i386 dies with signal 11
Unread postPosted: Mon Jul 08, 2013 8:19 pm 
Offline
Forum User
Forum User

Joined: Thu Feb 02, 2012 7:54 pm
Posts: 10
Location: Melbourne
Steve, I'm back, but still no better news. The latest 5.5.32-19.art log output looks quite a bit different this time. Needless to say reverting back to 5.5.31-16.art resolves the issue. At the moment it's more of a fyi post because I can't replicate it anywhere else and the affected machine is in production, thus I can't use it for testing.

130709 10:06:14 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
130709 10:06:14 [Note] libgovernor.so not found
130709 10:06:14 [Note] Plugin 'FEDERATED' is disabled.
130709 10:06:14 InnoDB: The InnoDB memory heap is disabled
130709 10:06:14 InnoDB: Mutexes and rw_locks use InnoDB's own implementation
130709 10:06:14 InnoDB: Compressed tables use zlib 1.2.3
130709 10:06:14 InnoDB: Using Linux native AIO
130709 10:06:14 InnoDB: Initializing buffer pool, size = 512.0M
130709 10:06:14 InnoDB: Completed initialization of buffer pool
InnoDB: Error: checksum mismatch in data file ./ibdata0
130709 10:06:14 InnoDB: Could not open or create data files.
130709 10:06:14 InnoDB: If you tried to add new data files, and it failed here,
130709 10:06:14 InnoDB: you should now edit innodb_data_file_path in my.cnf back
130709 10:06:14 InnoDB: to what it was, and remove the new ibdata files InnoDB created
130709 10:06:14 InnoDB: in this failed attempt. InnoDB only wrote those files full of
130709 10:06:14 InnoDB: zeros, but did not yet use them in any way. But be careful: do not
130709 10:06:14 InnoDB: remove old data files which contain your precious data!
130709 10:06:14 [ERROR] Plugin 'InnoDB' init function returned error.
130709 10:06:14 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
/usr/libexec/mysqld, Version: 5.5.32-cll-lve (MySQL Community Server (GPL) by Atomicorp). started with:
Tcp port: 0 Unix socket: /var/lib/mysql/mysql.sock
Time Id Command Argument
130709 10:06:14 [ERROR] Unknown/unsupported storage engine: InnoDB
130709 10:06:14 [ERROR] Aborting

130709 10:06:14 [Note] /usr/libexec/mysqld: Shutdown complete

130709 10:06:14 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

Later edit: well, it appears to be an upstream regression in 5.5.32 and 5.6.12:
http://bugs.mysql.com/bug.php?id=69623


Top
 Profile  
Reply with quote  
 Post subject: Re: mysqld 5.5.32-18.el5.art for i386 dies with signal 11
Unread postPosted: Sun Aug 04, 2013 7:35 pm 
Offline
Forum User
Forum User

Joined: Thu Feb 02, 2012 7:54 pm
Posts: 10
Location: Melbourne
Just fyi, 5.5.33-20.el5.art fixes the crash. Thanks.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 5 posts ] 

» Feed - Atomicorp

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group