the new stable release 2.3.0p17 of Checkmk is ready for download.
This stable release ships with 15 changes affecting all editions of Checkmk,
2 changes for the Enterprise editions, 0 Cloud Edition specific and
1 Managed Services Edition specific changes.
After updating our checkmk instances and the mk_mysql plugin on the monitored server, the MySQL DB Slave mysql service is vanished:
root@misqlslave:~# cat /usr/lib/check_mk_agent/plugins/mk_mysql | grep VERSION
CMK_VERSION="2.3.0p17"
[...]
root@misqlslave:~# mysql --version
mysql Ver 15.1 Distrib 10.1.37-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2
Is this intended?
IMHO it was useful to see the seconds behind the master in checkmk…
The reason is that in our mysql version SHOW REPLICA STATUS\G; is not possible:
MariaDB [(none)]> SHOW REPLICA STATUS\G;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'REPLICA STATUS' at line 1
ERROR: No query specified
while SHOW SLAVE STATUS\G; works fine:
MariaDB [(none)]> SHOW SLAVE STATUS\G;
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: misqlmaster.misoft.lan
Master_User: replication
Master_Port: 3306
Connect_Retry: 60
[...]
We are “forced” to use a old mariadb version (10.1.37) right now, because many indices are not updated by our devs yet
Could you please ensure backwards compatibility with the mk_mysql plugin? Thanks!
Edit: This is one of three mysql slave server our campany runs. On every other server the SHOW REPLICA STATUS; command does work
When a fix for that is provided as it is one month ago?!
You also have to be sure that the agent is updated immediately because the name of the agent section changed. Would be nice to put such info into the werk because the werk says there are no interaction needed.
