Pivotal Knowledge Base


Elastic Runtime Deploy Fails with a UDP Port Error


Pivotal Elastic Runtime 1.6 to 1.12


When deploying an Elastic Runtime job, the deploy fails and returns the following error: 

Failed to start UDP listener. Err: listen udp bind: address already in use


dhclient, the Linux process that sends Dynamic Host Configuration Protocol (DHCP) client requests, claims two UDP ports at random when a virtual machine (VM) starts. Because the Linux process selects the ports rather than Elastic Runtime, it is possible for dhclient to select a port that is already in use by a job in your deployment.

If dhclient selects a port that one of your Elastic Runtime jobs is configured to use, deploying that job fails and returns the above error.


Restart the VM that produces this error. Upon restart, the dhclient process selects two new UDP ports.


Powered by Zendesk