On retrying the upgrade today, planning to upgrade Zabbix with -D snapshot,
I found you brought 5.0.5 into -stable. The upgrade went smooth as silk,
thanks!
Sorry, you are right! Combing through my logs I just found that I was, in
fact, running 5.0.3 instead of 5.0.5 . I'll separately try both installing
zabbix from ports and pointing zabbix to the old fping. Sorry for the mess!
On Fri, Nov 20, 2020 at 6:48 PM Stuart Henderson
wrote:
> On 2020/11/
On 2020/11/20 17:30, Federico Churca-Torrusio wrote:
> >Simplest fix is probably to update zabbix to the version in -current,
> >ports diff for this below.
> >
> >The actual commit fixing it is in
> >
> https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/8cf3bbc393db3e48ac2401e50d1d880f53e8b75
>Simplest fix is probably to update zabbix to the version in -current,
>ports diff for this below.
>
>The actual commit fixing it is in
>
https://git.zabbix.com/projects/ZBX/repos/zabbix/commits/8cf3bbc393db3e48ac2401e50d1d880f53e8b758#src/libs/zbxicmpping/icmpping.c
I thought of that, but I don't
On 2020/11/20 16:38, Federico Churca-Torrusio wrote:
> Hello
>
> On upgrading, my Zabbix server started to wrongly report every host as up.
> According to other info I've found, it's very similar to Zabbix issue
> ZBX-18365 [1] , where Zabbix misinterprets fping's output as of fping 5.0 ,
> but it
Hello
On upgrading, my Zabbix server started to wrongly report every host as up.
According to other info I've found, it's very similar to Zabbix issue
ZBX-18365 [1] , where Zabbix misinterprets fping's output as of fping 5.0 ,
but it should have been fixed as of Zabbix 5.0.5 . This particular
inst
