Linux – Page 2 – Null Byte

Upgrading to Zabbix 7.0 from 6.x, GPG keys are not correct

By Antti Hurme 04/06/2024 No Comments 1 Min Read

If you update the repository configuration in rhel/rocky/alma/centos in /etc/yum.repos.d/zabbix.repo like previously, then you will get the error message below; “The GPG keys listed for the “Zabbix Official Repository – x86_64″ repository are already installed but they are not correct for this package.” To fix the issue, you will need to install the new Zabbix 7.0 release rpm found in https://repo.zabbix.com, for example zabbix-release-7.0-2.el9.noarch.rpm located in Zabbix Official Repository.

Excluding Zabbix from EPEL repo in RHEL/ROCKY/ALMA Linux

By Antti Hurme 03/03/2024 No Comments 2 Min Read

Now that Zabbix is a part of the EPEL repo, you might need to exclude it from the DNF configuration, if your using the official Zabbix repository. The error will be something similar to the following: Edit the repository config: /etc/yum.repos.d/epel.repo, and add an exclude in the [epel] repository configuration: run “dnf clean all” and “dnf update” again to check if the problem is solved. Excluding Zabbix when Updating Use…

Free Portainer Business at home – Using docker with more features in homelab!

Homelab Linux VMware

By Antti Hurme 12/03/2023 2 Comments 2 Min Read

I’ve started using docker as probably a lot of you, with just a Debian or Ubuntu server with the necessary binaries to get containers running. At one point, I discovered Portainer which made container management in a homelab environment a lot easier. I though about using Kubernetes, Rancher and other options like Tanzu. But they are all quite high maintenance to run a few containers at your home. If your…

[Z3005] Zabbix PostgreSQL database upgrade failed

Zabbix

By Antti Hurme 07/03/2023 No Comments 1 Min Read

When upgrading your Zabbix Database, you might encounter the following error “[Z3005] query failed: [0] PGRES_FATAL_ERROR:ERROR: permission denied for schema public”. The zabbix user you’ve created doesn’t normally need access to the database schema to work, so this would only be relevant when upgrading the zabbix version, for example between 6.2.x to 6.4.0. To fix the error, you need to give the zabbix database user access to modify the public…