Failed to deploy diego

[SimyungYang]

Now I'm trying to deploy the diego on AWS.
When I deploy the release by bosh deploy, I've got the following error.

Started updating job access_z1 > access_z1/0 (e35756c8-cddf-4273-9927-465564693e64) (canary). Failed: `access_z1/0 (e35756c8-cddf-4273-9927-465564693e64)' is not running after update (00:02:38)

Error 400007: `access_z1/0 (e35756c8-cddf-4273-9927-465564693e64)' is not running after update

I also had that kind of error when i tried to deploy CF for the first time.
can anyone tell me what i need to look at or how to figure out this kind of error?

I checked the vm status by bosh instances --ps and found out the ssh_proxy got failed

 access_z1/0 (e35756c8-cddf-4273-9927-465564693e64)*        | failing | n/a | access_z1        | 10.10.5.69 |
|   ssh_proxy                                                | failing |     |                  |            |
|   consul_agent                                             | running |     |                  |            |
|   metron_agent                                             | running |     |                  |            |
|   file_server                                              | running |     |                  |            |

does that mean the configuration of ssh_proxy was wrong or is there anything else which can cause this kind of error.?

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this. You can view the current status of your issue at: https://www.pivotaltracker.com/story/show/114372853.

[emalm]

Hi, @SimyungYang,

It'll probably be helpful to examine the logs from the access_z1 0 instance to see why it's failing. If you bosh ssh to that VM, those logs will be in /var/vcap/sys/log/ssh_proxy/ssh_proxy.stdout.log, and you can also retrieve them via bosh logs access_z1 0.

If this Diego deployment is coordinated with CF, so that the SSH-Proxy's CF authenticator is enabled, it's likely that the secret for the 'ssh-proxy' UAA client isn't being propagated to the SSH-Proxy job. That's been a common reason for the SSH-Proxy job not to start correctly.

Also, what versions of CF and Diego do you have deployed?

Thanks,
Eric, CF Runtime Diego PM

[SimyungYang]

Thank you, @ematpl for quick response.

For deployment, I just downloaded latest project from github. (master branch of diego-release & master branch of cf-release).

I'll look for the log message from access_z1 0 instance on you advice.

Thank you,

[SimyungYang]

When I tried before, I didn't really care about the version of CF & Diego.
and I just found out that there is recommend version of diego for each cf release.
I'll try with the recommended version of diego.
Thank you

[emalm]

Hi, @SimyungYang,

Were you able to resolve these errors?

Thanks,
Eric

[SimyungYang]

the environment which occurs the error was deleted in my AWS account.
and I didn't find the reason of the error unfortunately.

But I successfully deployed diego with a different yaml configuration...

Thank you, I close the issue.