[ZBX-4728] Availability report don't work Created: 2012 Mar 04  Updated: 2017 May 30  Resolved: 2012 Mar 11

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Frontend (F)
Affects Version/s: 1.8.10
Fix Version/s: 2.0.0

Type: Incident report Priority: Critical
Reporter: Coudy Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: availability, performance, reports
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

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

Issue Links:
Duplicate
duplicates ZBX-4729 can't patch 1.8.10 DB to 1.9.9 Closed

 Description   

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 -

 Comments   
Comment by Coudy [ 2012 Mar 04 ]

I don't know how to edit my issue, so I'm attaching this info to comment

I have tried 3 servers:
S1&S2 2xXeon @2.8Ghz, 8GB RAM, RAID10, Mysql+InnoDB
(Debian Stable 64bit, Mysql server 5.1.49-3, Apache2 2.2.16-6+squeeze6, PHP5 5.3.3-7+squeeze8)

S3 Intel Core 2 Quad 8300 @2.5Ghz, 4GB RAM, RAID10, Mysql+InnoDB
(Debian Testing 64bit, Mysql server 5.1.58-1, Apache2 2.2.22-1, PHP5 5.3.10-2)

Comment by richlv [ 2012 Mar 05 ]

might be a duplicate of ZBX-3157

Comment by Coudy [ 2012 Mar 08 ]

I was able to self repair my db, patch it to 2.0 and upgrade zabbix to 1.9.9 beta.
I can confirm, that Availability reports are now working much much faster as in 1.8.10. Report for 1 year for 212 hosts took several seconds.
I'm writing my howto, when it will be available, I'll post link here.

Comment by richlv [ 2012 Mar 11 ]

ok, so it was a performance issue, which is somewhat resolved in trunk.
setting "fix version" to 2.0.0 to indicate first stable version which will have this improvement

Comment by Coudy [ 2012 Mar 14 ]

The best solution is to upgrade to 2.0, but if it isn't possible I have workaround.
If you have to many hosts, you can split it wit this steps. Creating reports for only 1 group need less time, and server can process it without exceeded lmit.

1. Create new user group for each host group (for examples dsl_reports for dsl lines, server_reports for servers, etc..). Assign only host/templates from current host group to this user group
2. Create new user for each "report" group.
3. Loggin to Zabbix with new "report" user, and you can run availability reports.

Generated at Mon May 12 07:33:08 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.