You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
snikolaev@dev2:~$ mysql -P9306 -h0 -v
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 21
Server version: 6.2.13 b826cafe8@231007 dev (columnar 2.2.5 b8be4eb@230928) (secondary 2.2.5 b8be4eb@230928) git branch master...origin/master
Copyright (c) 2000, 2023, Oracle and/or its affiliates.
Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.
Reading history-file /home/snikolaev/.mysql_history
Type 'help;'or'\h' for help. Type '\c' to clear the current input statement.
mysql>droptableif exists t; create table t; insert into t values(1); begin; deletefrom t where id =1; droptableif exists t; create table t; commit;
--------------droptable if exists t
--------------
Query OK, 0 rows affected (0.03 sec)
--------------createtablet--------------
Query OK, 0 rows affected (0.00 sec)
--------------insert into t values(1)
--------------
Query OK, 1 row affected (0.00 sec)
--------------begin--------------
Query OK, 0 rows affected (0.00 sec)
--------------deletefrom t where id =1--------------
Query OK, 0 rows affected (0.00 sec)
--------------droptable if exists t
--------------
Query OK, 0 rows affected (0.03 sec)
--------------createtablet--------------
Query OK, 0 rows affected (0.00 sec)
--------------commit--------------
ERROR 2013 (HY000): Lost connection to MySQL server during query
No connection. Trying to reconnect...
ERROR 2003 (HY000): Can't connect to MySQL server on '0:9306' (111)ERROR:Can't connect to the server
You may require to run the one-liner 2-3 times for the crash to appear.
Crash log:
--- crashed SphinxQL request dump ---
commit
--- request dump end ---
--- local index:
Manticore 6.2.13 b826cafe8@231007 dev (columnar 2.2.5 b8be4eb@230928) (secondary 2.2.5 b8be4eb@230928)
Handling signal 11
-------------- backtrace begins here ---------------
Program compiled with Clang 15.0.7
Configured with flags: Configured with these definitions: -DDISTR_BUILD=jammy -DUSE_SYSLOG=1 -DWITH_GALERA=1 -DWITH_RE2=1 -DWITH_RE2_FORCE_STATIC=1 -DWITH_STEMMER=1 -DWITH_STEMMER_FORCE_STATIC=1 -DWITH_NLJ
SON=1 -DWITH_UNIALGO=1 -DWITH_ICU=1 -DWITH_ICU_FORCE_STATIC=1 -DWITH_SSL=1 -DWITH_ZLIB=1 -DWITH_ZSTD=1 -DDL_ZSTD=1 -DZSTD_LIB=libzstd.so.1 -DWITH_CURL=1 -DDL_CURL=1 -DCURL_LIB=libcurl.so.4 -DWITH_ODBC=1 -D
DL_ODBC=1 -DODBC_LIB=libodbc.so.2 -DWITH_EXPAT=1 -DDL_EXPAT=1 -DEXPAT_LIB=libexpat.so.1 -DWITH_ICONV=1 -DWITH_MYSQL=1 -DDL_MYSQL=1 -DMYSQL_LIB=libmysqlclient.so.21 -DWITH_POSTGRESQL=1 -DDL_POSTGRESQL=1 -DP
OSTGRESQL_LIB=libpq.so.5 -DLOCALDATADIR=/var/lib/manticore -DFULL_SHARE_DIR=/usr/share/manticore
Built on Linux x86_64 (jammy) (cross-compiled)
Stack bottom = 0x7fd05c043f60, thread stack size = 0x20000
Trying manual backtrace:
Something wrong with thread stack, manual backtrace may be incorrect (fp=0x1)
Wrong stack limit or frame pointer, manual backtrace failed (fp=0x1, stack=0x7fd05c050000, stacksize=0x20000)
Trying system backtrace:
begin of system symbols:
/usr/bin/searchd(_Z12sphBacktraceib+0x22a)[0x564e75cc4a4a]
/usr/bin/searchd(_ZN11CrashLogger11HandleCrashEi+0x355)[0x564e75b3e585]
/lib/x86_64-linux-gnu/libc.so.6(+0x42520)[0x7fd0e7849520]
Trying boost backtrace:
0# sphBacktrace(int, bool) in /usr/bin/searchd
1# CrashLogger::HandleCrash(int) in /usr/bin/searchd
2# 0x00007FD0E7849520 in /lib/x86_64-linux-gnu/libc.so.6
-------------- backtrace ends here ---------------
Please, create a bug report in our bug tracker (https://github.com/manticoresoftware/manticore/issues)
and attach there:
a) searchd log, b) searchd binary, c) searchd symbols.
Look into the chapter 'Reporting bugs' in the manual
(https://manual.manticoresearch.com/Reporting_bugs)
Dump with GDB via watchdog
[Fri Oct 13 13:17:54.260 2023] [1680068] [BUDDY] Sharding Event: ping []
The text was updated successfully, but these errors were encountered:
MRE
You may require to run the one-liner 2-3 times for the crash to appear.
Crash log:
The text was updated successfully, but these errors were encountered: