Date
1 - 4 of 4
`router_z1/0' is not running after update
|
Sam Dai
This issue has been resolved in https://github.com/cloudfoundry-incubator/cf-routing-release/issues/28, the root cause of this issue is that cf cli caches RoutingEndpoint in ~/cf/config.json so do a cf login again
cf login will fix this issue. |
|
|
|
Sam Dai
Yes, I haven't deployed cf-routing-release, I just deployed cf-routing-release, but meet a new issue, when I run command "cf router-groups", the following error is shown:
FAILED This command requires the Routing API. Your targeted endpoint reports it is not enabled. But I have enabled routing_api by setting "routing_api: enabled: true" in cf.yml. what else do I need configure? Thanks, Sam |
|
|
|
Christopher Piraino <cpiraino@...>
Hi Sam,
toggle quoted message
Show quoted text
To be sure about why the router_z1 VM is failing, you would want to look at the "monit summary" of the processes running on the router VM to see which one is failing. Then, you could look at the logs under "/var/vcap/sys/log" to find any errors. In your case though, trying to enable routing_api, the first question I would ask is whether or not you have the cf-routing-release <https://github.com/cloudfoundry-incubator/cf-routing-release> deployed already. If not, then setting "routing_api: enabled: true" will cause the GoRouter to fail to start up, since it will fail to connect to the routing API. - Chris On Wed, Apr 27, 2016 at 9:04 AM, Sam Dai <sam.dai(a)servicemax.com> wrote:
Hello, |
|
|
|
Sam Dai
Hello,
I just installed CF release v235, I used command "./scripts/generate-bosh-lite-dev-manifest" to generate a cf.yml, I enabled routing_api by setting "routing_api: enabled: true" in cf.yml, when I run the following commands: bosh create release --force && bosh -n upload release && bosh -n deploy There is the following error: Error 400007: `router_z1/0' is not running after update The detailed error message is as below: E, [2016-04-27 15:59:31 #8426] [task:6] ERROR -- DirectorJobRunner: `router_z1/0' is not running after update /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/instance_updater.rb:93:in `update' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/job_updater.rb:74:in `block (2 levels) in update_canary_instance' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3074.0/lib/common/thread_formatter.rb:49:in `with_thread_name' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/job_updater.rb:72:in `block in update_canary_instance' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/event_log.rb:97:in `call' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/event_log.rb:97:in `advance_and_track' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/job_updater.rb:71:in `update_canary_instance' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh-director-1.3074.0/lib/bosh/director/job_updater.rb:65:in `block (2 levels) in update_canaries' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3074.0/lib/common/thread_pool.rb:77:in `call' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3074.0/lib/common/thread_pool.rb:77:in `block (2 levels) in create_thread' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3074.0/lib/common/thread_pool.rb:63:in `loop' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/bosh_common-1.3074.0/lib/common/thread_pool.rb:63:in `block in create_thread' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `call' /var/vcap/packages/director/gem_home/ruby/2.1.0/gems/logging-1.8.2/lib/logging/diagnostic_context.rb:323:in `block in create_with_logging_context' Thanks, Sam |
|
|