-
Type:
Incident report
-
Resolution: Fixed
-
Priority:
Critical
-
Affects Version/s: 2.2.2
-
Component/s: Server (S)
-
Environment:Ubuntu 12.04 LTS, mysql 5.5.35 (package), zabbix server 2.2.2.
On Dell R420 server (32 Gb RAM, 2 x CPU Intel(R) Xeon(R) CPU E5-2440 0 @ 2.40GHz y 4 x 600Gb SAS)
Aprox. 650 hosts and 60000 items (~92 items/host) and 56000 trigggers (~85 trigger/host).
We store 30 history and 365 days trend, and a lot of items are checked every 120s and others every 300s.Ubuntu 12.04 LTS, mysql 5.5.35 (package), zabbix server 2.2.2. On Dell R420 server (32 Gb RAM, 2 x CPU Intel(R) Xeon(R) CPU E5-2440 0 @ 2.40GHz y 4 x 600Gb SAS) Aprox. 650 hosts and 60000 items (~92 items/host) and 56000 trigggers (~85 trigger/host). We store 30 history and 365 days trend, and a lot of items are checked every 120s and others every 300s.
Sometimes zabbix server stop working and get some crash information on log file.
Sometimes we got zabbix server daemon are up but it is not responding anymore.
