napsty / check_mysql_write Goto Github PK

# /usr/lib/nagios/plugins/check_mysql_write.sh -H mysqlhost -u monitoring -p supersecret -d monitoring
mysql: [Warning] Using a password on the command line interface can be insecure.
mysql: [Warning] Using a password on the command line interface can be insecure.
OK: Write query successful (UPDATE monitoring SET mytime=1566392156 WHERE host='icinga')

2021-05-01 17:05:03 19 [ERROR] InnoDB: Conflicting lock on table: `monitoring`.`monitoring` index: GEN_CLUST_INDEX that has lock 
RECORD LOCKS space id 8 page no 3 n bits 72 index GEN_CLUST_INDEX of table `monitoring`.`monitoring` trx id 627 lock_mode X locks rec but not gap
Record lock, heap no 2
Record lock, heap no 3
2021-05-01 17:05:03 19 [ERROR] InnoDB: WSREP state: 
2021-05-01 17:05:03 19 [ERROR] WSREP: Thread BF trx_id: 628 thread: 19 seqno: 247 client_state: exec client_mode: high priority transaction_mode: executing applier: 1 toi: 0 local: 0 query: UPDATE monitoring SET mytime=1619879025 WHERE host = 'node3'qd�`
2021-05-01 17:05:03 19 [ERROR] WSREP: Thread BF trx_id: 627 thread: 15 seqno: 248 client_state: exec client_mode: high priority transaction_mode: executing applier: 1 toi: 0 local: 0 query: UPDATE monitoring SET mytime=1619879025 WHERE host = 'node2'qd�`
2021-05-01 17:05:03 0x7f47684d5700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.4.16/storage/innobase/lock/lock0lock.cc line 687
InnoDB: We intentionally generate a memory trap.