-
Documentation task
-
Resolution: Fixed
-
Trivial
-
None
-
7.2.1
-
None
-
S25-W2/3, S25-W4/5, S25-W6/7, S25-W8/9, S25-W12/13, S25-W14/15
-
0.1
Steps to reproduce:
**
Just run Zabbix Server
Result:
I noticed that at least since upgrading to 7.2.1, the Zabbix Server binds to random UPD ports shortly after startup. They differ after restarting.
root@zabbix:~# ss -ulp | grep zabbix_server UNCONN 0 0 0.0.0.0:48890 0.0.0.0:* users:(("zabbix_server",pid=3621585,fd=21)) UNCONN 0 0 0.0.0.0:36795 0.0.0.0:* users:(("zabbix_server",pid=3621597,fd=20)) UNCONN 0 0 0.0.0.0:34756 0.0.0.0:* users:(("zabbix_server",pid=3621583,fd=21)) UNCONN 0 0 0.0.0.0:53551 0.0.0.0:* users:(("zabbix_server",pid=3621598,fd=21)) UNCONN 0 0 0.0.0.0:41340 0.0.0.0:* users:(("zabbix_server",pid=3621584,fd=21))
Even with DebugLevel=5 I can't see any relevant log lines as the ports are bound to. 7.0.6 doesn't seem to do this.
Expected:
I'd expect Zabbix Server not to bind to any UDP port, especially not globally and undocumentedly.
- mentioned in
-
Page Loading...
