[MDEV-10696] perfschema.hostcache_ipv6_ssl failed in buildbot: server crashed on shutdown Created: 2016-08-28  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: SSL, Tests
Affects Version/s: 10.0, 10.2
Fix Version/s: N/A

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

Issue Links:
Blocks
blocks MDEV-7069 Fix buildbot failures in main server ... Stalled

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/5776/steps/test_7/logs/stdio

perfschema.hostcache_ipv6_ssl            w1 [ fail ]
        Test ended at 2016-08-26 03:31:42
 
CURRENT_TEST: perfschema.hostcache_ipv6_ssl
 
 
Server [mysqld.1 - pid: 5430, winpid: 5430, exit: 256] failed during test run
Server log from this test:
----------SERVER LOG START-----------
160826  3:31:38 [Note] X509 subject mismatch: should be '/C=??/ST=??/L=??/
    O=No such thing/
    CN=Santa Claus/emailAddress=santa.claus@example.com' but is '/C=FI/ST=Helsinki/L=Helsinki/O=MariaDB/CN=client'
160826  3:31:38 [Note] X509 subject mismatch: should be '/C=??/ST=??/L=??/
    O=No such thing/
    CN=Santa Claus/emailAddress=santa.claus@example.com' but is '/C=FI/ST=Helsinki/L=Helsinki/O=MariaDB/CN=client'
160826  3:31:38 [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 https://mariadb.com/kb/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.28-MariaDB-debug
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=3
max_threads=153
thread_count=2
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61724 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x0xbca8850
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 = 0xb1bff29c thread_stack 0x48000
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(my_print_stacktrace+0x29)[0x8abd1a9]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(handle_fatal_signal+0x550)[0x83e3fe0]
[0xc70400]
/lib/i386-linux-gnu/libc.so.6(+0x7b678)[0x55d678]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld[0x8ad5aab]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(_db_keyword_+0x70)[0x8ad6610]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(_Z10unlink_thdP3THD+0x217)[0x81802f7]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(_Z29one_thread_per_connection_endP3THDb+0x54)[0x8180414]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(_Z24do_handle_one_connectionP3THD+0x133)[0x832ec33]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld(handle_one_connection+0x4f)[0x832ed9f]
/mnt/buildbot/build/mariadb-10.0.28/sql/mysqld[0x85bccaa]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xe22d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0x5ccace]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): 
Connection ID (thread ID): 125
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=on,exists_to_in=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.
Writing a core file
----------SERVER LOG END-------------
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
COUNT_FCRDNS_ERRORS	0
COUNT_HOST_ACL_ERRORS	0
COUNT_NO_AUTH_PLUGIN_ERRORS	0
COUNT_AUTH_PLUGIN_ERRORS	0
COUNT_HANDSHAKE_ERRORS	0
COUNT_PROXY_USER_ERRORS	0
COUNT_PROXY_USER_ACL_ERRORS	0
COUNT_AUTHENTICATION_ERRORS	0
COUNT_SSL_ERRORS	4
COUNT_MAX_USER_CONNECTIONS_ERRORS	0
COUNT_MAX_USER_CONNECTIONS_PER_HOUR_ERRORS	0
COUNT_DEFAULT_DATABASE_ERRORS	0
COUNT_INIT_CONNECT_ERRORS	0
COUNT_LOCAL_ERRORS	0
COUNT_UNKNOWN_ERRORS	0
FIRST_ERROR_SEEN	set
LAST_ERROR_SEEN	set
drop user 'user_ssl'@'santa.claus.ipv6.example.com';
drop user 'user_ssl_x509'@'santa.claus.ipv6.example.com';
set global debug_dbug= default;

According to cross-reference, it was the first time it ever happened.



 Comments   
Comment by Sergei Golubchik [ 2017-01-04 ]

The stack trace shows a crash in db_keyword. It's inside dbug, may be some race condition on shutdown. Must be a very rare, if it only has happened once. Either way, being a dbug issue it cannot possibly affect release builds.

Comment by Elena Stepanova [ 2017-07-06 ]

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/8718/steps/test_2/logs/stdio

perfschema.hostcache_ipv6_ssl            w3 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2017-07-05 15:38:06
line
170705 15:38:06 [ERROR] mysqld got signal 11 ;
Attempting backtrace. You can use the following information to find out
^ Found warnings in /mnt/buildbot/build/mariadb-10.2.7/mysql-test/var/3/log/mysqld.1.err
ok

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