zabbix-agent4 not running on 32xxx port needed to connect to docker

Inack1986

Hello,

I tried to install the agent, but on 10050 port the agent runs fine (no server listening). When I change to 32961 the docker local port the agent crashed mykfcexperience.

19073:20181118:091447.686 Starting Zabbix Agent [JANUS]. Zabbix 4.0.0 (revision 85308).
 19073:20181118:091447.686 **** Enabled features ****
 19073:20181118:091447.687 IPv6 support:          YES
 19073:20181118:091447.687 TLS support:           YES
 19073:20181118:091447.687 **************************
 19073:20181118:091447.687 using configuration file: /usr/local/etc/zabbix40/zabbix_agentd.conf
 19073:20181118:091447.687 agent #0 started [main process]
 19189:20181118:091447.687 agent #1 started [collector]
 19231:20181118:091447.687 agent #2 started [listener #1]
 19296:20181118:091447.688 agent #3 started [listener #2]
 19404:20181118:091447.688 agent #4 started [listener #3]
 19296:20181118:091710.149 Got signal [signal:15(SIGTERM),sender_pid:16781,sender_uid:0,reason:65537]. Exiting ...
 19404:20181118:091710.149 Got signal [signal:15(SIGTERM),sender_pid:16781,sender_uid:0,reason:65537]. Exiting ...
 19231:20181118:091710.149 Got signal [signal:15(SIGTERM),sender_pid:16781,sender_uid:0,reason:65537]. Exiting ...
 19073:20181118:091710.149 Got signal [signal:15(SIGTERM),sender_pid:16781,sender_uid:0,reason:65537]. Exiting ...
 19189:20181118:091710.149 Got signal [signal:15(SIGTERM),sender_pid:16781,sender_uid:0,reason:65537]. Exiting ...
 19073:20181118:091710.150 Zabbix Agent stopped. Zabbix 4.0.0 (revision 85308).

wadephillip

@inack1986 It seems that you have encountered an issue while trying to install the agent on port 32961, which is the local port for Docker. It appears that the agent crashes when you attempt to use this port, while it runs without any issue on port 10050, but there is no server listening on this port.

There could be several reasons for this problem, including a configuration issue or a conflict with another service running on the same port. One possible solution would be to check the configuration settings for the agent and ensure that it is set up correctly to listen on the desired port. You may also want to verify that there are no other services using the same port, which could cause conflicts and prevent the agent from running properly.

If the problem persists, it may be helpful to reach out to the support team for the agent to see if they can provide further assistance in resolving the issue.

I hope this helps, and please let me know if you have any further questions or concerns.