since few days, my zabbix-server decided to… take a nap.
After bashing some Windows Mobile devices, i took a coffee trying to understand what the funk was going on.
I were able to login to the interface, but the process was not started, as stated by the dashboard.
systemctl start zabbix-server did not ignite the whole gears, rebooting the system did not change a thing. So… runt through the log.
systemd is not capable to find the pid to babysit, therefore a tail /var/log/zabbix/zabbix_server.log led me to the issue…
My solution is “stupid” and working, but i would like to summon @mrmarkuz which is the maintainer of the package and @Andy_Wismer as the resident Zabbix-guru of the forum.
cp /etc/zabbix/zabbix_server.conf /etc/zabbix/zabbix_server_bck.conf
for create a copy of the config file, than i changed the section of /etc/zabbix/zabbix_server.conf
### Option: CacheSize
# Size of configuration cache, in bytes.
# Shared memory size for storing host, item and trigger data.
# Mandatory: no
# Range: 128K-8G
at the bottom
@mrmarkuz the change to the config file I suppose won’t survive to any signal-event related to zabbix_server, correct?
@Andy_Wismer for what i can understand, there was no defined cache size for the system. 128 is quite arbitrary and 16 times the default size. The installation is a VM with 4gb of ram hosting guacamole (still not used), zabbix and backup of the system… swap seem not used. I’m open for suggestions about a “reasonable” cache size, hint that could be helpful for other zabbix wannabe-admins better than me.