ZABBIX Forums - Zabbix Troubleshooting and Problems

zabbix.sock file keeps disappearing

cw_2147 — Thu, 27 Aug 2026 05:31:19 GMT

Hi,

We recently upgraded our underlying OS from Ubunut 22.04 to 24.04 and since that time the zabbix.sock file from /var/run/php keeps missing causing the system to not work. I recreate the file with the following command and the system start again but then about a week later will be missing and zabbix will stop working.

The command I run to get the system back up and running is - sudo ln -s /etc/alternatives/php-fpm.sock /var/run/php/zabbix.sock

Anyone know why the file would keep getting deleted or go missing?

Thanks

New hosts only get connection from Proxy to Server when the Proxy is restarted.

LarsB. — Tue, 18 Aug 2026 13:48:12 GMT

So, I got a problem with my Zabbix installation.
The Zabbix server (Postgres) is installed via Docker, the proxy (MySQL) also running in docker. When I create a new host in Zabbix and install the agent2 on a device, the proxy only recognizes a heartbeat from the Device but replies host not found.
For me it sounds like it doesn’t get the data from the server about the new host, but every time I change something the log on the proxy shows: received configuration data from server as if it got a new configuration.
When the proxy is restarted the host is instantly available. When Ive tested the proxy with SQLite it works without a problem. For testing I also tried connecting in active and passive mode. This didn't change anything.
I am using the latest stable release Zabbix 7.4.13.
Did someone run into something similar?

Action Overlap: Resolved event routed to wrong channel

mohammadnaghdi — Sat, 15 Aug 2026 11:31:34 GMT

I have encountered a consistent issue regarding Trigger Actions evaluation in Zabbix, specifically during the Recovery (Resolved) phase when a specifically tagged action overlaps with a broader action that covers the entire host.

Setup Details:

I have two distinct Trigger Actions configured:
1. Action A (Specific / SRE Team): Contains specific conditions and a dedicated event tag (e.g., sre_call: yes), targeting a dedicated Mattermost media type/channel assigned specifically to the SRE team.
2. Action B (Broad / Network Team): Covers the entire host (no specific tags, targeting all triggers for the host), targeting the Network team's Mattermost media type/channel.
Both Problem and Resolved operations are defined for both actions.
Troubleshooting Steps Taken: To thoroughly verify this, a separate Mattermost media type was created, and the word "TEST" was explicitly added to the Problem and Resolved message templates of the SRE action. Furthermore, this dedicated media type was registered in both the Trigger Action operations and the specific SRE User profile.

The Issue:

When a Problem occurs, Zabbix evaluates the conditions correctly. Both Action A and Action B trigger their respective notifications, and both groups receive the Problem alert successfully (with the "TEST" keyword appearing correctly in the SRE channel).
However, when the trigger state changes to Resolved, Zabbix's evaluation engine exhibits a conflict during Action Execution/Overlap. Because Action B covers the entire host without strict tags, Zabbix's evaluation engine fails to properly isolate the specific tagged action (Action A) during recovery.
As a result, the resolved event notification for Action A is hijacked/overwritten or incorrectly redirected and sent via Action B to the Network team's Mattermost channel, while the Action Log falsely indicates that the message was successfully dispatched for Action A.
If I temporarily disable Action B (the broad host-wide action), the Resolved notification successfully and correctly reaches the SRE team's Mattermost channel via Action A. This confirms that an overlap conflict in action evaluation occurs exclusively during the recovery phase when a host-wide broad action exists alongside a specifically tagged action.

Expected Behavior: Zabbix should evaluate recovery events with the exact same strict condition matching as problem events, ensuring that specific actions (like those using unique event tags and dedicated media types) independently process and send their own resolved notifications without being overridden, intercepted, or hijacked by broader host-wide actions.

Logically, any Problem messages sent to a specific channel must have their corresponding Problem Resolved messages delivered to that exact same channel.

Any insights or fixes for this behavior would be greatly appreciated.

Problem import maps from Zabbix 7.2.3 to 8.0

piton4ik — Fri, 14 Aug 2026 08:01:14 GMT

I installed the new Zabbix 8.0.0 beta 2 for testing and migrated hosts and templates, but I can't import the monitoring map.

host "ping3-100" is already exist

PHP Code:


Cannot find host "ping3-100" used in map "Ping3". [zabbix.php:17 → require_once() → ZBase->run() → ZBase->processRequest() → CController->run() → CControllerPopupImport->doAction() → CApiWrapper->__call() → CFrontendApiWrapper->callMethod() → CApiWrapper->callMethod() → CApiWrapper->callClientMethod() → CLocalApiClient->callMethod() → CConfiguration->import() → CConfiguration->importForce() → CConfigurationImport->import() → CConfigurationImport->processMaps() → CMapImporter->import() → CMapImporter->resolveMapReferences() in include/classes/import/importers/CMapImporter.php:77]

how to fix it?

Rebranding Zabbix

sbdcunha — Thu, 13 Aug 2026 08:14:57 GMT

I am using 7.4.11rc2 and its working fine
I need to brad zabbix logo and the new logo does not get replace
Earlier I had zabbix 6.4 and i was successfully rebranded the logo
did some googling and other AI tools but was not successful
Appreciate if someone can post a a link which can help me do the above

regards

simon

Simple Check for MSSQL service port not working after upgrade to 4.7.13

Christian_N — Tue, 11 Aug 2026 07:02:26 GMT

Had a strange issue yesterday. After updating both server and proxy to 7.4.13 the check for MSSQL port status on the MSSQL for Zabbix agent 2 template started to fail, but just on the hosts that was using the proxy, It's a "smple check" in the template, and if I change it to agent it works. Not a big issue, but has any one ells had the same issue?

Host cannot be found by technical host name when a visible name is configured(7.4.13)

Rudlafik — Wed, 05 Aug 2026 13:28:16 GMT

Host cannot be found by technical host name when a visible name is configured
Zabbix version: 7.4.13
Description:

When a host has a different Host name and Visible name, it cannot be found by searching for its technical host name in several parts of the Zabbix frontend.

For example:

Host name: 1234567890
Visible name: Test_host

Searching for 1234567890 does not return the host in the following locations:

Data collection → Hosts
Inventory → Hosts
Monitoring → Hosts
Monitoring → Latest data

The only place where the technical Host name appears as a searchable option is when creating or editing a graph widget on a dashboard. Steps to reproduce

Create a new host.
Set Host name to 1234567890.
Set Visible name to Test_host.
Save the host.
Open each of the following pages and search for 1234567890:
- Data collection → Hosts
- Inventory → Hosts
- Monitoring → Hosts
- Monitoring → Latest data

Actual result
The host is not found when searching by its technical host name, 1234567890. It can only be found by searching for its visible name, Test_host. Expected result

The host should be searchable by both: its technical Host name its Visible name

This should work consistently across all host-selection and host-search fields in the Zabbix frontend.

This behavior is particularly problematic in environments where the technical host name contains an asset ID, serial number, CMDB identifier, or another unique machine identifier, while the visible name is used as a human-readable display name.

Zabbix History Syncer suddenly spikes and keeps high on IO Usage [Repost]

DrNick — Wed, 05 Aug 2026 07:09:49 GMT

***sorry for the repost, lost connection due to cloudflare, and seemed that i also lost a big part of my text and couldnt edit post***

Hey there, hope that someone can help me with some pointers where to look at, i don't have all the log files of the event, so i cant bee that specific.

We have a small zabbix server running for quite some time, its hosted on a Ubuntu 24.04.2 LTS; MySQL ; Zabbix version 7.0.7, Running as VM on a Windows Hyper-V.
About 140 hosts monitored; about 10.500 active items; with a nvps of about 50.

The server has been running fine, no problems at all, low io, nice usage, nothing to be concerend about.
But when i was on holiday, suddenly on Sunday the 19th of July roughly between 17:00 and 19:00 our server IO Spiked and basically never returned to normal again.
IO Wait times of 50% or more and that without stopping.

Stopping the zabbix server, didn't lower it instantly; eventually it would drop. Shutting down MySQL; would stop the IO load.
Starting the MySQL server didn't start the IO spikes back again and would run normally.
After starting the zabbix server, the IO spike did return after some time. As far as i could see, the History syncer was busy more then other processes.

As far as i could see the log files from zabbix dont throw any real big issues or errors, not on startup or anything like that.
i did enable the slow log query and that does show some more queries, but i can't really tell if that causes it, or is a result of.

To the best of our knowledge in the recent past before the event, no new hosts have been added, no old hosts have been removed,
and no real changes where made. Even the host system was let alone, i mostly do those things, but not this time.

Does anyone have some clue's where to look at?
I don't think 'performance' is in place here, because of the sudden event and the load before was not that high in any way.
On the hardware host also everything seems to be normal, no broken disks, no array faults, only high IO usage since that event.
(the machine is hosting 1 other VM, but no that VM isn't causing the IO load on the main host).

Is there some option i could turn on to show more why or what is happening. In General we dont keep that much of a history, to make the server not too overloaded.
single items stored roughly 3days to max 7days (mostly depending on poll interval); trends stored mostly max 180days;

i added some screenshots, roughly 24hour graps, Prior to the event, during the event, after the event (with more detail) and after the mysql (+reboot) change.
Hope that someone can point me in some direction where to look at.

DB backup's are done 4 times a week, zabbix server is shut down, DB backup is taken, mysql is restarted, zabbix server is start up again.
This is also running for some years and was not running during this event, that would run at night time.

Code:

[mysqld]
user = mysql
bind-address = 127.0.0.1
mysqlx-bind-address = 127.0.0.1
key_buffer_size = 16M
myisam-recover-options = BACKUP
innodb_buffer_pool_size=4G
innodb_flush_log_at_trx_commit=2
log_error = /var/log/mysql/error.log
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mysql-slow.log
long_query_time = 2
max_binlog_size = 100M
binlog_expire_logs_seconds = 604800

Code:

ListenPort=10051
LogType=file
LogFile=/var/log/zabbix/zabbix_server.log
LogFileSize=5
DebugLevel=3
PidFile=/tmp/zabbix_server.pid
DBHost=localhost
DBName=zabbix
DBUser=zabbix
DBPassword=supersecret
DBPort=3306
StartPollers=10
StartIPMIPollers=0
StartPreprocessors=6
StartPollersUnreachable=10
StartTrappers=6
StartPingers=30
StartDiscoverers=1
StartHTTPPollers=2
StartTimers=2
StartEscalators=2
StartAlerters=2
StartJavaPollers=0
StartVMwareCollectors=0
SNMPTrapperFile=/opt/zabbix/tmp/zabbix_traps.tmp
StartSNMPTrapper=1
ListenIP=0.0.0.0
HousekeepingFrequency=1
MaxHousekeeperDelete=5000
CacheSize=64M
StartDBSyncers=2
HistoryCacheSize=512M
HistoryIndexCacheSize=64M
Timeout=30
TrapperTimeout=300
UnreachablePeriod=35
UnavailableDelay=60
UnreachableDelay=15
ExternalScripts=/opt/zabbix/share/zabbix/externalscripts
FpingLocation=/usr/sbin/fping
Fping6Location=/usr/sbin/fping6
LogSlowQueries=3000
TmpDir=/tmp
StartProxyPollers=1
ProxyConfigFrequency=3600
ProxyDataFrequency=60
AllowRoot=0
User=zabbix-srv

Zabbix History Syncer suddenly spikes and keeps high on IO Usage

DrNick — Tue, 04 Aug 2026 14:33:01 GMT

** Double post; this one can be deleted; please check the newer, more elaborated post here:
https://www.zabbix.com/forum/zabbix-...o-usage-repost

Hey there, hope that someone can help me with some pointers where to look at, i don't have all the log files of the event, so i cant bee that specific.

We have a small zabbix server running for quite some time, its hosted on a Ubuntu 24.04.2 LTS; MySQL ; Zabbix version 7.0.7, Running as VM on a Windows Hyper-V.
About 140 hosts monitored; about 10.500 active items; with a nvps of about 50.

The server has been running fine, no problems at all, low io, nice usage, nothing to be concerend about.
But when i was on holiday, suddenly on Sunday the 19th of July roughly between 17:00 and 19:00 our server IO Spiked and basically never returned to normal again.
IO Wait times of 50% or more and that without stopping.

Stopping the zabbix server, didn't lower it instantly; eventually it would drop. Shutting down MySQL; would stop the IO load.

Code:

[mysqld]
user = mysql
bind-address = 127.0.0.1
mysqlx-bind-address = 127.0.0.1
key_buffer_size = 16M
myisam-recover-options = BACKUP
innodb_buffer_pool_size=4G
innodb_flush_log_at_trx_commit=2
log_error = /var/log/mysql/error.log
slow_query_log = 1
slow_query_log_file = /var/log/mysql/mysql-slow.log
long_query_time = 2
max_binlog_size = 100M
binlog_expire_logs_seconds = 604800

Code:

ListenPort=10051
LogType=file
LogFile=/var/log/zabbix/zabbix_server.log
LogFileSize=5
DebugLevel=3
PidFile=/tmp/zabbix_server.pid
DBHost=localhost
DBName=zabbix
DBUser=zabbix
DBPassword=supersecret
DBPort=3306
StartPollers=10
StartIPMIPollers=0
StartPreprocessors=6
StartPollersUnreachable=10
StartTrappers=6
StartPingers=30
StartDiscoverers=1
StartHTTPPollers=2
StartTimers=2
StartEscalators=2
StartAlerters=2
StartJavaPollers=0
StartVMwareCollectors=0
SNMPTrapperFile=/opt/zabbix/tmp/zabbix_traps.tmp
StartSNMPTrapper=1
ListenIP=0.0.0.0
HousekeepingFrequency=1
MaxHousekeeperDelete=5000
CacheSize=64M
StartDBSyncers=2
HistoryCacheSize=512M
HistoryIndexCacheSize=64M
Timeout=30
TrapperTimeout=300
UnreachablePeriod=35
UnavailableDelay=60
UnreachableDelay=15
ExternalScripts=/opt/zabbix/share/zabbix/externalscripts
FpingLocation=/usr/sbin/fping
Fping6Location=/usr/sbin/fping6
LogSlowQueries=3000
TmpDir=/tmp
StartProxyPollers=1
ProxyConfigFrequency=3600
ProxyDataFrequency=60
AllowRoot=0
User=zabbix-srv

Zabbix 7.0.26 - 7.0.29 housekeeper consumes all available RAM

MelvinS — Mon, 03 Aug 2026 06:21:19 GMT

Hello,

I have a memory problem with the housekeeper in Zabbix 7.0.26 - 7.0.29 using MariaDB.

Housekeeping was disabled for some time, so old history data accumulated. After starting it manually, the housekeeper continuously consumes more RAM while processing old history and trends:
1281 11303284 11896316 /usr/sbin/zabbix_server: housekeeper [removing old history and trends]
1347 7080 599644 /usr/sbin/zabbix_server: trigger housekeeper [deleted 0 problems records in 0.013036 sec, idle for 60 second(s)]

The VM originally had 8 GB RAM and became unresponsive. I increased it to 16 GB, but the housekeeper consumed that memory as well. More RAM only delays the problem. After restarting zabbix-server, the memory is released and the server remains stable until housekeeping is started again.

This seems related to the initial history queries that retrieve itemid and MIN(clock) from all history and trend tables.

Is this a known issue in Zabbix 7.0? Is there a way to limit the housekeeper’s memory usage or safely process the accumulated history in smaller batches?

Environment:

Zabbix 7.0.29
Debian 13
MariaDB
16 GB RAM

At the moment, the database continues to grow because new history data is constantly being added, while the housekeeper cannot complete its cleanup process without exhausting all available memory.

Best regards

Agent2 NVIDIA plugin for Windows 7.4.11+ is not a valid Win32 application

evzen — Sat, 01 Aug 2026 19:33:21 GMT

There seems to be an issue - or at least something weirdly changed - in the Agent2 NVIDIA plugin for Windows 7.4.11 and newer.
The plugin does not run, with OS complaining that it cannot create the process because it's not a valid Win32 application.
All versions up to 7.4.10 work perfectly fine.

As a proof I collected the plugins 7.4.8 to 7.4.13 and one thing is clearly visible right away - the executable sizes changed significantly since 7.4.11:

Code:

C:\Program Files\Zabbix Agent 2>Directory of C:\Program Files\Zabbix Agent 2

13.03.2026  17:50        10 702 192 zabbix-agent2-plugin-nvidia-gpu-7.4.8.exe
09.04.2026  10:31        10 702 192 zabbix-agent2-plugin-nvidia-gpu-7.4.9.exe
28.05.2026  13:00        10 702 704 zabbix-agent2-plugin-nvidia-gpu-7.4.10.exe
02.06.2026  18:19         8 602 696 zabbix-agent2-plugin-nvidia-gpu-7.4.11.exe
09.07.2026  11:56         8 602 696 zabbix-agent2-plugin-nvidia-gpu-7.4.12.exe
29.07.2026  13:42         8 745 528 zabbix-agent2-plugin-nvidia-gpu-7.4.13.exe

Trying to execute the plugin - version 7.4.10 works:

Code:

C:\Program Files\Zabbix Agent 2>zabbix-agent2-plugin-nvidia-gpu-7.4.10.exe
NVIDIA plugin for Zabbix agent 2

Usage of "zabbix-agent2-plugin-nvidia-gpu-7.4.10.exe"
    zabbix-agent2-plugin-nvidia-gpu-7.4.10.exe -h
    zabbix-agent2-plugin-nvidia-gpu-7.4.10.exe -V

Options:
  -h --help                               Display this help message
  -V --version                            Print program version and exit

...but version 7.4.11 or newer does not launch:

Code:

PS C:\Program Files\Zabbix Agent 2> .\zabbix-agent2-plugin-nvidia-gpu-7.4.11.exe
ResourceUnavailable: Program 'zabbix-agent2-plugin-nvidia-gpu-7.4.11.exe' failed to run: An error occurred trying to start process 'C:\Program Files\Zabbix Agent 2\zabbix-agent2-plugin-nvidia-gpu-7.4.11.exe' with working directory 'C:\Program Files\Zabbix Agent 2'. The specified executable is not a valid application for this OS platform.At line:1 char:1
+ .\zabbix-agent2-plugin-nvidia-gpu-7.4.11.exe
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.

zabbix configuration for port 443 on nginx,mysql,php raspberry pi

colporteur — Wed, 29 Jul 2026 21:35:51 GMT

How to configure zabbix on an 8G Raspberry pi 5 OS (13 (trixie)), nginx (1.26.3-3+deb13u7), mysql (5.8+1.1.1), php-mysql (2:8.4+101) & zabbix (1:7.4.13-1+debian13) to support https using self-signed-certificates.

I have installed nginx and have it working on port 433 using the self-signed-certificates. I then installed php and it serves webpage on 443. I then installed mysql and finally zabbix. I can connect to the zabbix web interface console :443 but the error message at the bottom indicates Zabbix Server is not running:the information displayed may not be current.

Before starting the project to use port 443, I built a zabbix server using the same configuration on port 8080. The install is working. I have configured a few devices and am gathering data.

I am a new user to zabbix. No experience at all! After evaluating a few products I landed here. The goal is to replace the MikroTik Dude server with zabbix. If someone could share their knowledge or point me in the direction of https configuration resources, that would be appreciated.

So far I have tried internet searches and cull this forum looking for hints. After to many attempts to continue to count, I ask for help.

I’m close to making it work, just not close enough.