Hi all.
I have updated my mariadb to version 10.6.7 on a host that I monitoring and am no longer able to monitor it. A few things have changed in the way that authentication is performed, and a message from mariadb breaks the template. The message is:
To rectify this, I have made the following changes:
From the command line, I am able to run the mysql.ping command as user zabbix:
However, when I run zabbix_get from the server, I get:
If I set the debug level of the zabbix agent on the host to 4 and run a zabbix_get, I see the following in the agent log:
I am using zabbix server 6.0.1 and agent 6.0.3. I am also monitoring older mariadb and mysql instances on other hosts without issues.
Any help would be appreciated.
Shaun
I have updated my mariadb to version 10.6.7 on a host that I monitoring and am no longer able to monitor it. A few things have changed in the way that authentication is performed, and a message from mariadb breaks the template. The message is:
Code:
"WARNING: Forcing protocol to TCP due to option specification. Please explicitly state intended protocol".
Code:
Add HOME=/var/lib/zabbix in template_db_mysql.conf to force user zabbix to use the .my.cnf file. Add protocol=tcp to /var/lib/zabbix/.my.cnf to eradicate the error message from mariadb 10.6.7
Code:
sudo -u zabbix mysqladmin -h"localhost" -P"3306" ping mysqld is alive
Code:
zabbix_get -s xxxx.xxxx.xxxx.xxxx -p 10050 -k mysql.ping["localhost","3306"] ZBX_NOTSUPPORTED: Unsupported item key.
Code:
18095:20220511:112508.305 Requested [mysql.ping[localhost,3306]] 18095:20220511:112508.305 Sending back [ZBX_NOTSUPPORTED: Unsupported item key.]
Any help would be appreciated.
Shaun
Comment