Hi there,
I'm running Zabbix 4.0 on a bunch of Centos 7 servers and last night there was an update to 4.0.17. When that happened it removed the following file which obviously broke monitoring for Mysql.
/etc/zabbix/zabbix_agentd.d/userparameter_mysql.conf
It's an easy fix. All I had to do was copy the sample file back to that location and restart the zabbix agent on all of the servers. That seems unusual because I've gone through many updates and never seen that problem before.
Should I be putting that file in a different place so that it doesn't get removed from future updates or was this just a bug?
Thanks!
I'm running Zabbix 4.0 on a bunch of Centos 7 servers and last night there was an update to 4.0.17. When that happened it removed the following file which obviously broke monitoring for Mysql.
/etc/zabbix/zabbix_agentd.d/userparameter_mysql.conf
It's an easy fix. All I had to do was copy the sample file back to that location and restart the zabbix agent on all of the servers. That seems unusual because I've gone through many updates and never seen that problem before.
Should I be putting that file in a different place so that it doesn't get removed from future updates or was this just a bug?
Thanks!
Comment