[SOLVED] Re: net/zabbix-5.0.5 : Zabbix wrongly reporting down hosts as up
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!
Re: net/zabbix-5.0.5 : Zabbix wrongly reporting down hosts as up
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/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/8cf3bbc393db3e48ac2401e50d1d880f53e8b758#src/libs/zbxicmpping/icmpping.c > > > > I thought of that, but I don't think it would work. According to > > Zabbix's Jira [1] , that particular commit was already merged into Zabbix > > 5.0.5 . Most curious. > > > > [1]: https://support.zabbix.com/browse/ZBX-18365 > > You said you were running OpenBSD 6.8 which comes with 5.0.3 >
Re: net/zabbix-5.0.5 : Zabbix wrongly reporting down hosts as up
>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 think it would work. According to Zabbix's Jira [1] , that particular commit was already merged into Zabbix 5.0.5 . Most curious. [1]: https://support.zabbix.com/browse/ZBX-18365
net/zabbix-5.0.5 : Zabbix wrongly reporting down hosts as up
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 installation has OpenBSD -release on an amd64 virtual machine with syspatches, with Zabbix and fping from pkg_add . A workaround mentioned for other OS's was to downgrade fping 5 to fping 4 , but I haven't tried that yet; so far, I have rolled back to 6.7 . Is this issue reported elsewhere for OpenBSD? How could I pin fping so it doesn't upgrade on pkg_add -u ? Would it be "canon" to graft in an old /usr/local/sbin/fping ? Old versions: * OpenBSD 6.7 * Zabbix 4.0.19 from pkg_add * fping 4.2 from pkg_add New versions: * OpenBSD 6.8 * Zabbix 5.0.5 from pkg_add * fping 5.0 from pkg_add [1]: https://support.zabbix.com/browse/ZBX-18365 Thanks Federico Churca-Torrusio
