Revision history [back]

There are a few potential causes for this issue. Here are a few steps that you can take to try to resolve the issue:

1. Check that the Jenkins agent is running. If the agent is not running, then the tcpSlaveAgentListener will not be active. You can check the agent logs to see if there are any errors preventing it from connecting.

2. Check your firewall settings. If the tcpSlaveAgentListener is being blocked by a firewall, you may need to adjust your firewall settings to allow inbound connections to the Jenkins server.

3. Confirm that the port number for the tcpSlaveAgentListener is correct. By default, the tcpSlaveAgentListener listens on port 50000. If this port has been changed, you will need to update your Jenkins configuration to reflect this change.

4. Check that the Jenkins listener configuration is correct. The tcpSlaveAgentListener is configured in the Jenkins configuration file. If the configuration is incorrect, the listener may not be started. Check that the agent port and host name settings are correct.

If you are still unable to locate the tcpSlaveAgentListener after trying these steps, you may need to seek further assistance from the Jenkins community or support team.