Details
-
Bug
-
Status: Closed (View Workflow)
-
Minor
-
Resolution: Won't Fix
-
10.2
-
None
Description
http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-aarch64/builds/9546
http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-aarch64/builds/9546/steps/mtr/logs/mysqld.1.err.4
|
10.2 620ea816adeceaba7c875679ab8505f4 |
binlog.binlog_no_uniqfile_crash 'mix' w4 [ fail ] Found warnings/errors in server log file!
|
Test ended at 2020-10-21 20:57:39
|
line
|
Attempting backtrace. You can use the following information to find out
|
^ Found warnings in /dev/shm/var/4/log/mysqld.1.err
|
ok
|
Version: '10.2.35-MariaDB-log' socket: '/dev/shm/var/tmp/4/mysqld.1.sock' port: 16060 MariaDB Server
|
2020-10-21 20:57:37 281472642547872 [Warning] Next log extension: 2147483647. Remaining log filename extensions: 0. Please consider archiving some logs.
|
2020-10-21 20:57:37 281472642547872 [ERROR] Log filename extension number exhausted: 2147483647. Please fix this by archiving old logs and updating the index files.
|
2020-10-21 20:57:37 281472642547872 [ERROR] Can't generate a unique log-filename master-bin.(1-999)
|
|
|
2020-10-21 20:57:37 281472642547872 [ERROR] MYSQL_BIN_LOG::open failed to generate new file name.
|
2020-10-21 20:57:37 281472642547872 [ERROR] Could not use master-bin for logging (error 2). Turning logging off for the whole duration of the MySQL server process. To turn it on again: fix the cause, shutdown the MySQL server and restart it.
|
2020-10-21 20:57:37 281472641761440 [Note] /usr/sbin/mysqld (initiated by: root[root] @ localhost []): Normal shutdown
|
201021 20:57: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.2.35-MariaDB-log
|
key_buffer_size=1048576
|
read_buffer_size=131072
|
max_used_connections=2
|
max_threads=153
|
thread_count=2
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63025 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...
|
2020-10-21 20:57:37 281472641761440 [Note] Event Scheduler: Purging the queue. 0 events
|
stack_bottom = 0x0 thread_stack 0x49000
|
2020-10-21 20:57:37 281472641761440 [Note] /usr/sbin/mysqld: Shutdown complete
|
|
|
addr2line: Dwarf Error: Offset (2501149) greater than or equal to .debug_str size (121120).
|
addr2line: Dwarf Error: Offset (6516329) greater than or equal to .debug_str size (2575280).
|
addr2line: Dwarf Error: Could not find abbrev number 108.
|
addr2line: Dwarf Error: Offset (1590519) greater than or equal to .debug_str size (121120).
|
2020-10-21 20:57:38 281473163716240 [Note] /usr/sbin/mysqld (mysqld 10.2.35-MariaDB-log) starting as process 10623 ...
|
|
|