code is law, a developer takes sometimes a direction
zabbix-agent2 is required but disabled by default so there should be no issue with updating.
It’s easier to install both agents than to separate them and manage two rpms and this way it’s easy to migrate from agent to agent2.
Zabbix 5.0.12 released. And installed. With the usual yum update
command. No reboot yet. Seems working.
Cheers.
15 months laters… 5.0.27 release. Don’t forget the usual signal-event nethserver-zabbix-update
after package install.
6 months laters… 5.0.30 install. Don’t forget the usual signal-event nethserver-zabbix-update
after package install.
(yeah, copypasted, lazy thursday)
Amost 9 months laters… 5.0.37 install. Don’t forget the usual signal-event nethserver-zabbix-update
after package install.
(totally copypasted, lazy saturday)
I’m quite boring here. New stuff
zabbix-server-pgsql-5.0.41-1.el7.x86_64
zabbix-agent2-5.0.41-1.el7.x86_64
zabbix-web-5.0.41-1.el7.noarch
zabbix-agent-5.0.41-1.el7.x86_64
don’t forget to trigger the signal-event command you find into upper post.