FAQ
Hi all,

I met an issue when I deploy some apps to local CF(installed from
source code), and the application start take a long time but it's not
started as well. I check the cloud_controller.log and found the
following stack trace.


============================ cloud_controller.log
=================================
2012-06-18 19:18:20.656199] cc - pid=21442 tid=86a2 fid=8273 DEBUG --
app: 52 update_from_parms
[2012-06-18 19:18:20.660369] cc - pid=21442 tid=86a2 fid=8273 DEBUG
-- app: 52 Updating ["lock_version", "state"]
[2012-06-18 19:18:20.666201] cc - pid=21442 tid=86a2 fid=8273 DEBUG
-- app: 52 Staging starting
[2012-06-18 19:18:20.877421] cc staging pid=21442 tid=86a2 fid=8273
DEBUG -- Queueing staging command /home/dragon/
cloudfoundry/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/bin/
ruby /home/dragon/cloudfoundry/vcap/cloud_controller/script/
run_plugin.rb node /tmp/d20120618-21442-1gjkc8f /tmp/
d20120618-21442-1tqwdb8 /tmp/d20120618-21442-f57csd/plugin_env.json /
home/dragon/cloudfoundry/.deployments/devbox/config/staging
[2012-06-18 19:18:20.878063] cc staging pid=21442 tid=86a2 fid=8273
DEBUG -- Starting staging command: /home/dragon/
cloudfoundry/.deployments/devbox/deploy/rubies/ruby-1.9.2-p180/bin/
ruby /home/dragon/cloudfoundry/vcap/cloud_controller/script/
run_plugin.rb node /tmp/d20120618-21442-1gjkc8f /tmp/
d20120618-21442-1tqwdb8 /tmp/d20120618-21442-f57csd/plugin_env.json /
home/dragon/cloudfoundry/.deployments/devbox/config/staging
[2012-06-18 19:18:21.060663] cc - pid=21442 tid=86a2 fid=28f7 DEBUG
-- [HealthManager] Received START request for app 51 - co-datastore
[2012-06-18 19:18:21.067676] cc - pid=21442 tid=86a2 fid=28f7 DEBUG
-- [HealthManager] Request for older version of app, ignoring
/home/dragon/cloudfoundry/.deployments/devbox/deploy/rubies/ruby-1.9.2-
p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/bundler/spec_set.rb:
88:in `block in materialize': Could not find vcap_staging-0.1.52 in
any of the sources (Bundler::GemNotFound)
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/spec_set.rb:82:in `map!'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/spec_set.rb:82:in `materialize'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/definition.rb:90:in `specs'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/definition.rb:135:in `specs_for'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/definition.rb:124:in `requested_specs'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/environment.rb:23:in `requested_specs'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/runtime.rb:11:in `setup'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler.rb:107:in `setup'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.0.18/lib/
bundler/setup.rb:17:in `<top (required)>'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/
custom_require.rb:59:in `require'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/
custom_require.rb:59:in `rescue in require'
from /home/dragon/cloudfoundry/.deployments/devbox/deploy/
rubies/ruby-1.9.2-p180/lib/ruby/site_ruby/1.9.1/rubygems/
custom_require.rb:35:in `require'
from /home/dragon/cloudfoundry/vcap/cloud_controller/script/
run_plugin.rb:5:in `<main>'
[2012-06-18 19:18:21.778145] cc staging pid=21442 tid=86a2 fid=9073
DEBUG -- Staging command FAILED with 1:
[2012-06-18 19:18:21.821371] cc - pid=21442 tid=c8ca fid=5972 WARN
-- Unable to repack application in /tmp/d20120618-21442-1tqwdb8: tar:
*: Cannot stat: No such file or directory\ntar: Exiting with failure
status due to previous errors\n pid 13736 exit 2
[2012-06-18 19:18:21.998187] cc - pid=21442 tid=86a2 fid=8273 DEBUG
-- app: 52 Staging complete
[2012-06-18 19:18:22.013657] cc_events - pid=21442 tid=86a2 fid=8273
INFO -- [2012-06-18 19:18:22 -0700, :USER, "stoneage14@163.com", "PUT:/
apps/mycpdatastore", "mycpdatastore", :SUCCEEDED]
==========================================================================

I've never seen this before, it shows something that miss a gem
package named "vcap_staging-0.1.52". but I verify the cloud foundry
ruby gems list:

......

systemu (2.4.2, 2.4.1)
terminal-table (1.4.5)
thin (1.3.1)
thor (0.14.6)
tilt (1.3.3, 1.2.2)
treetop (1.4.9)
tzinfo (0.3.26)
uuid (2.3.4)
uuidtools (2.1.2)
vcap_common (1.0.10, 1.0.8)
vcap_logging (1.0.1, 1.0.0, 0.1.3)
vcap_services_base (0.1.8)
vcap_stager (0.1.14)
vcap_staging (0.1.54)
vegas (0.1.8)
vmc (0.3.17)
........

Why the CF want to find vcap_staging-0.1.52 ? How can I resolve this ?

Thanks,
Brick

Search Discussions

Discussion Posts

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 1 of 2 | next ›
Discussion Overview
groupvcap-dev @
postedJun 19, '12 at 2:49a
activeJun 19, '12 at 4:47a
posts2
users2

People

Translate

site design / logo © 2022 Grokbase