Hi all,
I am using bosh to deploy cf-153, all jobs are running now. But I get this
error message: CFoundry::StackNotFound: 250003: The stack could not be
found: The requested app stack lucid64 is not available on this system.
I believe this error message is thrown here:
https://github.com/cloudfoundry/cloud_controller_ng/blob/master/lib/cloud_controller/stager/stager_pool.rb#L39

What's more, there are 3 files under directory rootfs in warden,
ls -l /var/vcap/data/packages/warden/37.1/warden/root/linux/rootfs
total 12
-rwxrwxr-x 1 root root 942 Dec 19 18:27 centos.sh
-rwxrwxr-x 1 root root 427 Dec 19 18:27 setup.sh
-rwxrwxr-x 1 root root 2597 Dec 19 18:27 ubuntu.sh

Meanwhile, the messages about lucid64 shown by command $ nats sub '>' look
like that:
Msg received :
'{"id":"0-adf045127f954b85a44be4eff1f00f15","stacks":["lucid64"],"available_memory":2048,"available_disk":20000,"app_id_to_count":{},"placement_properties":{"zone":"default"}}'
Msg received :
'{"id":"0-adf045127f954b85a44be4eff1f00f15","stacks":["lucid64"],"available_memory":2048}'

However, I can't find any information concernning dea.advertise or
staging.advertise,
I assume that's the root cause. So, how can I solve it? Thanks!

--
Best regards,
DuJun



2014/1/3 James Bayer <jbayer@gopivotal.com>
your uaa yml file certainly appears to be incorrect.

how did you get this system created? did you use BOSH or an alternative?

On Thu, Jan 2, 2014 at 11:14 PM, Doom zhou wrote:

hi Harry Zhang
i push with --stack lucid64 or anything else(oh i don't know how to list
my STACKNAME) ,same error below output
output:
1,388,732,199vagrant@cf sinatra$cf push --stack lucid64
Using manifest file manifest.yml


Creating hello... OK


Binding hello.192.168.12.34.xip.io to hello... OK
Uploading hello... OK
Preparing to start hello... FAILED
CFoundry::StackNotFound: 250003: The stack could not be found: Therequested app stack lucid64
is not available on this system

and
1,388,731,438vagrant@cf vagrant$ nats-sub '>'
Listening on [>]
[#1] Received on [router.start] :
'{"id":"66d31af325413c2e26f7e246bb65fb72","hosts":["10.0.2.15"]}'
[#2] Received on [router.register] :
'{"host":"192.168.12.34","port":8181,"uris":["api.192.168.12.34.xip.io
"],"tags":{"component":"CloudController"}}'

so my dea may be incorrect

all my config files are adjust with
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/adSWqNAE1g4
introduce

version info

1. host:Centos 6.5
2. vagrant:1.3
3. ruby(rbenv)1.9.3
4. vagrant box: precise64
5. java 1.6
6. mvn 3.1

sth log error collect
uaa.log

[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[2014-01-03 04:31:19.166] uaa/uaa - ???? [main] .... ERROR ---
YamlConfigurationValidator: Failed to load YAML validation bean. YourYAML file may be invalid
.
Can't construct a java object for tag:yaml.org,2002:org.cloudfoundry.identity.uaa.UaaConfiguration;
exception=Cannot create property=pid for
JavaBean=org.cloudfoundry.identity.uaa.UaaConfiguration@384e57ba; Unable
to find property 'pid' on class: org.cloudfoundry.identity.uaa.UaaConf



-_-
On Thursday, January 2, 2014 10:26:30 PM UTC+8, Harry Zhang wrote:

Well, let's make it more clear. There are at least two parts need to
aware lucid64: CC and DEA. You can consider lucid64 as a linux file system
with pre-installed components used for warden.

1. Try to add param --stack STACKNAME when "cf push", see what happens?
2. Can you see debug logs in DEA like below?
[dea.advertise] : '{"id":"0-aca1cceecf9f6c0fee953b38cf8129
65","prod":false,"stacks":["lucid64"],"available_memory":4024}'
If yes, your dea may being working well.
3. Do you have corret config/stacks.yml in CC_ng? If yes, your cc
should know lucid64

If not, you should check warden log carefully, to see if there's
something wrong when start the container.

And posingt your OS version of stemcell also helps here.

On Thursday, January 2, 2014 5:17:48 PM UTC+8, dj19...@gmail.com wrote:

Hi all,
I am deploying cf-153 and meet a problem about lucid64,

root@inception-server-Quantal:~/cf_demoapp_ruby_rack# cf push
Warning: url is not a valid manifest attribute. Please remove this
attribute from your manifest to get rid of this warning
Using manifest file manifest.yml

Creating hello... OK

1: hello
2: none
Subdomain> hello

1: cloudstack.cf.test
2: none
Domain> cloudstack.cf.test

Creating route hello.cloudstack.cf.test... OK
Binding hello.cloudstack.cf.test to hello... OK
Uploading hello... OK
Preparing to start hello... FAILED
CFoundry::StackNotFound: 250003: The stack could not be found: The
requested app stack lucid64 is not available on this system.

But I can't find any error messages in cc or dea? Is there anyone can
provide me with some clues? Thanks!

--
Best Regards,
DuJun
To unsubscribe from this group and stop receiving emails from it, send
an email to vcap-dev+unsubscribe@cloudfoundry.org.


--
Thank you,

James Bayer

To unsubscribe from this group and stop receiving emails from it, send an
email to vcap-dev+unsubscribe@cloudfoundry.org.
To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+unsubscribe@cloudfoundry.org.

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 8 of 9 | next ›
Discussion Overview
groupvcap-dev @
postedJan 2, '14 at 9:17a
activeJan 9, '14 at 8:08a
posts9
users5

People

Translate

site design / logo © 2021 Grokbase