There is an issue with the agent in 4.2.3, can you update zabbix to 4.2.4 or later. The issue is described here https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/378846-zabbix-and-semaphore-use
With 4.2.3 it was changing /var to read only when cron.daily ran. Had no idea what was going on as no logs were getting written. Happened two days in a row right after a clean install of 4.2.3. So I simply downloaded 4.2.5 from the zabbix website and manually configured and installed not using portage and or overly. The normal zabbix configuration installs everything in /usr/local/. It does not interfere with the portage installation of zabbix. Then simply change the /etc/init.d/zabbix-server and zabbix-agentd to point to the binary install location /usr/local/sbin. Installing 4.2.3 via portage will get all the dependencies installed.Then install Zabbix 4.2.5 from tarball and leave zabbix installed via portage alone, or uninstall via portage then reinstall all the dependencies it pulled in if you do not want the portage version installed. I have been running 4.2.5 for a number of days now with 16 host's, 7 web checks with auto discovery turned on for the local network. Everything seems to be working as they should be. Have had no problems what so ever. 3 days now, everything running in the morning, no more /var changed to read only. I am getting ready to add more hosts as it appears to be stable. It may be safe to say 4.2.5 is stable. It is a shame that the maintainer's are so far behind. There is no reason other than time that Zabbix should not be bumped to 4.2.5 and get rid of having to unmask everything after 2.2.16-r1. Unfortunately same issue with many packages, not enough maintainers to keep up with new releases. I am increasingly starting to make my own overlays and or installing manually. Due to so many packages not being maintained and updated with current releases. Release notes state 7 Dec 2016 for Zabbix 2.2.16. A year and a half is an eternity, Zabbix should have been updated to the current 4.2.5 release notes dated 29 Jul 2019 some time ago. Considering all the known bugs that have been taken care of. The maintainers should be able to simply bump the version and it should work. It has been working fine for me, no errors no issues what so ever.
Issue was fixed over a month ago in 4.2.4. We need ebuild bump. Current version is 4.2.6.
https://www.zabbix.com/forum/zabbix-troubleshooting-and-problems/378846-zabbix-and-semaphore-use
Created attachment 588692 [details] ebuild Ebuild for 4.2.3 seems to work fine with 4.2.6. Also semaphore bug is gone. Please add this to portage tree.
I am also affected by this and would appreciate an ebuild bump.
4.2.3 got removed with https://github.com/gentoo/gentoo/commit/b57e63a1f026822b8969b965ed6db975b3df8542 This bug can probably be closed.
