Ad Widget

Collapse

Graphs Problem

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • osde
    Junior Member
    • Feb 2005
    • 3

    #1

    Graphs Problem

    Hi, I have a problem with graphs, we use ZABBIX 1.1 alpha5 and all work fine, but the graphs repently start to show like this:



    ...any idea ????
  • cooper
    Senior Member
    • Sep 2004
    • 110

    #2
    Originally posted by osde
    Hi, I have a problem with graphs, we use ZABBIX 1.1 alpha5 and all work fine, but the graphs repently start to show like this:

    ...any idea ????
    Check this thread

    cooper

    Comment

    • osde
      Junior Member
      • Feb 2005
      • 3

      #3
      Zabbix doesn't draw lines if timestamp difference between points is more than 4*refresh period. Alexei...
      Ok, thank you cooper, but it is happend with more than 30 graphs, the cuestion is... why it is happened?


      this is the status of my server:

      -----------------------------------------
      STATUS OF ZABBIX
      Parameter Value
      ZABBIX server is running Yes
      Number of values stored 106924643
      Number of trends stored 1270409
      Number of alarms 93128
      Number of alerts 6439
      Number of triggers (enabled/disabled) 1200(1119/81)
      Number of items (active/trapper/not active/not supported) 2452(2355/0/15/82)
      Number of users 15
      Number of hosts (monitored/not monitored/templates) 319(219/100/0)
      -----------------------------------------

      thank in advance

      Comment

      • cooper
        Senior Member
        • Sep 2004
        • 110

        #4
        What does your zabbix_server.log say? I notice that your CPU% is around 50%+. I know that zabbix_server will only wait 3 sec (by default) for agent(d) to respond. zabbix_server might be timing out waiting for this server to respond when its load spikes? server.log file should give us some insight into that. Can you post a bit of it? You could try increasing the Timeout parameter in your agentd.conf file. You could try increasing the Timeout parameter in your agentd.conf file.

        cooper.

        Comment

        Working...