Elena Stepanova added a comment - 2017-04-22 15:38 - edited The monitor output started appearing in the error log not because of a deadlock, but because of this: InnoDB: Warning: difficult to find free blocks in InnoDB: the buffer pool (338 search iterations)! InnoDB: 0 failed attempts to flush a page! Consider InnoDB: increasing the buffer pool size. InnoDB: It is also possible that in your Unix version InnoDB: fsync is very slow, or completely frozen inside InnoDB: the OS kernel. Then upgrading to a newer version InnoDB: of your operating system may help. Look at the InnoDB: number of fsyncs in diagnostic info below. InnoDB: Pending flushes (fsync) log: 0; buffer pool: 2 InnoDB: 181000753 OS file reads, 37103888 OS file writes, 3324228 OS fsyncs InnoDB: Starting InnoDB Monitor to print further InnoDB: diagnostics to the standard output. The monitor output is not old, it's unique and up-to-date every time. I suppose you consider it old because of the LATEST DETECTED DEADLOCK part, which is indeed rather old and the same. It's normal, because as the name suggests, it's the latest detected deadlock. There has been no detected deadlocks since then, so the same one is printed every time. Please let us know if you still have any questions/concerns about this.

bulepage added a comment - 2017-04-22 16:41 I don't understand why print every time ? In my opinion the bug is that every minutes ( or less) write to the error log the last detected deadlock (until the server restart, or the disk space aviable).

bulepage added a comment - 2017-04-22 17:03 I find set GLOBAL innodb_status_output=Off; is disable the messages

bulepage added a comment - 2017-04-22 17:56 - edited set global innodb_status_output='ON'; Make a dead lock I make with this https://stackoverflow.com/questions/18994621/percona-pt-deadlock-logger-doesnt-detect-deadlock/19154285#19154285 and in the error log write every minutes last dead lock