I'm currently having an issue with Zabbix and I don't know how to fix this other than causing mass loss of data.
In the last few days I've noticed whenever a host of mine had two or more interfaces and the primary interface went down, Zabbix wouldn't recognize the other interface I've selected as the primary. For example, I have a SonicWALL host with three interfaces, which I'll name it A,B and C.
Interface A is the primary interface and for an unknown reason it went down so I checked if the other interfaces were working properly and, fortunatelly, both B and C were working just fine so I could switch and move on to understand what happened with interface A.
I switched my SonicWALL host's interface from A to B, clicked on "update" but Zabbix is still issuing a message informing it cannot connect to "A".
I've tried to restart my Zabbix server and disable & enable my host but with no sucess in both attempts.
Checked my server log (/var/log/zabbix/zabbix_server.log) and the only information I could find, until the time of this writing, that was related to this issue was:
The only solution I found until now, which is quite a terrible idea, was to do a full clone, delete the host and recreate it back to our server. The tool would recognize the new host using the interface I checked is working properly but I'd lose all my data.
Any tips on how I could deal with this?
Currently using Zabbix 3.4 in a Centos 7.
Edit: I increased my debug level in my server's config file and I got this other three log lines:
In the last few days I've noticed whenever a host of mine had two or more interfaces and the primary interface went down, Zabbix wouldn't recognize the other interface I've selected as the primary. For example, I have a SonicWALL host with three interfaces, which I'll name it A,B and C.
Interface A is the primary interface and for an unknown reason it went down so I checked if the other interfaces were working properly and, fortunatelly, both B and C were working just fine so I could switch and move on to understand what happened with interface A.
I switched my SonicWALL host's interface from A to B, clicked on "update" but Zabbix is still issuing a message informing it cannot connect to "A".
I've tried to restart my Zabbix server and disable & enable my host but with no sucess in both attempts.
Checked my server log (/var/log/zabbix/zabbix_server.log) and the only information I could find, until the time of this writing, that was related to this issue was:
375:20181019:081445.274 temporarily disabling SNMP agent checks on host "SonicWALL01": host unavailable
Any tips on how I could deal with this?
Currently using Zabbix 3.4 in a Centos 7.
Edit: I increased my debug level in my server's config file and I got this other three log lines:
2302:20181019:084647.390 In get_values_snmp() host:'SonicWALL01' addr:'X.X.X.X' num:1
2272:20181019:084707.190 hostid:10273 host:'SonicWALL' name:'SonicWALL01' status:0
2302:20181019:084747.457 temporarily disabling SNMP agent checks on host "SonicWALL01": host unavailable
2272:20181019:084707.190 hostid:10273 host:'SonicWALL' name:'SonicWALL01' status:0
2302:20181019:084747.457 temporarily disabling SNMP agent checks on host "SonicWALL01": host unavailable