Cannot connect with Zabbix Agent 5.0.21 on Fedora 36 to Zabbix Server 6.2.1

[markfs]

Hi guys,

I have a problem to connecting from Zabbix Agent 5.0.21 on Fedora 36 to Zabbix Server 6.2.1
The server runs in the Docker container, the agent works fine on Windows, just not on Fedora.
Zabbix_agentd.log says

2196:20220817:220526.258 Starting Zabbix Agent [xyz123]. Zabbix 5.0.21 (revision 47104dd574).
2196:20220817:220526.258 **** Enabled features ****
2196:20220817:220526.258 IPv6 support: YES
2196:20220817:220526.258 TLS support: YES
2196:20220817:220526.258 **************************
2196:20220817:220526.258 using configuration file: /etc/zabbix_agentd.conf
2196:20220817:220526.258 agent #0 started [main process]
2198:20220817:220526.259 agent #1 [collector]
2199:20220817:220526.259 agent #2 started[listener #1]
2200:20220817:220526.260 agent #3 started[listener #2]
2201:20220817:220526.260 agent #4 started[listener #3]
2202:20220817:220526.261 agent #5 started [active checks #1]
2196:20220817:220743.953 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
2196:20220817:220743.956 Zabbix Agent stopped. Zabbix 5.0.21 (revision 47104dd574).

The agent runs and stops after some time.

Error message in the server is "Zabbix agent is not available (for 3m)"

Port 10050 in the firewall on the server and host are enabled,
ping each other is also possible.

Can this have something to do with the version of the agent?

[tim.mooney]

The 5.0.x agent should work fine with a 6.2.x server.

You say you're connecting from the agent to the server, which suggests you're using active checks. I also see "active checks" in the agent log. Have you opened port 10051 on the server, so the agent can initiate connections to that port?

The TERM signal the agent receives in the log snippet you show suggests some other process told the agent to shut down. Assuming this wasn't a case where you manually shut down the agent while debugging the issue, is there something else on the Fedora client that would be telling the agent to shut down?

Are you using SELinux, and if so, have the appropriate labels been applied on the client?

[markfs]

Hi Tim,

thanks for your response.

The agent is now stable, the firewall ports 10050 and 10051are activated.
SElinux is active, what can I do to make it work?

[tim.mooney]

At least for RHEL, there is a separate package (zabbix-selinux-policy) that you can load, have you tried loading that on the Fedora system to see if it helps?