Hello together,
we have an Zabbix 2.0.3 which is running on an OpenSuse 11.4 and 25 Zabbix proxies (2.0.1). The mysql database has a size of 55 GB.
I tried to upgrade to 2.0.6 and 2.0.7 and after around one hour we have a big problem with the Zabbix server and I don't know what is going wrong.
We are getting many of the following log entries in the server:
I have tested to convert the ids table to MyISAM engine, but it did not help.
When this error appears, the Zabbix server is unusable and had a heavy load (and sents around 5000 false positive alert emails). Only a reboot of this server helps. I have rolled back to the old Zabbix version 2.0.3 and now it is working.
Here are some additional informations about the infrastructure. All proxies and the server are in an virtual environment. The Zabbix server it self, has 8GB RAM.
Maybe we have a problem in a config of the server or mysql. Or is the old version of the proxies a problem (never server and old proxy version mix)? Has anyone an idea to analyse the issue?
Regards,
Jörg
we have an Zabbix 2.0.3 which is running on an OpenSuse 11.4 and 25 Zabbix proxies (2.0.1). The mysql database has a size of 55 GB.
I tried to upgrade to 2.0.6 and 2.0.7 and after around one hour we have a big problem with the Zabbix server and I don't know what is going wrong.
We are getting many of the following log entries in the server:
zabbix_server [6982]: ERROR [file:db.c,line:1500] Something impossible has just happened.
6949:20130807:120314.931 [Z3005] query failed: [1205] Lock wait timeout exceeded; try restarting transaction [update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='eventid']
zabbix_server [6984]: ERROR [file:db.c,line:1500] Something impossible has just happened.
6870:20130807:120334.103 [Z3005] query failed: [1205] Lock wait timeout exceeded; try restarting transaction [update autoreg_host set listen_ip='[REMOVED]',listen_dns='',listen_port=10050 where autoreg_hostid=51]
6866:20130807:120334.103 [Z3005] query failed: [1205] Lock wait timeout exceeded; try restarting transaction [update autoreg_host set listen_ip='[REMOVED]',listen_dns='',listen_port=10050 where autoreg_hostid=51]
6949:20130807:120314.931 [Z3005] query failed: [1205] Lock wait timeout exceeded; try restarting transaction [update ids set nextid=nextid+1 where nodeid=0 and table_name='events' and field_name='eventid']
zabbix_server [6984]: ERROR [file:db.c,line:1500] Something impossible has just happened.
6870:20130807:120334.103 [Z3005] query failed: [1205] Lock wait timeout exceeded; try restarting transaction [update autoreg_host set listen_ip='[REMOVED]',listen_dns='',listen_port=10050 where autoreg_hostid=51]
6866:20130807:120334.103 [Z3005] query failed: [1205] Lock wait timeout exceeded; try restarting transaction [update autoreg_host set listen_ip='[REMOVED]',listen_dns='',listen_port=10050 where autoreg_hostid=51]
When this error appears, the Zabbix server is unusable and had a heavy load (and sents around 5000 false positive alert emails). Only a reboot of this server helps. I have rolled back to the old Zabbix version 2.0.3 and now it is working.
Here are some additional informations about the infrastructure. All proxies and the server are in an virtual environment. The Zabbix server it self, has 8GB RAM.
Number of hosts (monitored/not monitored/templates) 973 871 / 34 / 68
Number of items (monitored/disabled/not supported) 26718 15817 / 10870 / 31
Number of triggers (enabled/disabled)[problem/unknown/ok] 10209 8732 / 1477 [106 / 0 / 8626]
Required server performance, new values per second 194.8 -
Number of items (monitored/disabled/not supported) 26718 15817 / 10870 / 31
Number of triggers (enabled/disabled)[problem/unknown/ok] 10209 8732 / 1477 [106 / 0 / 8626]
Required server performance, new values per second 194.8 -
Regards,
Jörg