Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.3.39
-
None
-
Rockylinux
Description
Mysqldump is crashing upon running below commands
mysqldump -u admin -pusers09@ inventory outward > outward.sql
mysqldump: Couldn't execute 'show fields from `outward`': Lost connection to MySQL server during query (2013)
Logs from Mariadb below
231024 13:42:15 [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.39-MariaDB source revision: ca001cf2048f0152689e1895e2dc15486dd0b1af
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=1
max_threads=153
thread_count=6
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467435 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x7f7cdc000fb8
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 = 0x7f7ce01efc48 thread_stack 0x49000
/usr/libexec/mysqld(my_print_stacktrace+0x41)[0x55dd81d0ceb1]
/usr/libexec/mysqld(handle_fatal_signal+0x4f5)[0x55dd81832c05]
/lib64/libpthread.so.0(+0x12c20)[0x7f7cebe70c20]
Trying to get some variables.
Some pointers may be invalid and cause the dump to abort.
Query (0x7f7cdc011ae0): show fields from `outward`
Connection ID (thread ID): 10
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,materiali$
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file...
Working directory at /var/lib/mysql
Resource Limits:
Limit Soft Limit Hard Limit Units
Attachments
Issue Links
- duplicates
-
MDEV-32563 Describe table1 shows error
-
- Closed
-