Debian 7 (wheezy), with previous version 2.4. Made the backup to current files, downloaded the new repository and upgraded. Only had to put the password to the zabbix_server.conf and start the service again.
Database upgraded fine.
I'm using snmp to read our firewall's incoming/outgoing packets to show internet bandwidth use, and now the graphs keep having chunks of missing data.
Reading the log, it says:
3150:20160304:104358.887 temporarily disabling SNMP agent checks on host "WatchGuard Firewall Mcbo": host unavailable
The host isn't unavailable. I can ping it just fine. I can browse to its internal website. I can even use snmpwalk to read values just fine.
I am using ifInOctets/ ifOutOctets once per minute to read values.
Is there something i need to fine tune to make zabbix reliable again? I remember tweaking CacheSize from 8MB to 32 MB, i just did that again.
For reference, here are my zabbix stats:
Number of hosts (enabled/disabled/templates) 136 89 / 1 / 46
Number of items (enabled/disabled/not supported) 9298 9119 / 19 / 160
Number of triggers (enabled/disabled [problem/ok]) 543 486 / 57 [4 / 482]
Number of users (online) 9 2
Required server performance, new values per second 118.38
Using mysql, hardware is core 2 duo with 4GB RAM.
I should also mention that on 2.4, when the power goes out (frequent in my country) sometimes i had the same behavior, and had to restart the service multiple times and sometimes just leave it running for hours until it stabilized, but the situation seems worse on 3.0
Any tips?
Database upgraded fine.
I'm using snmp to read our firewall's incoming/outgoing packets to show internet bandwidth use, and now the graphs keep having chunks of missing data.
Reading the log, it says:
3150:20160304:104358.887 temporarily disabling SNMP agent checks on host "WatchGuard Firewall Mcbo": host unavailable
The host isn't unavailable. I can ping it just fine. I can browse to its internal website. I can even use snmpwalk to read values just fine.
I am using ifInOctets/ ifOutOctets once per minute to read values.
Is there something i need to fine tune to make zabbix reliable again? I remember tweaking CacheSize from 8MB to 32 MB, i just did that again.
For reference, here are my zabbix stats:
Number of hosts (enabled/disabled/templates) 136 89 / 1 / 46
Number of items (enabled/disabled/not supported) 9298 9119 / 19 / 160
Number of triggers (enabled/disabled [problem/ok]) 543 486 / 57 [4 / 482]
Number of users (online) 9 2
Required server performance, new values per second 118.38
Using mysql, hardware is core 2 duo with 4GB RAM.
I should also mention that on 2.4, when the power goes out (frequent in my country) sometimes i had the same behavior, and had to restart the service multiple times and sometimes just leave it running for hours until it stabilized, but the situation seems worse on 3.0
Any tips?