bosh task tasknumber --debug wrote:

Are you using centos ? /etc/resolvconf/resolv.conf.d/head wrote:

These are the errors I found under /var/vcap/sys/log: /var/vcap/sys/log/consul_template_ctl.err.log: [2015-06-17 05:10:03+0000] ------------ STARTING consul_template_ctl at Wed Jun 17 05:10:03 UTC

whats the location of the log file? Sincerely, DUlanjalie wrote: -- Dulanjalie

Can you provide the task debug logs please ? wrote:

I tried. Allowed all the IPs. Still the same issue. Removed the VDC and started all over again. Still the same issue. Is there any ruby/gem version that i need to

Sometime the agent don t respond because the load on the VM is too high during some compilation, so yes you have a timeout error. aristoteles.neto(a)webdrive.co.nz> wrote:

Theres no timeout for compilation tasks as far as I know, provided the compilation VM started successfully and the agent is still responding. Based on the message, I’d hazard a guess that its

bosh ssh to the haproxy and check the logs /var/vcap/sys/log. wrote:

Just timeout, compiling take too much time on the t2.micro. flavio.schuindt(a)gmail.com> wrote:

I’ve had a problem similar to this when I was using HVM stem cells, without specifying an ‘ephemeral_disk’ property for the resource pool in the deployment manifest as in [1]. [1] -

Can you try using 0.0.0.0/0 as source IP .. Just want to be sure SG are not the problem wrote:

Just to post the resolution... I don't know why, but I delete all the stuff (deleted VPC) and restarted tutorial from the beginning and now it suceeds. In this same topic, I changed c3.large to

Thank you! After adding environment to meta section, the deployment is moving forward but timing out on “Started updating job ha_proxy_z1 > ha_proxy_z1/0 (canary)" What changed: meta:

Hi Ken, I execute "bosh micro deploy" from outside AWS. Still I added the rule you suggested. No luck yet :( Sincerely, Dulanjalie -- Dulanjalie

Hi Dulanjalie, if you run 'bosh micro deploy' on a AWS VM(work VM), I think you have to add a security group ingress setting to the work VM as below: | Custom TCP Rule | TCP | 25889 | bosh SG

Hi Gwenn, I do not see any error in my sg settings. Still the issue is there. I brought up a VM manually then I was able to SSH to it. So i believe key is correct. TypeProtocolPort RangeSourceCustom

I'm currently working on some bash scripts with 'expect' tool to automate the bosh ssh command, as I didn't found any other simple solution. consul/ansible might a right way to solve the problem, but

Hi Danny, guys I may confirm the issue. We faced with it many times. Going to collect more info on next occurrence.

Please check security groups on AWS http://bosh.io/docs/init-aws.html#create-security Can be a communication issue between director and the bosh agent. wrote: