[MDEV-23957] seg fault when loading data Created: 2020-10-14  Updated: 2021-01-31  Resolved: 2021-01-31

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - InnoDB
Affects Version/s: 10.3.22
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Nigel Reed Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: crash, need_feedback
Environment:

Ubuntu 20.04 16GB Ryzen 1800+ CPU.


 Description   

InnoDB: ###### Diagnostic info printed to the standard error stream
2020-10-14 5:01:37 0 [ERROR] [FATAL] InnoDB: Semaphore wait has lasted > 600 seconds. We intentionally crash the server because it appears to be hung.
201014 5:01:37 [ERROR] mysqld got signal 6 ;
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.22-MariaDB-1ubuntu1
key_buffer_size=134217728
read_buffer_size=131072
max_used_connections=5
max_threads=153
thread_count=11
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 467423 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
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 = 0x0 thread_stack 0x49000
/usr/sbin/mysqld(my_print_stacktrace+0x32)[0x557754ef9202]
/usr/sbin/mysqld(handle_fatal_signal+0x55d)[0x5577549cb37d]
sigaction.c:0(__restore_rt)[0x7fa7528a63c0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0xcb)[0x7fa7523b518b]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x12b)[0x7fa752394859]
/usr/sbin/mysqld(+0x4d3ce9)[0x5577546f8ce9]
/usr/sbin/mysqld(+0xa39e3a)[0x557754c5ee3a]
nptl/pthread_create.c:478(start_thread)[0x7fa75289a609]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x43)[0x7fa752491293]
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...
Working directory at /var/lib/mysql
Resource Limits:
Fatal signal 11 while backtracing

 Comments   
Comment by Nigel Reed [ 2020-10-18 ]

How to recreate.
1. On a Windows PC, download and compile using Visual Studio Community edition DiscogsXML2MySQL from https://github.com/nelemans1971/Discogs
2. change into the DiscogsXML2MySQL/bin/release (or debug if you built it) and edit the ini file to point at the mariadb server on the Linux server. User and Pass need to be the root user since it will create a database for you.
3. Run the DiscogsXML2MySQL binary and wait...it'll download 4 large files then start converting to a TAB file, and import into the database. Somewhere along the line mariadb will throw the error below.

I can do a video of the process if that would help.

Comment by Elena Stepanova [ 2021-01-02 ]

nelgin,

Can you instead enable the general log in MariaDB server, run the steps you describe, and provide the general log after the server crashes (and MariaDB's cnf file(s) or the output of SHOW VARIABLES command)?

Thanks.

Comment by Nigel Reed [ 2021-01-03 ]

I wonder if its because the tab delimited files are so big that it's trying to import. Some are over 3 million lines. Maybe I can try adjusting the timeout variables and try again.

Generated at Thu Feb 08 09:26:20 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.