Debian Codegraph @

mysql-test/suite/binlog/r/binlog_restart_server_with_exhausted_index_value.result

raw
1 call mtr.add_suppression("Next log extension: 2147483647. Remaining log filename extensions: 0. Please consider archiving some logs");
2 call mtr.add_suppression("Log filename extension number exhausted: 2147483647. Please fix this by archiving old logs and updating the index files.");
3 call mtr.add_suppression("Can't generate a unique log-filename .*");
4 call mtr.add_suppression("MYSQL_BIN_LOG::open failed to generate new file name.");
5 call mtr.add_suppression("Attempting backtrace. You can use the following information to find out*");
6 RESET MASTER;
7 # restart
8 FLUSH BINARY LOGS;
9 ERROR HY000: Binary logging not possible. Message: Can't generate a unique log-filename binlog.(1-999), while rotating the binlog. Aborting the server
10 Occurrences of 'Aborting' in the input file: 1
11 Occurrences of 'MYSQL_BIN_LOG::open failed to generate new file name.' in the input file: 1
12 Occurrences of 'Can't generate a unique log-filename .*' in the input file: 1
13 Occurrences of 'Log filename extension number exhausted: 2147483647. Please fix this by archiving old logs and updating the index files.' in the input file: 1
14 Occurrences of 'Aborting' in the input file: 1
15 Occurrences of 'MYSQL_BIN_LOG::open failed to generate new file name.' in the input file: 1
16 Occurrences of 'Can't generate a unique log-filename .*' in the input file: 1
17 Occurrences of 'Log filename extension number exhausted: 2147483647. Please fix this by archiving old logs and updating the index files.' in the input file: 1
18 # restart