Details
-
Type:
Bug
-
Status: Done
-
Priority:
Critical
-
Resolution: Fixed
-
Affects Version/s: 5.5, 5.6, 5.7
-
Fix Version/s: 5.7.21-20, 5.6.39-83.1, 5.5.59-38.11
-
Component/s: None
-
Labels:
Description
I seem to recall having this issue before, maybe something is still missing from the new deployment. When a server instance crashes/asserts in an mtr run, it dumps full stacktraces to the output. These traces should be fully resolved, but it seems that now they aren't :
00:01:05 /mnt/workspace/mysql-5.7-param/BUILD_TYPE/debug/Host/centos6-64/build/client//m: No such file or directory. 00:01:05 Missing separate debuginfo for the main executable file 00:01:05 Try: yum --enablerepo='*-debug*' install /usr/lib/debug/.build-id/1f/8f012dfa493429f0cf0d1c65dc57019cc9df75 00:01:05 [New Thread 32690] 00:01:05 Core was generated by `/mnt/workspace/mysql-5.7-param/BUILD_TYPE/debug/Host/centos6-64/build/client//m'. 00:01:05 Program terminated with signal 6, Aborted. 00:01:05 #0 0x0000003f91e0c97c in ?? () 00:01:05 #0 0x0000003f91e0c97c in ?? () 00:01:05 #1 0x0000000000471246 in ?? () 00:01:05 #2 0x0000003f91d8f120 in ?? () 00:01:05 #3 0x0000000691a6680a in ?? () 00:01:05 #4 0x00007ffe19f1b730 in ?? () 00:01:05 #5 0x0000000000418c6a in ?? () 00:01:05 #6 0x0000000001a4b068 in ?? () 00:01:05 #7 0x0000000601a4b080 in ?? () 00:01:05 #8 0x0000000000000001 in ?? () 00:01:05 #9 0x0000003f91e0f7e0 in ?? () 00:01:05 #10 0x0000000000000001 in ?? () 00:01:05 #11 0x0000000000000000 in ?? () 00:01:05
To see the full error look here and search for the failing test rocksdb.allow_to_start_after_corruption : http://jenkins.percona.com/view/5.7/job/mysql-5.7-param/1307/BUILD_TYPE=debug,Host=centos6-64/consoleFull