ZABBIX Forums - Zabbix Troubleshooting and Problems

Duplicate entry '632279' for key 'event_recovery.PRIMARY' Zabbix 7.4.11

Nadja — Tue, 14 Jul 2026 10:19:21 GMT

Good morning

I'm pretty new in the Zabbix-Community and with Zabbix itself. We started using it company-wide about 6 months ago, and we already startet with Version 7.x.x.

Since about one or two week ago, we startet noticing some problems that wouldn't resolve their status on their own, and they weren't closable (even though I configured it to be closable). After some investigation, we discovered that we startet getting these error messages: Duplicate entry '632279' for key 'event_recovery.PRIMARY' . After even more investigation, we discovered that there was an inconsistency between the mysql tables problem, event_recovery and events.

What seems to happen is the following: Zabbix created a recovery reference for the event 632279 . However, the actual recovery event 632279 was never created in the `events` table. We were able to check the faulty events the following mysql-command:

Code:

SELECT p.eventid,p.name
FROM problem p
JOIN event_recovery er
ON p.eventid=er.eventid
WHERE p.r_eventid IS NULL;

And delete these after verifying them:

Code:

DELETE er
FROM event_recovery er
JOIN problem p
ON p.eventid = er.eventid WHERE p.r_eventid IS NULL;

But it's still regularly occuring.

We didn't do a major release upgrade, the only upgrade that happened in the last couple of months was from 7.4.10 to 7.4.11 (since I saw some of these error mesage appearing after a major upgrade).

What we did however, was we moved the existing Zabbix-instance from the downloadable zabbix-appliance to a Ubuntu-Installation. To do that, we created a dump of the existing tables (because of the configurations, but we removed the data itself). Because the data was way too big to move.

I found another Thread in this forum stating the same problem, but after a major upgrade: https://www.zabbix.com/forum/zabbix-...covery-primary
Where he tells the user to re-create these tables and the key-constraints "An online post suggested rebuilding the events_recovery table and re-establishing the association with the primary keys in the events table. "

Can you maybe help me find the problem we currently have, and resolve it? And wether we should follow this guide above, and if we should, how would that be possible?

Some Informations:
Zabbix server version and Zabbix frontend version 7.4.11
Mysql Server: 8.0.46
Ubuntu-Server: 24.04.3

If you need any other informations, feel free to let me know, and thank you for your time. I have posted this in the wrong part of the forum before, so I try it once more.

Best regards
Nadja

Zabbix Agent Windows vfs discovery error after volume unmounted

Buaya-kun — Mon, 13 Jul 2026 07:51:50 GMT

I have issues with Zabbix Agentd and Zabbix Agent2 on vfs.discovery and vf.get items. After I unmount a removable VeraCrypt volume, Agentd/Agent2 produce error when get vfs value.

This is the result of zabbix_agent2.exe -t vfs.fs.discovery when the VeraCrypt volume mounted:

Code:

vfs.fs.discovery                              [s|[{"{#FSNAME}":"D:","{#FSTYPE}":"NTFS","{#FSLABEL}":"Kaede Data","{#FSDRIVETYPE}":"fixed"},{"{#FSNAME}":"C:","{#FSTYPE}":"NTFS","{#FSLABEL}":"Kaede Win10","{#FSDRIVETYPE}":"fixed"},{"{#FSNAME}":"W:","{#FSTYPE}":"NTFS","{#FSLABEL}":"TrueCrypt WebSites","{#FSDRIVETYPE}":"removable"},{"{#FSNAME}":"V:","{#FSTYPE}":"NTFS","{#FSLABEL}":"TrueCrypt Development","{#FSDRIVETYPE}":"removable"}]]

after I unmounted the VeraCrypt volume, it became like this:

Code:

vfs.fs.discovery                              [m|ZBX_NOTSUPPORTED] [Cannot obtain a list of filesystems. Volume: \\?\Volume{bdd4c528-aa81-11f0-84c9-f01e34112bd0}\ Error: The system cannot find the file specified.]

Tested on Zabbix Agentd and Zabbix Agent2 version 6.0.47 and 7.4.12, result are the same. OS is Windows 10 with the latest update.

Any way to fix this issues?
Thanks

Discovery problem in 7.4.12

BiMW — Fri, 10 Jul 2026 05:56:52 GMT

After upgrading from 7.4.11 to 7.4.12, the discovery rule started detecting hosts that had been previously discovered and deleted. Is anyone else experiencing this issue?

After downgrade all is normal.

Zabbix Queue backlog after radius failure

ericg — Wed, 08 Jul 2026 22:42:56 GMT

Zabbix Infrastructure
OS: Ubuntu 24.04
Zabbix: 7.4.10
Zabbix servers: 2 in HA
Zabbix Proxies: 5 in active mode, one is stand alone the other four are in proxy groups grouped in 2's
PostgreSQL: 18.3, w/timescaleDB 2.23.1
PGbouncer: 1.24.1
Compression: on after 7d

Issue experienced: Around 4am yesterday two of our Zabbix proxies stopped using their value cache and they started backlogging items. This all seems to coincide with our Radius server failing to authenticate requests during this time, the radius server has failed to auth at other times but not necessarily at this scale.
After Radius resumed working after a few moments, the two Zabbix proxies never caught up on the backlog of items you can seen in the queue of the screenshot I've included (both proxy 3 and 4 were about the same).
To resolve the backlog I Restarted the primary Zabbix server at 9:18 AM which failed over to the second Zabbix server, at this point certain metrics started recording again, but the queue stayed backlogged. At 1:12 PM I restarted both proxy 3 and 4 and that resolved their backlog of queued items.

Any suggestions for a bug this could be? or perhaps what I should see in the logs to help narrow down what the problem could be?

Service outages don't send email

cjyar — Mon, 29 Jun 2026 18:42:30 GMT

tl;dr:

Services don't send emails.
Triggers do send emails.
Services do send MS Teams notifications.

I have a Service action that sends notifications via email, but it doesn't work. No emails are received, and nothing shows up in the Zabbix server log. But that same Service action also successfully sends notifications to MS Teams, so I know the Service action is being triggered. At the same time, I have a Trigger action that sends email alerts to the same people, and those emails are successfully delivered. There's something I don't understand here; can somebody explain what I'm missing?

Here's the Service action:

And here's the Trigger action:

No SNMP connection with custom template

Colin_ — Tue, 23 Jun 2026 08:44:02 GMT

Hello everyone,

since there is no official integration for SecurePoint firewalls, I used the vendor-provided MIBs and converted them into a Zabbix template using mib2zabbix. https://github.com/zabbix-tools/mib2zabbix
I have applied the same approach to several LANCOM switches without any issues. However, with the SecurePoint template, I am encountering a different behavior:

It appears that the Zabbix proxy is not sending any SNMP requests at all.
There are no error messages in the frontend or logs.
In Data collection -> Hosts, the SNMP availability icon remains grey.

The basic setup should be correct:

SNMP is properly configured on the SecurePoint firewall.
The corresponding firewall rule allowing SNMP is in place.
The firewall and the Zabbix proxy are located in the same network (no routing involved).

When disabling and enabling the working and non-working templates, I receive the following log messages.

Code:

2105:20260623:102629.116 received configuration data from server at "192.168.XXX.XXX", datalen 62621 <-- Disabled working template
2105:20260623:102639.254 received configuration data from server at "192.168.XXX.XXX", datalen 62621 <-- Enabled working template
2156:20260623:102656.089 enabling SNMP agent checks on host "XXX.XXX.de": interface became available <-- SNMP is enabled
2105:20260623:102709.601 received configuration data from server at "192.168.XXX.XXX", datalen 37848 <-- Disabled SecurePoint template
2105:20260623:102729.848 received configuration data from server at "192.168.XXX.XXX", datalen 37848 <-- Enabled SecurePoint template
                                                                                                     <-- Nothing happens

I don't know what I should check next. Any hints or troubleshooting approaches would be appreciated.

Interesting Issue

kellym — Mon, 22 Jun 2026 17:51:56 GMT

Our Zabbix environment consists of separate database, server, and proxies. This is on updated 7 LTS. The web runs on the server. We came in this morning to "Zabbix Server is not running", then it would go away, then it would come back. We have noticed that if we disable the web, then the server itself does not crash. Pretty much as soon as we enable the web, boom, server crashes. I can provide almost any data if requested.

Preventing Service Discovery certain services - Windows

furicle — Thu, 18 Jun 2026 17:36:18 GMT

Fairly new Zabbix user - I'm sure this is a 'me-issue' - I have read similar threads in this forum but I've not figured it out yet.

Zabbix 7.4 on Alma 9 - monitoring Windows server core clients with agent2 active

There are some services I do not want to monitor - e.g. 'StateRepository' - even though they are marked as auto start up in Windows, as they generate false positive warnings.

If I delete either the item

Windows services discovery: State of service "StateRepository" (State Repository Service)

or the trigger on that item, it comes back, due to auto discovery.

What I thought was the fix, was to add a new template, populating the Macros tab like this

But that isn't over-riding the Windows by Zabbix agent active template

What's the correct fix here?
I'd rather not do it per host (haven't tried)
I'd rather not alter the built in template as I think it would get over-ridden on zabbix updates?

I don't understand that 'template macros' vs 'inherited and template macros' choice either...

Comments appreciated

after upgradin debian 12 to 13 and zabbix 7 to 7.4 an apt error appears

majed17 — Tue, 16 Jun 2026 05:57:23 GMT

Peace,
Hit:5 http://repo.zabbix.com/zabbix/7.4/release/debian trixie InRelease
Hit:6 http://repo.zabbix.com/zabbix/7.4/stable/debian trixie InRelease
All packages are up to date.
Notice: Skipping acquire of configured file 'main/binary-amd64/Packages' as repository 'http://repo.zabbix.com/zabbix/7.4/release/debian trixie InRelease' doesn't support architecture 'amd64'

how to solve?