Closed tnweiss closed 5 years ago
We have created an issue in Pivotal Tracker to manage this:
https://www.pivotaltracker.com/story/show/165735204
The labels on this github issue will be updated when the story is started.
I found the issue, I forgot to upload my secrets.yml to the bosh instance.
bosh-cloud update-runtime-config ${BOSH_DEPLOYMENT_DIR}/runtime-configs/dns.yml --vars-store ${DEPLOYMENT_DIR}/secrets.yml --name dns
@tnweiss i have the same issue . i dont know what you did there . i dont use the bosh-cloud command u used there , and what is in the dns.yml file couldnt find it anywhere
@addisflava that error is unfortunately a general one that means the bbs component cannot talk to locket to grab a lock and establish the master instance
It could be from a wide range of connection issues but a common one is if your cents are expired
this is the error am getting
{"timestamp":"2019-07-23T20:52:37.376033400Z","level":"info","source":"bbs","message":"bbs.starting","data":{}}
{"timestamp":"2019-07-23T20:52:52.430802403Z","level":"fatal","source":"bbs","message":"bbs.failed-to-create-locket-client","data":{"error":"context deadline exceeded","trace":"goroutine 1 [running]:\ncode.cloudfoundry.org/lager.(*logger).Fatal(0xc000072a20, 0xce4d70, 0x1e, 0xdcd460, 0x13b0860, 0x0, 0x0, 0x0)\n\t/var/vcap/data/compile/bbs/src/code.cloudfoundry.org/lager/logger.go:138 +0xc6\nmain.main()\n\t/var/vcap/data/compile/bbs/src/code.cloudfoundry.org/bbs/cmd/bbs/main.go:240 +0x41f0\n"}}
panic: context deadline exceeded
goroutine 1 [running]:
code.cloudfoundry.org/lager.(*logger).Fatal(0xc000072a20, 0xce4d70, 0x1e, 0xdcd460, 0x13b0860, 0x0, 0x0, 0x0)
/var/vcap/data/compile/bbs/src/code.cloudfoundry.org/lager/logger.go:162 +0x58c
main.main()
/var/vcap/data/compile/bbs/src/code.cloudfoundry.org/bbs/cmd/bbs/main.go:240 +0x41f0
What is this issue about?
I'm trying to deploy cloud foundry in to my aws environment using bosh. When i run the bosh deploy command the isntances are created, then nats, and adapter get updated, then when bosh tries to update diego-api it hangs, eventually spitting out the following error.
What version of cf-deployment are you using?
v7.11.0
Please include the
bosh deploy...
command, including all the operations files (plus any experimental operation files you're using):Please provide output that helps describe the issue:
Below are tailed logs from the diego-api instance
/var/vcap/sys/log/bbs/bbs.stderr.log
/var/vcap/sys/log/bbs/bbs.stdout.log
/var/vcap/sys/log/bbs/bpm.log
/var/vcap/sys/log/locket/locket.stderr.log
What IaaS is this issue occurring on?
AWS
Is there anything else unique or special about your setup?
I have recently deployed version 1.38.0 succesfully. I made sure to clear the external RDS tables before redeploying.
Appreciate the help!