404: entity not found or inaccessible

yangzif...@gmail.com

unread,

Sep 13, 2012, 4:29:21 AM9/13/12

to vcap...@cloudfoundry.org

with you guys' help, Now I have finished the installation without any ERROR:

But when I use it, another problem comes:

root@arch3:~/cloudfoundry/vcap/dev_setup/bin# ./vcap_dev -n rest start

Targeting deployment "rest" with cloudfoundry home ""

Setting up cloud controller environment

Using cloudfoundry config from /root/cloudfoundry/.deployments/rest/config

Executing /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/bin/ruby /root/cloudfoundry/vcap/dev_setup/bin/vcap start cloud_controller mysql_gateway redis_gateway mongodb_node redis_node health_manager mongodb_gateway router -c /root/cloudfoundry/.deployments/rest/config -v /root/cloudfoundry -l /root/cloudfoundry/.deployments/rest/log

cloud_controller : RUNNING

health_manager : RUNNING

router : RUNNING

only 3 processes are running. I see the document "Single/Multi Node VCAP Deployment using dev_setup". there are much more processes.

and when I use vmc to test, the result is

root@arch3:~/cloudfoundry/vcap/dev_setup/bin# vmc target api.vcap.me

Successfully targeted to [http://api.vcap.me]

root@arch3:~/cloudfoundry/vcap/dev_setup/bin# vmc register

Email: y...@gmail.com

Password: ***

Verify Password: ***

Creating New User: OK

Attempting login to [http://api.vcap.me]

Problem with login to 'http://api.vcap.me', 404: entity not found or inaccessible, try again or register for an account.

Haipeng Wu

unread,

Sep 13, 2012, 7:49:02 AM9/13/12

to vcap...@cloudfoundry.org

I wonder how you did the setup, is that "./vcap_dev_setup"?

You used "-n rest" when starting cloud foundry, you made a deployment called "rest" before?

haipeng

Orson

unread,

Sep 13, 2012, 7:01:00 PM9/13/12

to vcap...@cloudfoundry.org, yangzif...@gmail.com

I was having an identical issue - I traced it back to an issue with the VMC gem version 0.3.21. Downgrading the gem to version 0.3.18 resolved it.

YMMV, HTH.

Orson

yangzif...@gmail.com

unread,

Sep 13, 2012, 8:11:38 PM9/13/12

to vcap...@cloudfoundry.org

Yes, I made a brand new installation according to 'Single/Multi Node VCAP Deployment using dev_setup'.

And I got successful installation information at the end.

and use './vcap_dev -n rest start' to start the rest components.

But only 3 processes are running.

I see the logs and pid, only these three process.

在 2012年9月13日星期四UTC+8下午7时49分04秒，Haipeng Wu写道：

Haipeng Wu

unread,

Sep 13, 2012, 9:09:34 PM9/13/12

to vcap...@cloudfoundry.org

If you just use command "./vcap_dev_setup" to deploy, just use command "./vcap_dev start" to start.

haipeng

yangzif...@gmail.com

unread,

Sep 13, 2012, 9:13:52 PM9/13/12

to vcap...@cloudfoundry.org

Here is the result, still 3 processes

root@arch3:~/cloudfoundry/vcap/dev_setup/bin# ./vcap_dev start

Targeting deployment "rest" with cloudfoundry home "/root/cloudfoundry"

Setting up cloud controller environment

Using cloudfoundry config from /root/cloudfoundry/.deployments/rest/config

Executing /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/bin/ruby /root/cloudfoundry/vcap/dev_setup/bin/vcap start cloud_controller mysql_gateway redis_gateway mongodb_node redis_node health_manager mongodb_gateway router -c /root/cloudfoundry/.deployments/rest/config -v /root/cloudfoundry -l /root/cloudfoundry/.deployments/rest/log

cloud_controller : RUNNING

health_manager : RUNNING

router : RUNNING

root@arch3:~/cloudfoundry/vcap/dev_setup/bin#

in the log dir

root@arch3:~/cloudfoundry/.deployments/rest/log# ll

total 40

drwxr-xr-x 3 root root 4096 2012-09-13 09:16 ./

drwxr-xr-x 6 root root 4096 2012-09-10 20:58 ../

-rw-r--r-- 1 root root 16587 2012-09-14 02:09 cloud_controller.log

-rw-r--r-- 1 root root 2869 2012-09-14 02:09 health_manager.log

drwxr-xr-x 2 root root 4096 2012-09-13 09:17 nginx/

-rw-r--r-- 1 root root 1063 2012-09-14 02:09 router.log

in the config dir:

root@arch3:~/cloudfoundry/.deployments/rest/config# ll

total 84

drwxr-xr-x 5 root root 4096 2012-09-13 10:09 ./

drwxr-xr-x 6 root root 4096 2012-09-10 20:58 ../

-rw-r--r-- 1 root root 3670 2012-09-13 04:54 cloud_controller.yml

-rw-r--r-- 1 root root 775 2012-09-13 05:01 deploy.json

-rw-r--r-- 1 root root 372 2012-09-10 20:58 deployment_info.json

-rw-r--r-- 1 root root 1731 2012-09-13 09:14 health_manager.yml

drwxr-xr-x 2 root root 4096 2012-09-10 20:58 legacy_staging/

-rw-r--r-- 1 root root 288 2012-09-13 04:44 mongodb_backup.cron

-rw-r--r-- 1 root root 451 2012-09-13 04:44 mongodb_backup.yml

-rw-r--r-- 1 root root 484 2012-09-13 05:00 mongodb_gateway.yml

-rw-r--r-- 1 root root 925 2012-09-13 04:44 mongodb_node.yml

-rw-r--r-- 1 root root 449 2012-09-13 09:18 mysql_gateway.yml

drwxr-xr-x 2 root root 4096 2012-09-13 09:19 nats_server/

-rw-r--r-- 1 root root 280 2012-09-13 05:00 redis_backup.cron

-rw-r--r-- 1 root root 195 2012-09-13 05:00 redis_backup.yml

-rw-r--r-- 1 root root 463 2012-09-13 05:00 redis_gateway.yml

-rw-r--r-- 1 root root 665 2012-09-13 10:06 redis_node.yml

-rw-r--r-- 1 root root 211 2012-09-13 08:52 router.yml

-rw-r--r-- 1 root root 3561 2012-09-13 04:54 runtimes.yml

drwxr-xr-x 2 root root 4096 2012-09-13 05:00 staging/

-rw-r--r-- 1 root root 140 2012-09-13 05:01 vcap_components.json

在 2012年9月14日星期五UTC+8上午9时09分35秒，Haipeng Wu写道：

Haipeng Wu

unread,

Sep 13, 2012, 9:49:14 PM9/13/12

to vcap...@cloudfoundry.org

How did you deploy? From your information, your deployment name is rest, but default should be dev_box.

yangzif...@gmail.com

unread,

Sep 13, 2012, 10:23:01 PM9/13/12

to vcap...@cloudfoundry.org

Hi

there are 3 servers.

lib184 is rest, lab61 is dea, Lab 186 is mysql

using below 3 setup config:

rest.yml:

deployment:

jobs:

install:

- nats_server

- cloud_controller:

builtin_services:

- redis

- mongodb

- mysql

- router

- health_manager

- ccdb

- redis_node:

index: "0"

- redis_gateway

- mysql_gateway

- mongodb_node:

index: "0"

- mongodb_gateway

dea.yml

# Deployment

# ----------

deployment:

jobs:

install:

- dea

installed:

- nats_server:

host: "192.168.161.184"

port: "4222"

user: "nats"

password: "nats"

mysql0.yml:

deployment:

jobs:

install:

- mysql_node:

index: "0"

installed:

- nats_server:

host: "192.168.161.184"

在 2012年9月14日星期五UTC+8上午9时49分15秒，Haipeng Wu写道：

Haipeng Wu

unread,

Sep 14, 2012, 12:47:31 AM9/14/12

to vcap...@cloudfoundry.org

From your start information, the missed processed are all service components.

Do you have these source code?

If so, I have no idea why they all missed.

haipeng

yangzif...@gmail.com

unread,

Sep 14, 2012, 2:21:02 AM9/14/12

to vcap...@cloudfoundry.org

where shoud be the service code?

~/cloudfoundry/vcap/services is empty

在 2012年9月14日星期五UTC+8下午12时47分32秒，Haipeng Wu写道：

Haipeng Wu

unread,

Sep 14, 2012, 2:42:16 AM9/14/12

to vcap...@cloudfoundry.org

git submodule update --init

yangzif...@gmail.com

unread,

Sep 14, 2012, 3:31:09 AM9/14/12

to vcap...@cloudfoundry.org

Yes, after that , the process show up

but they can't be started, do I need to reinstall it?

Error Message is :

root@arch3:~/cloudfoundry/vcap/dev_setup/bin# ./vcap_dev -n rest restart

Targeting deployment "rest" with cloudfoundry home ""

Setting up cloud controller environment

Using cloudfoundry config from /root/cloudfoundry/.deployments/rest/config

Executing /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/bin/ruby /root/cloudfoundry/vcap/dev_setup/bin/vcap restart cloud_controller redis_gateway health_manager redis_node router mongodb_gateway mongodb_node mysql_gateway -c /root/cloudfoundry/.deployments/rest/config -v /root/cloudfoundry -l /root/cloudfoundry/.deployments/rest/log

cloud_controller : STOPPED

redis_gateway : STOPPED

health_manager : STOPPED

redis_node : STOPPED

router : STOPPED

mongodb_gateway : STOPPED

mongodb_node : STOPPED

mysql_gateway : STOPPED

cloud_controller : RUNNING

redis_gateway : STOPPED

LOG:

/root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/spec_set.rb:90:in `block in materialize': Could not find beefcake-0.3.7 in any of the sources (Bundler::GemNotFound)

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/spec_set.rb:83:in `map!'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/spec_set.rb:83:in `materialize'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/definition.rb:127:in `specs'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/definition.rb:172:in `specs_for'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/definition.rb:161:in `requested_specs'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/environment.rb:23:in `requested_specs'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/runtime.rb:11:in `setup'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler.rb:107:in `setup'

from /root/cloudfoundry/.deployments/rest/deploy/rubies/ruby-1.9.2-p180/lib/ruby/gems/1.9.1/gems/bundler-1.1.3/lib/bundler/setup.rb:17:in `<top (required)>'

from <internal:lib/rubygems/custom_require>:33:in `require'

from <internal:lib/rubygems/custom_require>:33:in `rescue in require'

from <internal:lib/rubygems/custom_require>:29:in `require'

from /root/cloudfoundry/vcap/bin/../services/redis/bin/redis_gateway:5:in `<main>'