[MDEV-13260] perfschema.hostcache_ipv6_addrinfo_bad_allow failed in buildbot (server crashed) Created: 2017-07-06  Updated: 2023-11-29  Resolved: 2023-11-29

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

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


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/8655/steps/test_2/logs/mysqld.1.err.2

Version: '10.2.7-MariaDB-debug-log'  socket: '/mnt/buildbot/build/mariadb-10.2.7/mysql-test/var/tmp/2/mysqld.1.sock'  port: 16020  Source distribution
2017-07-01 13:17:20 2983562048 [Warning] Host name 'santa.claus.ipv6.example.com' could not be resolved: Temporary failure in name resolution
2017-07-01 13:17:20 2983865152 [Warning] Host name 'santa.claus.ipv6.example.com' could not be resolved: Temporary failure in name resolution
CURRENT_TEST: perfschema.hostcache_ipv6_addrinfo_again_deny
2017-07-01 13:17:21 2971663168 [Warning] Host name 'santa.claus.ipv6.example.com' could not be resolved: Temporary failure in name resolution
2017-07-01 13:17:21 2983865152 [Warning] Host name 'santa.claus.ipv6.example.com' could not be resolved: Temporary failure in name resolution
CURRENT_TEST: perfschema.hostcache_ipv6_addrinfo_bad_allow
2017-07-01 13:17:21 2983562048 [Warning] Hostname 'santa.claus.ipv6.example.com' does not resolve to '2001:db8::6:6'.
2017-07-01 13:17:21 2983562048 [Note] Hostname 'santa.claus.ipv6.example.com' has the following IP addresses:
2017-07-01 13:17:21 2983562048 [Note]  - 2001:db8::6:7e
2017-07-01 13:17:21 2983562048 [Note]  - 2001:db8::6:7f
170701 13:17:21 [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.2.7-MariaDB-debug-log
key_buffer_size=1048576
read_buffer_size=131072
max_used_connections=3
max_threads=153
thread_count=4
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61867 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0xb0b005d0
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 = 0xb1d582a0 thread_stack 0x49000
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(my_print_stacktrace+0x32)[0x8cef0b6]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(handle_fatal_signal+0x3c7)[0x859f527]
[0xb771e400]
/lib/i386-linux-gnu/libc.so.6(+0xbd4a5)[0xb72894a5]
/lib/i386-linux-gnu/libc.so.6(fnmatch+0x69)[0xb728aaf9]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld[0x8d11332]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(_db_keyword_+0x79)[0x8d1180a]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(_db_pargs_+0x65)[0x8d10c20]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(my_net_set_read_timeout+0x50)[0x8271f19]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(_Z10do_commandP3THD+0x684)[0x8336818]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1bf)[0x8474c64]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld(handle_one_connection+0x38)[0x84749f2]
/mnt/buildbot/build/mariadb-10.2.7/sql/mysqld[0x87aefe8]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb74a6d4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb72b6ace]
 
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x0): 
Connection ID (thread ID): 20
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,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,orderby_uses_equalities=on,condition_pushdown_for_derived=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


Generated at Thu Feb 08 08:04:10 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.