Ad Widget

Collapse

the same error fires on all monitored hosts at the same time

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • kwd2
    Junior Member
    • Sep 2017
    • 6

    #1

    the same error fires on all monitored hosts at the same time

    Hi all,
    I am seeing errors generated by zabbix where the error is reported on all monitored hosts at nearly the same time. I've seen this with several different triggers too. The error shown below is the same on every node at roughly the same time +- 60 seconds
    Anyone know what causes this? how to fix?
    thanks
    Ken
    Attached Files
  • kaspars.mednis
    Senior Member
    Zabbix Certified Trainer
    Zabbix Certified SpecialistZabbix Certified Professional
    • Oct 2017
    • 349

    #2
    Hello !

    This error may come from zabbix server, but its strange that it happens on every server...
    Have you checked the caches graph on zabbix server internal monitoring graphs ? Some caches may be full.
    than it's time to increase CacheSize.



    zabbix server restart needed after config change

    Regards,
    Kaspars

    Comment

    • kwd2
      Junior Member
      • Sep 2017
      • 6

      #3
      Hi,
      thanks for the suggestion. The server's cache was below 25% free so that appears to have fired the trigger.
      I think the problem is in provisioning. This zabbix server is monitoring many cloud nodes, each of which has its own zabbix server. The centralized server was provisioned by importing the templates and hosts from each existing zabbix server on each node. So I'm guessing the individual node triggers are tied to the central servers data and that causes them all to fire
      thansk
      Ken

      Edit, yes this was the problem. The central server is essentially a copy of each node's zabbix server, where each node is stored as a host_group and each host_froup had the Zabbix server template in it, so all the host groups were triggering off of the zabbix servers data
      Last edited by kwd2; 09-11-2017, 23:03.

      Comment

      Working...