Архивы Zabbix

PING3. Configuration and monitoring

I configured the PING3 remote monitoring device and wrote a zabbix template.

Zabbix: Monitoring Unread Emails

Voicemail messages were arriving in the VoiceMail subfolder of the Inbox, which operators were supposed to listen to and respond to user requests, but sometimes no one read them, so it became necessary to monitor the number of unread emails.

Zabbix: Monitoring Directory Permission Changes

Let’s say you’ve specified the rights and owner for a specific directory and want to ensure no one changes them. To do this, we’ll monitor it using Zabbix-agent.

Zabbix-server process does not terminate

Once I updated Ubuntu server and Zabbix-server by running apt update, apt upgrade, after the update was complete I agreed to restart all updated services, but Zabbix-server continued to be running for 20 minutes and did not restart.

Zabbix ERROR 1273 (HY000) at line 483: Unknown collation: ‘utf8mb4_unicode_ci’

One day I was migrating a Zabbix server database to another server and an error occurred:

Monitoring mdadm in Zabbix

I will give an example of simple monitoring of a mdadm software raid in Zabbix.

Can’t open PID file /run/zabbix/zabbix_server.pid (yet?) after start: No such file or directory

Once, on Ubuntu 18.04.6 LTS, I updated the Zabbix server to version 6.0 LTS and the new version did not start.

Monitoring Linux directory size in Zabbix

One day I needed to monitor the size of a directory in Zabbix and create a trigger so that Zabbix would notify when the directory size increases.

Zabbix: icmpping “Ping item must have target or host interface specified”

Once I upgraded Zabbix to version 6.4 and noticed that the “Template ICMP Ping” template stopped working on new devices, it continued to work on old ones, but if you add a new device, a warning was displayed:

Zabbix. Upgrading the database to primary keys

Starting with Zabbix 6.0, primary keys are used for all tables in new installations, but since I upgraded Zabbix server to version 6.4, I had to manually update the tables after the upgrade.

Before updating, first of all, open the menu “Report” – “System Information” and make sure that the keys are not used, this will be indicated by the entry – “Database history tables use primary key – No”, if the keys are used, then this entry simply will not be.