2019-06-14 11:48:22 34947827200 [Note] Suppressing warnings of type 'The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted.' for up to 300 seconds because of flooding
190614 12:26:01 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2019-06-14 12:26:02 34422751232 [Note] /usr/local/libexec/mysqld (mysqld 10.1.35-MariaDB) starting as process 84009 ...
2019-06-14 12:26:03 34422751232 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-06-14 12:26:03 34422751232 [Note] InnoDB: The InnoDB memory heap is disabled
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-14 12:26:03 34422751232 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Using SSE crc32 instructions
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Completed initialization of buffer pool
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-14 12:26:03 34422751232 [Note] InnoDB: Starting crash recovery from checkpoint LSN=371199792870
2019-06-14 12:26:19 34422751232 [Note] InnoDB: Processed 2189 .ibd/.isl files
2019-06-14 12:26:35 34422751232 [Note] InnoDB: Processed 3850 .ibd/.isl files
2019-06-14 12:26:36 34422751232 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
2019-06-14 12:26:37 34422751232 [Note] InnoDB: Read redo log up to LSN=371199923712
2019-06-14 12:26:37 34422751232 [Note] InnoDB: Starting final batch to recover 54 pages from redo log
InnoDB: Last MySQL binlog file position 0 793748930, file name ./mysql-bin.000477
2019-06-14 12:26:38 34422751232 [Note] InnoDB: 128 rollback segment(s) are active.
2019-06-14 12:26:38 34422751232 [Note] InnoDB: Waiting for purge to start
2019-06-14 12:26:38 34422751232 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 371199889554
2019-06-14 12:26:39 34937568256 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-06-14 12:26:39 34422751232 [Note] Plugin 'FEEDBACK' is disabled.
2019-06-14 12:26:39 34422751232 [Note] Recovering after a crash using mysql-bin
2019-06-14 12:26:52 34422751232 [Note] Starting crash recovery...
2019-06-14 12:26:52 34422751232 [Note] Crash recovery finished.
2019-06-14 12:26:52 34937570816 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2019-06-14 12:26:52 34937570816 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
2019-06-14 12:26:52 34422751232 [Note] Server socket created on IP: '0.0.0.0'.
2019-06-14 12:26:52 34919731200 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2019-06-14 12:26:52 34919731200 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
2019-06-14 12:26:53 34422751232 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '10.1.35-MariaDB' socket: '/tmp/mysql.sock' port: 3306 FreeBSD Ports
2019-06-14 12:26:53 34919744000 [Warning] IP address '10.44.1.17' could not be resolved: hostname nor servname provided, or not known
2019-06-14 12:26:53 821610200 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2019-06-14 12:26:56 34919747840 [Warning] IP address '10.44.1.19' could not be resolved: hostname nor servname provided, or not known
2019-06-14 12:27:10 34920638464 [Warning] IP address '10.44.1.16' could not be resolved: hostname nor servname provided, or not known
2019-06-14 12:27:10 34920642304 [Warning] IP address '10.44.1.24' could not be resolved: hostname nor servname provided, or not known
2019-06-14 12:27:35 34920644864 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE equ_posts SET post_password = '49bc8767c29283e1ff89', post_modified_gmt = '2019-06-14 12:27:35', post_modified = '2019-06-14 12:27:35' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:27:35' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:27:36 34939028736 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '22e198294124210ec5c7', post_modified_gmt = '2019-06-14 12:27:36', post_modified = '2019-06-14 12:27:36' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:27:36' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:29:14 34920644864 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE equ_posts SET post_password = 'c438b9fb6876df8facad', post_modified_gmt = '2019-06-14 12:29:14', post_modified = '2019-06-14 12:29:14' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:29:14' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:29:49 34742540288 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '91c0b7450542f503f821', post_modified_gmt = '2019-06-14 12:29:49', post_modified = '2019-06-14 12:29:49' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:29:49' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:30:34 34939032576 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE equ_posts SET post_password = 'e0e138f742abf66c79dd', post_modified_gmt = '2019-06-14 12:30:34', post_modified = '2019-06-14 12:30:34' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:30:34' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:30:36 34939028736 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = '3d664c18b45aca82147c', post_modified_gmt = '2019-06-14 12:30:36', post_modified = '2019-06-14 12:30:36' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:30:36' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:31:37 34921200384 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'c9b0fe702bb497bb3c56', post_modified_gmt = '2019-06-14 12:31:37', post_modified = '2019-06-14 12:31:37' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:31:37' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:31:54 34921196544 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE equ_posts SET post_password = 'abe59a15d694a582c4d6', post_modified_gmt = '2019-06-14 12:31:54', post_modified = '2019-06-14 12:31:54' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:31:54' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:32:12 34920646144 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. Statements writing to a table with an auto-increment column after selecting from another table are unsafe because the order in which rows are retrieved determines what (if any) rows will be written. This order cannot be predicted and may differ on master and the slave. Statement: DELETE FROM sfk_wps_key WHERE key_id NOT IN (SELECT key_id FROM sfk_wps_index)
2019-06-14 12:32:33 34939470848 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'b1e2be118f35e08135d3', post_modified_gmt = '2019-06-14 12:32:33', post_modified = '2019-06-14 12:32:33' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:32:33' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:33:02 34921196544 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE equ_posts SET post_password = 'b4723ba64ab27b4d9d3d', post_modified_gmt = '2019-06-14 12:33:02', post_modified = '2019-06-14 12:33:02' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:33:02' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:33:30 34920644864 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'b750c4fbb66e4d053f1c', post_modified_gmt = '2019-06-14 12:33:30', post_modified = '2019-06-14 12:33:30' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:33:30' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:34:34 34920644864 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE equ_posts SET post_password = '4f4afefd85bc00545f94', post_modified_gmt = '2019-06-14 12:34:34', post_modified = '2019-06-14 12:34:34' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:34:34' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:34:39 34921605632 [Warning] Unsafe statement written to the binary log using statement format since BINLOG_FORMAT = STATEMENT. The statement is unsafe because it uses a LIMIT clause. This is unsafe because the set of rows included cannot be predicted. Statement: UPDATE sfk_posts SET post_password = 'f8d10dcea2d271308c1d', post_modified_gmt = '2019-06-14 12:34:39', post_modified = '2019-06-14 12:34:39' WHERE post_type = 'scheduled-action' AND post_status = 'pending' AND post_password = '' AND post_date_gmt <= '2019-06-14 12:34:39' ORDER BY menu_order ASC, post_date_gmt ASC, ID ASC LIMIT 25
2019-06-14 12:35:46 34920644864 [Note] /usr/local/libexec/mysqld: Normal shutdown
2019-06-14 12:35:46 34920644864 [Note] Event Scheduler: Purging the queue. 0 events
2019-06-14 12:35:46 34937563136 [Note] InnoDB: FTS optimize thread exiting.
2019-06-14 12:35:46 34920644864 [Note] InnoDB: Starting shutdown...
2019-06-14 12:35:48 34920644864 [Note] InnoDB: Waiting for page_cleaner to finish flushing of buffer pool
2019-06-14 12:35:50 34920644864 [Note] InnoDB: Shutdown completed; log sequence number 371202803765
2019-06-14 12:35:50 34920644864 [Note] /usr/local/libexec/mysqld: Shutdown complete
190614 12:35:50 mysqld_safe mysqld from pid file /var/db/mysql/mariadb.trinitech.co.uk.pid ended
190614 12:42:01 mysqld_safe Starting mysqld daemon with databases from /var/db/mysql
2019-06-14 12:42:01 34422751232 [Note] /usr/local/libexec/mysqld (mysqld 10.1.35-MariaDB) starting as process 24344 ...
2019-06-14 12:42:01 34422751232 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2019-06-14 12:42:01 34422751232 [Note] InnoDB: The InnoDB memory heap is disabled
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2019-06-14 12:42:01 34422751232 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Compressed tables use zlib 1.2.11
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Using SSE crc32 instructions
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Completed initialization of buffer pool
2019-06-14 12:42:01 34422751232 [Note] InnoDB: Highest supported file format is Barracuda.
2019-06-14 12:42:03 34422751232 [Note] InnoDB: 128 rollback segment(s) are active.
2019-06-14 12:42:03 34422751232 [Note] InnoDB: Waiting for purge to start
2019-06-14 12:42:03 34422751232 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 371202803765
2019-06-14 12:42:03 34930345728 [Note] InnoDB: Dumping buffer pool(s) not yet started
2019-06-14 12:42:03 34422751232 [Note] Plugin 'FEEDBACK' is disabled.
2019-06-14 12:42:03 34930348288 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2019-06-14 12:42:03 34930348288 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
2019-06-14 12:42:03 34422751232 [Note] Server socket created on IP: '0.0.0.0'.
2019-06-14 12:42:04 34930350848 [Warning] InnoDB: Cannot open table mysql/gtid_slave_pos from the internal data dictionary of InnoDB though the .frm file for the table exists. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting.html for how you can resolve the problem.
2019-06-14 12:42:04 34930350848 [Warning] Failed to load slave replication state from table mysql.gtid_slave_pos: 1932: Table 'mysql.gtid_slave_pos' doesn't exist in engine
2019-06-14 12:42:04 34422751232 [Note] /usr/local/libexec/mysqld: ready for connections.
Version: '10.1.35-MariaDB' socket: '/tmp/mysql.sock' port: 3306 FreeBSD Ports
2019-06-14 12:42:19 34745351424 [Warning] IP address '10.44.1.19' could not be resolved: hostname nor servname provided, or not known
2019-06-14 12:42:19 816fbfd00 InnoDB: Error: Table "mysql"."innodb_table_stats" not found.
2019-06-14 12:42:26 34948297472 [Warning] IP address '10.44.1.17' could not be resolved: hostname nor servname provided, or not known