Debian 12

It's normal to have errors about enexpected fields, because there were protocol changes related to addition of configurable timeouts per item.

But it's strange proxies last seen not updated for the same server version. Does any data come from this proxy at all?

What is the most reliable way to test?

Its a lab setup, each proxy monitoring only its own host.

I expect answer is no. Definitely more items not arriving in queue

Oh, my bad. Real problem "proxy not starting and not creating logs".

Next step for this is running in foreground, or something else?

The proxy completely fails to start after updating:

● zabbix-proxy.service - Zabbix Proxy
     Loaded: loaded (/lib/systemd/system/zabbix-proxy.service; enabled; preset: enabled)
     Active: activating (auto-restart) (Result: exit-code) since Wed 2024-01-03 10:10:22 CET; 6s ago
    Process: 88708 ExecStart=/usr/sbin/zabbix_proxy -c $CONFFILE (code=exited, status=1/FAILURE)
        CPU: 24ms
Jan 03 10:10:22 zbx7prxLan1 systemd[1]: zabbix-proxy.service: Control process exited, code=exited, status=1/FAILURE
Jan 03 10:10:22 zbx7prxLan1 systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'.
Jan 03 10:10:22 zbx7prxLan1 systemd[1]: Failed to start zabbix-proxy.service - Zabbix Proxy.
 

And last line in /var/log/zabbix/zabbix_proxy.log is

780:20231228:165450.996 Zabbix Proxy stopped. Zabbix 7.0.0alpha1 (revision aef542ad8ae).

Well, real problem was my configuration error in ProxyMemoryBufferAge.

$ sudo /usr/sbin/zabbix_proxy -T -c /etc/zabbix/zabbix_proxy.conf
Validating configuration file "/etc/zabbix/zabbix_proxy.conf"
zabbix_proxy [88846]: ERROR: wrong value of "ProxyMemoryBufferAge" configuration parameter

I failed noticing gap in allowed values:

### Option: ProxyMemoryBufferAge
#       Maximum age of data in proxy memory buffer, in seconds.
#       When enabled (not zero) and records in proxy memory buffer are older, then it forces proxy buffer
#       to switch to database mode until all records are uploaded to server.
#       This parameter must be less or equal to ProxyOfflineBuffer parameter.
#
# Mandatory: no
# Range: 0,600-864000
# Default:
# ProxyMemoryBufferAge=0
ProxyMemoryBufferAge=300

 Thank you for support and sorry.

I think reason for this user error is all my attention was consumed by

 This parameter must be less or equal to ProxyOfflineBuffer parameter

and many times checking ProxyOfflineBuffer=32 (hours) is less than ProxyMemoryBufferAge=300 (seconds).
 

EDIT: See? Wrong again, 32 is MORE than 300!

Yes, we will make this message clearer.

Fixed in:

• 7.0.0beta1 1799d1bec22

Well thanks. But I meant something else. I see this point is hard to catch.

I focused on the units problem so much that I missed

ProxyMemoryBufferAge=300

is out of allowed range for ProxyMemoryBufferAge

Range: 0,600-864000

Question 1: What is reason for ProxyOfflineBuffer*3600 > ProxyMemoryBufferAge check?

Anything bad happens, or ProxyMemoryBufferAge just becomes effectively zero/forever?

Question 2: Is it necessary to set ProxyOfflineBuffer using one-hour steps? Would "2.5h" break?

If not, I propose allowing time suffixes like in frontend (s, m, h, d, w, M) and setting all in "seconds".

At least for me, comparing "32h" and "300s" or just "300" requires way less attention for humans.

user185953, q1 - ProxyOfflineBuffer would never work if we allowed bigger ProxyMemoryBufferAge.  q2 - "2.5h" is not supported, but in general adding units to all time and period related parameters in the .conf files is something we want to add in the future.