We are running our monitoring solution zabbix on an arch linux system.
Arch linux tends to be "up to date" since it philosophie is "patch current code base, not legacy".
I've updated the monitoring system and with that, the php version jumped from 7.4.x to 8.0.x.
After that, a lot of "widgets" (boxes) in the zabbix frontend displayed me a lot of the following error.
I've researched it and found that the error exists in the DB.php class.
I've opened the issue Ticket ZBX-18984 and created the pull request 39 on the github source code.
Hopefully, this fix will make it quickly into the code. I've added a git patch file to the issue. You can download and apply it on your system.
I wanted to quickly develop something. I thought this is the perfect timing to migrate mentally from the insecure and almost dead docker to the alive and secure podman.
I went to the page of thecodingmachine and tried it with the following one-liner:
podman run -p 80:80 --rm --name php-bazzline -v "$PWD":/var/www/html thecodingmachine/php:7.4-v3-apache
Sadly nothing is working so I've created a feature request asking for podman support.
I am using the zfs-snap-manager for such a long time that I never ever had a look on it since years.
I've just created zfs pools and zfs snap manager configurations without thinking or checking it for a while now.
But once upon a time I wanted to check the behaviour and found out that some configured snapshots where not made.
After a while I saw that my assumption was false, so the error was in front of the display :-).
My configuration for the section schema was simplified to 7d because all I wanted for a dataset was that I can go back the last seven days.
After finding the log file (/var/log/zfs-snap-manager.log) and tailing it, I quickly saw the log message Got invalid schema for dataset .... Just a bit more investigation and I found out that I have to provide a fully defined schema like 7d0w0m0y.
After adapting all available configuration files on all hosts, the zfs-snap-manager is working as expected.
I found an existing feature request to "relaxed" the schema interpretion and stumpled over another feature request asking for creating unittests. So I've forked it and will try to learn python by fixing the issue on my own.
migrate code to python3
write unittests
implement relaxed handling of schema with default values