Re: cf push fails with Tcp connection error


Danny Berger
 

It sounds like consul may not be healthy on your CC VM. Perhaps ssh there
and take a look at the logs in /var/vcap/sys/log/**/*.log for a few more
hints. Specifically you might want to take a look at whether consul is
running properly. You might also try verifying what your
default_to_diego_backend setting is.

Since this is a bit more CF-specific, you might find better luck on the
cf-dev(a)lists.cloudfoundry.org mailing list or in the channels at
http://slack.cloudfoundry.org/

On Tue, Nov 8, 2016 at 1:26 PM, Sankeerth Sai <sankyrth4u(a)gmail.com> wrote:

Trying to push applications to newly deployed cloud foundry environment on
the top of vsphere and seeing this error. Has anyone else seen the same
problem? Are there any additional properties that needs to be added to the
cf-deployment manifest file ?

Starting app groovy-application in org cloud-foundry / space tools as
admin...
FAILED
Error restarting application: Server error, status code: 500, error code:
170011, message: Stager error: Failed to open TCP connection to
stager.service.cf.internal:8888 (getaddrinfo: Name or service not known)



Thanks
SAI
--
Danny Berger

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.