Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-4728

Availability report don't work

XMLWordPrintable

    • Icon: Incident report Incident report
    • Resolution: Fixed
    • Icon: Critical Critical
    • 2.0.0
    • 1.8.10
    • Frontend (F)
    • I have tried 3 servers:
      S1&S2 2xXeon @2.8Ghz, 8GB RAM, RAID10, Mysql+InnoDB
      S3 Intel Core 3 Quad 8300 @2.5Ghz, 4GB RAM, RAID10, Mysql+InnoDB

      I can't run Availability report (next AVR) on any server. When I click on AVR I see waiting for server. Tried many browsers (IE8, FF, Chrome) and Windows XP , Debian, Ubuntu as desktop client.
      I have tried production server S1, I see time exceeded in apache log with php5 max_execution_time = 300. With max_execution_time = 600 I don't see anything in log.
      So i did mysqldump --single-transaction --master-data zabbix > zabbix.sql and uploaded this database to S2 and S3 with mysql zabbix < zabbix.sql
      On any server AVR don't work. Results are equal. Only what I see is "waiting for server"

      I had problems with AVR from beginning (year 2010) when I switched from Nagios to Zabbix 1.8.x . They don't work or they was slow. But I had one version where AVR works (can't remember which version). I upgraded zabbix only with stable releases to current stable 1.8.10.

      My zabbix configuration :

      REPORT
      Parameter Value Details
      Zabbix server is running No localhost:10051
      Number of hosts (monitored/not monitored/templates) 1479 1422 / 4 / 53
      Number of items (monitored/disabled/not supported) 6806 6308 / 262 / 236
      Number of triggers (enabled/disabled)[problem/unknown/ok] 3705 3701 / 4 [25 / 252 / 3424]
      Number of users (online) 6 2
      Required server performance, new values per second 134.36 -

            Unassigned Unassigned
            coudy Coudy
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: