Don't know but some things you could try are:
Check if the ipadress of your microbosh has changed.
Check which dns server has been configured on the cf nodes.
If they differ try triggering a reconfigure.
By doing a "bosh recreate {job}"
if this solves the problem for that job you could do a "bosh deploy

I have not tested any of the above things but this is what I should do.
On Tuesday, July 9, 2013 6:00:30 AM UTC+2, Mike Williams wrote:

Having "updated" my MicroBOSH with "bosh micro deploy $stemcell --update"
(which created a new MicroBOSH VM), my Cloud Foundry nodes are now a little
sick. The logs are full of things like:

mount.nfs: DNS resolution failed for 0.core.default.cf.microbosh: Name
or service not known

Oops. How do I fix DNS resolution for my existing CF VMs?

cheers, Mike


Have an innovative day

*Innovation Factory *De Lairessestraat 180* *1075 HM Amsterdam* *+31
20 7787008 www.innovationfactory.eu

*The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer. Innovation Factory does not accept
liability for any errors, viruses or omissions in the contents of this
message, which may arise as a result of e-mail transmission. No employee or
agent is authorized to conclude any binding agreement on behalf of
Innovation Factory with another party by email.*

Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 6 | next ›
Discussion Overview
groupbosh-users @
postedJul 9, '13 at 4:00a
activeJul 11, '13 at 2:01a



site design / logo © 2021 Grokbase