[ZBX-26903] Message: "unknown request received from "127.0.0.1": [zabbix.stats]" in proxy log, when proxy is monitored by Zabbix agent (Proxy health template) Created: 2025 Aug 22  Updated: 2026 Apr 27  Resolved: 2026 Apr 27

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 7.4.2rc2, 8.0.0alpha1
Fix Version/s: 7.4.10rc1, 8.0.0beta1 (master)

Type: Problem report Priority: Major
Reporter: Nikita Gogolevs Assignee: Sergejs Boidenko
Resolution: Fixed Votes: 14
Labels: agent, logs, proxy, server
Remaining Estimate: Not Specified
Time Spent: 16h
Original Estimate: Not Specified

Attachments: PNG File screenshot-1.png     PNG File screenshot-2.png    
Issue Links:
Causes
caused by ZBXNEXT-9873 Backend: Frontend to Server communica... Closed
Duplicate
Team: Team A
Sprint: S26-W16/17
Story Points: 0.3

 Description   

Steps to reproduce:

  1. Create a host for monitoring the proxy, use template: Zabbix proxy health by Zabbix agent
  2. Start server, agent, proxy
  3. See the proxy logs

Result:
Message regarding agent item zabbix.stats[] keeps appearing in the log:

 55015:20250822:144649.061 unknown request received from "127.0.0.1": [zabbix.stats]
 55012:20250822:144650.065 unknown request received from "127.0.0.1": [zabbix.stats]
 55014:20250822:144651.068 unknown request received from "127.0.0.1": [zabbix.stats]
 55016:20250822:144749.067 unknown request received from "127.0.0.1": [zabbix.stats]
 55012:20250822:144750.060 unknown request received from "127.0.0.1": [zabbix.stats]
 55014:20250822:144751.061 unknown request received from "127.0.0.1": [zabbix.stats]
 55015:20250822:144849.057 unknown request received from "127.0.0.1": [zabbix.stats]
 55012:20250822:144850.066 unknown request received from "127.0.0.1": [zabbix.stats]

Expected:
There should be no issues related to zabbix.stats metric

 Comments   
Comment by Tony den Haan [ 2025 Oct 31 ]

Getting the same with template "Remote Zabbix proxy health". Server and proxy 7.4.4

Comment by Tony den Haan [ 2025 Nov 04 ]

I had a closer look and replaced zabbis.stats[ in the template with zabbix[stats, appears to fix the issue.

EDIT: this is very quick, dirty and partly wrong, real problem is 'zabbix.stats' is master item which is not used for all items.

Comment by Alessandro Burati [ 2025 Nov 04 ]

Hi,

we have same issue with template Zabbix proxy health by Zabbix agent active, but if we change items from zabbix.stats[ to zabbix[stats they  become unrecognized and of course the message regarding agent item stops in the log.. 

Where did you change the template to fix the issue?

Thank you.

Comment by Tony den Haan [ 2025 Nov 04 ]

I downloaded the template and edited that, and then imported it again. After deleting the bad one of course.

Comment by Adrien Demma [ 2026 Jan 06 ]

So, is this a proper solution before official fix? Our logs are spammed with this.

Comment by Volodymyr Mosiichuk [ 2026 Jan 06 ]

Hi,
Not really sure how you guys fix that. The same I'm getting with Server 7.4.5 and Proxy 7.4.5/7.4.6.

My template "Remote Zabbix proxy health" has correct items like zabbix[stats,*] from stock.
I think these three main items are causing the issue, since there are 3 repeatable messagesin the logs.

Comment by Alessandro Burati [ 2026 Jan 08 ]

I'm sorry but I didn't solved the problem, I still receive thousands of spam logs like this every day (version 7.4.6).

I tried to edit template as suggested by Tony den Haan but I lose reading the items so I revert the modify.

Comment by Urmo Braun [ 2026 Apr 04 ]

This issue is still present in 7.4.8 and I have investigated it further.

The bug is in src/libs/zbxtrapper/trapper.c, where send_internal_stats_json(...) is called on line 1244 (7.4.8). It does not return immediately, and execution continues through the standard request-processing logic, eventually reaching the generic handler that logs:

unknown request received from "127.0.0.1": [zabbix.stats]

So the request is handled correctly, but due to missing control-flow termination it is later incorrectly treated as unknown.

The fix is to return immediately after handling the stats request (e.g. return ret;) or convert subsequent if statements into an else if chain to prevent fall-through.

I applied the fix locally (adding return ret; after send_internal_stats_json(...)), rebuilt Zabbix, and verified that the log messages disappear and stats collection works as expected.

Comment by Vladislavs Sokurenko [ 2026 Apr 07 ]

Looks like caused by ZBXNEXT-9873

Comment by Sergejs Boidenko [ 2026 Apr 22 ]

Available in versions:

Generated at Fri May 08 18:20:18 EEST 2026 using Jira 10.3.18#10030018-sha1:5642e4ad348b6c2a83ebdba689d04763a2393cab.