[MDEV-8279] main.func_encrypt failed in buildbot Created: 2015-06-07  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Locking, Tests
Affects Version/s: 5.5
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None

Issue Links:
Relates
relates to MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

It is known to happen only once so far; but I'm filing it for the record, because this type of failure is rarely noticed – it only shows up when all other tests pass, and it is not stored in buildbot failures (hence does not show up in the cross-reference report).

http://buildbot.askmonty.org/buildbot/builders/kvm-bintar-centos5-x86/builds/2880/steps/test/logs/stdio

Completed: All 2748 tests were successful.
 
Errors/warnings were found in logfiles during server shutdown after running the
following sequence(s) of tests:
    main.func_encrypt
388 tests were skipped, 177 by the test itself.

main.func_encrypt                        w2 [ pass ]     10
worker[2] > Restart [mysqld.1 - pid: 16900, winpid: 16900] - running with different options '--loose-disable-performance-schema' != '--loose-des-key-file=/usr/local/mariadb-5.5.44-linux-i686/mysql-test/std_data/des_key_file'
***Warnings generated in error logs during shutdown after running tests: main.func_encrypt
 
150606 20:01:48 [ERROR] mysqld got signal 11 ;
Attempting backtrace. You can use the following information to find out

Error log

CURRENT_TEST: main.func_encrypt
150606 20:01:48 [Note] /usr/local/mariadb-5.5.44-linux-i686/bin/mysqld (mysqld 5.5.44-MariaDB-log) starting as process 16901 ...
150606 20:01:48 [Note] Plugin 'InnoDB' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_RSEG' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_UNDO_LOGS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_TRX' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_CMP' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_CMPMEM' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_TABLES' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_INDEXES' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_COLUMNS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_FIELDS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_FOREIGN' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_FOREIGN_COLS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_SYS_STATS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_TABLE_STATS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_INDEX_STATS' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_BUFFER_POOL_PAGES' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_BUFFER_POOL_PAGES_INDEX' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_BUFFER_POOL_PAGES_BLOB' is disabled.
150606 20:01:48 [Note] Plugin 'XTRADB_ADMIN_COMMAND' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_CHANGED_PAGES' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_BUFFER_PAGE' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_BUFFER_PAGE_LRU' is disabled.
150606 20:01:48 [Note] Plugin 'INNODB_BUFFER_POOL_STATS' is disabled.
150606 20:01:48 [Note] Plugin 'BLACKHOLE' is disabled.
150606 20:01:48 [Note] Plugin 'ARCHIVE' is disabled.
150606 20:01:48 [Note] Plugin 'FEDERATED' is disabled.
150606 20:01:48 [Note] Plugin 'FEEDBACK' is disabled.
150606 20:01:48 [Note] Plugin 'partition' is disabled.
150606 20:01:48 [Warning] /usr/local/mariadb-5.5.44-linux-i686/bin/mysqld: unknown variable 'loose-debug-sync-timeout=300'
150606 20:01:48 [Note] Server socket created on IP: '::'.
150606 20:01:48 [Note] Event Scheduler: Loaded 0 events
150606 20:01:48 [Note] /usr/local/mariadb-5.5.44-linux-i686/bin/mysqld: ready for connections.
Version: '5.5.44-MariaDB-log'  socket: '/usr/local/mariadb-5.5.44-linux-i686/mysql-test/var/tmp/2/mysqld.1.sock'  port: 16020  MariaDB Server
150606 20:01:48 [Note] /usr/local/mariadb-5.5.44-linux-i686/bin/mysqld: Normal shutdown
 
150606 20:01:48 [Note] Event Scheduler: Purging the queue. 0 events
150606 20:01:48 [Note] /usr/local/mariadb-5.5.44-linux-i686/bin/mysqld: Shutdown complete
 
150606 20:01:48 [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.5.44-MariaDB-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=0
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61464 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0xb5b89000
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 = 0xb3bb6348 thread_stack 0x48000
mysys/stacktrace.c:246(my_print_stacktrace)[0x87576bd]
sql/signal_handler.cc:153(handle_fatal_signal)[0x8310fab]
[0x939420]
psi/mysql_thread.h:612(inline_mysql_mutex_lock)[0x81bf25e]
sql/handler.cc:692(ha_close_connection(THD*))[0x83120e1]
sql/sql_class.cc:1470(~THD)[0x8184170]
sql/mysqld.cc:2503(unlink_thd(THD*))[0x8123ce3]
sql/mysqld.cc:2608(one_thread_per_connection_end(THD*, bool))[0x8123d87]
sql/sql_connect.cc:1277(do_handle_one_connection(THD*))[0x8278f91]
sql/sql_connect.cc:1183(handle_one_connection)[0x827913c]
perfschema/pfs.cc:1018(pfs_spawn_thread)[0x84836c0]
/lib/libpthread.so.0[0x27e49b]
/lib/libc.so.6(clone+0x5e)[0x38442e]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): 
Connection ID (thread ID): 5
Status: KILL_CONNECTION
 
Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=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_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off
 
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.
Writing a core file
CURRENT_TEST: perfschema.start_server_off



 Comments   
Comment by Elena Stepanova [ 2015-06-07 ]

I could not reproduce it by running the test 1000 times on the same VM.

Generated at Thu Feb 08 07:25:57 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.