[MDEV-12752] Server crashes in net_send_eof, perfschema.hostcache_ipv6_addrinfo_again_allow failed in buildbot with ps-protocol Created: 2017-05-09  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Prepared Statements, 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/8055/steps/test_3/logs/stdio

perfschema.hostcache_ipv6_addrinfo_again_allow w1 [ fail ]  Found warnings/errors in server log file!
        Test ended at 2017-05-08 15:35:53
line
170508 15:35:53 [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.6/mysql-test/var/1/log/mysqld.1.err
ok
 
 - saving '/mnt/buildbot/build/mariadb-10.2.6/mysql-test/var/1/log/perfschema.hostcache_ipv6_addrinfo_again_allow/' to '/mnt/buildbot/build/mariadb-10.2.6/mysql-test/var/log/perfschema.hostcache_ipv6_addrinfo_again_allow/'

170508 15:35:53 [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.6-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 = 61863 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0xb0c005d0
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 = 0xb12b52a0 thread_stack 0x49000
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(my_print_stacktrace+0x32)[0x8cebbd6]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(handle_fatal_signal+0x3c1)[0x859c54d]
[0xb7743400]
/lib/i386-linux-gnu/libc.so.6(+0xbd4a5)[0xb72ae4a5]
/lib/i386-linux-gnu/libc.so.6(fnmatch+0x69)[0xb72afaf9]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld[0x8d0db6a]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_db_keyword_+0x79)[0x8d0e042]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_db_pargs_+0x65)[0x8d0d458]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_Z12net_send_eofP3THDjj+0x18c)[0x8275988]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_ZN8Protocol8send_eofEjj+0x56)[0x8276226]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_ZN8Protocol13end_statementEv+0x1e1)[0x8275f8b]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0x2af1)[0x8337b7e]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_Z10do_commandP3THD+0x73a)[0x83349ca]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1bf)[0x8472120]
/mnt/buildbot/build/mariadb-10.2.6/sql/mysqld(handle_one_connection+0x38)[0x8471eae]


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