[MDEV-20145] CONNECT engine - ERROR 2013 (HY000): Lost connection to MySQL server during query Created: 2019-07-24  Updated: 2020-11-15  Resolved: 2020-11-15

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Connect
Affects Version/s: 10.3.16, 10.4.6
Fix Version/s: N/A

Type: Bug Priority: Critical
Reporter: Seonghwan Kim Assignee: Anel Husakovic
Resolution: Incomplete Votes: 0
Labels: need_feedback
Environment:

VMWare, CentOS 7.5, MariaDB 10.3.16, MariaDB 10.4.6


Issue Links:
Relates
relates to MDEV-20201 Connecting to remote MySQL via ODBC c... Closed

 Description   

root@localhost [abc] 10:02> create table migtb1_from_ms engine=connect connection='dsn=firebird_test;uid=SYSDBA;pwd=masterkey;dbname=192.168.116.173:/var/lib/firebird/data/employee.fdb' table_type=odbc tabname=country;
ERROR 2013 (HY000): Lost connection to MySQL server during query
root@localhost [abc] 10:02> 
 
Error Log : 
190724 10:02:46 [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.3.16-MariaDB-log
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=1026
thread_count=7
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2386710 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
 
Thread pointer: 0x7f185c000a88
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 = 0x7f18615adec0 thread_stack 0x49000
2019-07-24 10:02:46 0 [Note] CONNECT: Version 1.06.0009 January 27, 2019
2019-07-24 10:02:46 0 [Note] InnoDB: Using Linux native AIO
2019-07-24 10:02:46 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-07-24 10:02:46 0 [Note] InnoDB: Uses event mutexes
2019-07-24 10:02:46 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-07-24 10:02:46 0 [Note] InnoDB: Number of pools: 1
2019-07-24 10:02:46 0 [Note] InnoDB: Using SSE2 crc32 instructions
2019-07-24 10:02:46 0 [Note] InnoDB: Initializing buffer pool, total size = 256M, instances = 1, chunk size = 128M
2019-07-24 10:02:46 0 [Note] InnoDB: Completed initialization of buffer pool
2019-07-24 10:02:46 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
2019-07-24 10:02:46 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=1630158
2019-07-24 10:02:46 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2019-07-24 10:02:46 0 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-07-24 10:02:46 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2019-07-24 10:02:46 0 [Note] InnoDB: Setting file '/MARIADB_DATA/DATA/ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2019-07-24 10:02:46 0 [Note] InnoDB: File '/MARIADB_DATA/DATA/ibtmp1' size is now 12 MB.
2019-07-24 10:02:46 0 [Note] InnoDB: Waiting for purge to start
2019-07-24 10:02:46 0 [Note] InnoDB: 10.3.16 started; log sequence number 1630167; transaction id 23
2019-07-24 10:02:46 0 [Note] InnoDB: Loading buffer pool(s) from /MARIADB_DATA/DATA/ib_buffer_pool
2019-07-24 10:02:46 0 [Note] InnoDB: Buffer pool(s) load completed at 190724 10:02:46
2019-07-24 10:02:46 0 [Note] Plugin 'FEEDBACK' is disabled.
2019-07-24 10:02:46 0 [Note] Recovering after a crash using tc.log
2019-07-24 10:02:46 0 [Note] Starting crash recovery...
2019-07-24 10:02:46 0 [Note] Crash recovery finished.
2019-07-24 10:02:46 0 [Note] Server socket created on IP: '::'.
2019-07-24 10:02:46 0 [Warning] 'user' entry 'root@dbtest1' ignored in --skip-name-resolve mode.
2019-07-24 10:02:46 0 [Warning] 'user' entry '@dbtest1' ignored in --skip-name-resolve mode.
2019-07-24 10:02:46 0 [Warning] 'proxies_priv' entry '@% root@dbtest1' ignored in --skip-name-resolve mode.
2019-07-24 10:02:46 0 [Note] Reading of all Master_info entries succeeded
2019-07-24 10:02:46 0 [Note] Added new Master_info '' to hash table
2019-07-24 10:02:46 0 [Note] /MARIADB/mariadb/bin/mysqld: ready for connections.
Version: '10.3.16-MariaDB-log'  socket: '/tmp/mariadb.sock'  port: 3306  MariaDB Server



 Comments   
Comment by Olivier Bertrand [ 2019-07-28 ]

Sorry but because the error log backtrace doesn't contain anything about CONNECT, I am not able to try fixing this bug. You may try to provide more information by setting connect_xtrace to 1023.

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