I am not sure if this is the right place but here goes.
I have setup a fresh Zabbix 3.4.3 on a CentOS 7.4 64bit, with PHP 5.6.31, MySQL 5.7.2. I use the yum repository. Did nto have any issues with this and the Zabbix Server started up, again no issues.
I imported my host and templates so I now have 420 host, 41832 item and 4630 triggers. I then edited the zabbix_server.conf to give it the processes and cache that I thought was in the range that should work. restarted the server and repeated a coupe time to tune it in. All looked good and soon was down to 8 triggers showing up. Then after a bout 20 mins it jumped up to 420 triggers. All services were still running and the database was still available. Did a zabbix_server restart and it dropped back to 8 triggers after 5 mins.
This keep happening each time I would make a small change in the zabbix_server.conf.
I turned on the MySQL logging and found this error:
Aborted connection 11861 to db: 'zabbix' user: 'zabbix' host: 'localhost' (Got an error reading communication packets)
I run down this rabbit hole and made all kinds of adjustments to the MySQL. But have not really improved the system much.
In the server graphs after restart I see values, as the system runs they slowly start dropping out one by one after about 20 mins and by 30 mins there are no new updates.
Anyone have an idea where to go on this.
I have several 3.2.x systems running with about the same load with no issues.
I have setup a fresh Zabbix 3.4.3 on a CentOS 7.4 64bit, with PHP 5.6.31, MySQL 5.7.2. I use the yum repository. Did nto have any issues with this and the Zabbix Server started up, again no issues.
I imported my host and templates so I now have 420 host, 41832 item and 4630 triggers. I then edited the zabbix_server.conf to give it the processes and cache that I thought was in the range that should work. restarted the server and repeated a coupe time to tune it in. All looked good and soon was down to 8 triggers showing up. Then after a bout 20 mins it jumped up to 420 triggers. All services were still running and the database was still available. Did a zabbix_server restart and it dropped back to 8 triggers after 5 mins.
This keep happening each time I would make a small change in the zabbix_server.conf.
I turned on the MySQL logging and found this error:
Aborted connection 11861 to db: 'zabbix' user: 'zabbix' host: 'localhost' (Got an error reading communication packets)
I run down this rabbit hole and made all kinds of adjustments to the MySQL. But have not really improved the system much.
In the server graphs after restart I see values, as the system runs they slowly start dropping out one by one after about 20 mins and by 30 mins there are no new updates.
Anyone have an idea where to go on this.
I have several 3.2.x systems running with about the same load with no issues.


After much database tuning and hair pulling it turned out to be a faulty cable in the datacenter.
Comment