Good afternoon!
So I tried to look for similar issues throughout the forum but it seemed as though most folks had an issue with the CacheSize settings in the zabbix_server.conf file. I don't see that issue in the logs, but maybe I'm wrong. Here's the backstory....
We just upgraded (two weeks ago) from 3.4 to 4.2. We are using MySQL/MariaDB on a seperate vm for the database. Everything has been working great until today. We started having several issues this morning. The first was a database connection issue.
ERROR 1129 (HY000): Host ‘XXX.XXX.XXX.XXX’ is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’
We fixed this issue by running the msqladmin -u root -p flush-hosts. We also increased the number of max_connections in the my.cnf config file. That seemed to fix that issue, but then we started getting the banner in the zabbix frontend:
The Zabbix Server is not running; the information displayed might not be current.
We pulled the zabbix_server.log and it looks like it's crashing after it's loads the workers.
80655:20190826:152735.015 server #216 started [preprocessing worker #3]
80653:20190826:152735.016 server #214 started [preprocessing worker #1]
80654:20190826:152735.017 server #215 started [preprocessing worker #2]
80486:20190826:152735.639 Got signal [signal:11(SIGSEGV),reason:1,refaddr
nil)]. Crashing ...
There doesn't seem to be any warning prior to the crash. Also it's not in the same place every time. The Zabbix server tries to come online and it continues to crash. Here's another exerpt:
80925:20190826:152753.035 server #214 started [preprocessing worker #1]
80926:20190826:152753.036 server #215 started [preprocessing worker #2]
80927:20190826:152753.037 server #216 started [preprocessing worker #3]
80757:20190826:152755.601 Got signal [signal:11(SIGSEGV),reason:1,refaddr
nil)]. Crashing ...
So I tried to look for similar issues throughout the forum but it seemed as though most folks had an issue with the CacheSize settings in the zabbix_server.conf file. I don't see that issue in the logs, but maybe I'm wrong. Here's the backstory....
We just upgraded (two weeks ago) from 3.4 to 4.2. We are using MySQL/MariaDB on a seperate vm for the database. Everything has been working great until today. We started having several issues this morning. The first was a database connection issue.
ERROR 1129 (HY000): Host ‘XXX.XXX.XXX.XXX’ is blocked because of many connection errors; unblock with ‘mysqladmin flush-hosts’
We fixed this issue by running the msqladmin -u root -p flush-hosts. We also increased the number of max_connections in the my.cnf config file. That seemed to fix that issue, but then we started getting the banner in the zabbix frontend:
The Zabbix Server is not running; the information displayed might not be current.
We pulled the zabbix_server.log and it looks like it's crashing after it's loads the workers.
80655:20190826:152735.015 server #216 started [preprocessing worker #3]
80653:20190826:152735.016 server #214 started [preprocessing worker #1]
80654:20190826:152735.017 server #215 started [preprocessing worker #2]
80486:20190826:152735.639 Got signal [signal:11(SIGSEGV),reason:1,refaddr
nil)]. Crashing ...There doesn't seem to be any warning prior to the crash. Also it's not in the same place every time. The Zabbix server tries to come online and it continues to crash. Here's another exerpt:
80925:20190826:152753.035 server #214 started [preprocessing worker #1]
80926:20190826:152753.036 server #215 started [preprocessing worker #2]
80927:20190826:152753.037 server #216 started [preprocessing worker #3]
80757:20190826:152755.601 Got signal [signal:11(SIGSEGV),reason:1,refaddr
nil)]. Crashing ...
Comment