Hi,

I just installed CF V2 with the nice installer (no errors) and when using cf I get the following error when trying to log in: CFoundry::NotFound: :

Output of cf login with options "-t" and "-v" below. The login failed as subsequent commands ask me to login first.

Does anybody know what might be off?

For background, I installed and tried all versions of cf starting with 4.2.8 (5.2.0, 5.2.2, 5.3.0, 5.3.1) and none of them worked.

Thanks,

Christoph

192:tmp christoph$ cf login --password c1oudc0w admin -t -v
target: http://api.172.16.227.102.xip.io

>>>
REQUEST: GET http://api.172.16.227.102.xip.io/info
REQUEST_HEADERS:
  Accept : application/json
  Content-Length : 0
RESPONSE: [200]
RESPONSE_HEADERS:
  content-length : 270
  content-type : application/json;charset=utf-8
  date : Fri, 27 Sep 2013 18:15:00 GMT
  server : nginx
  x-content-type-options : nosniff
  x-vcap-request-id : 0b2141b3-0ee9-407a-bf41-a6d60f222f91
RESPONSE_BODY:
{
  "name": "vcap",
  "build": "2222",
  "support": "http://support.cloudfoundry.com",
  "version": 2,
  "description": "Cloud Foundry sponsored by Pivotal",
  "authorization_endpoint": "http://login.172.16.227.102.xip.io",
  "token_endpoint": "http://uaa.172.16.227.102.xip.io",
  "allow_debug": true
}
<<<
CFoundry::NotFound: : 
192:tmp christoph$ 

Cannot get either the standard or with-services versions to deploy on a clean Ubuntu x64 10.04 VM.

It looks like there have been changes to repositories linked to cf-release, such as gorouter, which are not included in the services snapshot, and are no longer compatible with your manifest.

Seems related to the p("x") helpers, job 'micro' fails, they added more? :/
http://grokbase.com/p/cloudfoundry.org/vcap-dev/136bfq5zfv/script-which-jobs-using-new-p-x-y-z-helpers-and-which-arent

Quoted from Dr Nic from that thread:
Doh, sorry this seems to give the correct (shorter) list:

$ grep '^properties:' jobs/*/spec | awk '{print $1}' | cut -d / -f 2 | uniq
cloud_controller_ng
gorouter

To summarize: these two jobs can be colocated; but I think not with any
other job today. Or something like that.

My current results:
grep '^properties:' jobs/*/spec | awk '{print $1}' | cut -d / -f 2 | uniq
cloud_controller_ng
collector
dea_next
gorouter
health_manager_next
login
nats
saml_login
syslog_aggregator
uaa

I have installed the branch of service-combined, when I start all processes, some processes start abnormally:

Execution failed: mysql_worker_0, postgresql_worker_0
Does not exist:warden, dea_next ("initializing" -> "does not exist" loop....)
sometimes running, sometimes does not exist: mysql_gateway, postgresql_gateway

thanks for help

Hey,

i managed to get a vm with a release running. I used the vagrant approach to achieve this.

I'm able to login, create orgs, spaces, services, ... but when if deploy a rails application and try running my migrations from within the console it fails. The application is not able to acces the database node.

When i logged in to the database service by using the mysql command line client with the credentials within DATABASE_URL retrieved from the "cf logs" command i was able to acces the database and verify it's existence. So the binding and provisioning processes are working properly. But my app can't access the database.

Do you have any ideas regarding this topic? Did you manage to get an application running that's using a mysql or postgresql database?

Regards,
Julian

I can't find the warden.sock in "/var/vcap/data/warden/", so the warden component can't be started.

Anyone can help me?

I am using cf_nise_installer trying to install CF on my ubuntu 12.04 LTS. But the script stopped when it try to build nginx.

gcc -c -pipe -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Wunused-function -Wunused-variable -Wunused-value -Werror -g -DNDK_SET_VAR -I src/core -I src/event -I src/event/modules -I src/os/unix -I ../simpl-ngx_devel_kit-bc97eea/objs -I objs/addon/ndk -I /var/vcap/packages/nginx/lua/include -I ../pcre-8.12 -I objs
-o objs/src/core/ngx_resolver.o
src/core/ngx_resolver.c
src/core/ngx_resolver.c: In function ‘ngx_resolver_process_ptr’:
src/core/ngx_resolver.c:1425:43: error: variable ‘qclass’ set but not used [-Werror=unused-but-set-variable]
src/core/ngx_resolver.c:1425:36: error: variable ‘qtype’ set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
make[1]: *** [objs/src/core/ngx_resolver.o] Error 1
make[1]: Leaving directory `/var/vcap/data/compile/nginx/nginx-0.8.54'
make: *** [build] Error 2

How can I suppress this build error: "all warnings being treated as errors"?

Newbie question - I guess I need to use vagrant to set-up a VirtualBox virtual machine using nise-bosh-vagrant first, then issue the curl command on the virtual machine.

So ... what options do I give the command :
nise-bosh-vagrant --manifest
how do I access a bosh release ? which one ? do I need to have downloaded some nise-bosh code, or point at a remote machine, or issue a command ? and where does the manifest come from (is it packaged with a bosh release) ?

Thanks.

Hi yudai,

Last week, I successfully built a devbox on a single server. However there is no mongodb service after all processes launched.

Then I found that there were no mongodb entries in the template section in the micro.yml file. I added

• mongodb_node_ng
• mongodb_gateway
  to the micro.yml file and did a update. But the mongodb service is still not available.

Please help. Thanks.

Below is the monit summary after I added mongodb, and you can see the status for mongodb related processes is "not monitored"

Process 'postgres' running
Process 'nats' running
Process 'warden' running
Process 'dea_next' running
Process 'dir_server' running
Process 'health_manager_next' running
Process 'serialization_data_server' running
Process 'uaa' running
Process 'vcap_registrar' running
Process 'vcap_redis' running
Process 'mysql55' running
Process 'mysql_node' running
Process 'mysql_worker_0' running
Process 'mysql_worker_1' running
Process 'mysql_worker_2' running
Process 'mysql_worker_3' running
Process 'mysql_worker_4' running
Process 'mysql_gateway' Does not exist
Process 'mongodb_warden' not monitored
Process 'mongodb_node' not monitored
Process 'mongodb_worker_0' not monitored
Process 'mongodb_worker_1' not monitored
Process 'mongodb_worker_2' not monitored
Process 'mongodb_worker_3' not monitored
Process 'mongodb_worker_4' not monitored
Process 'mongodb_gateway' Does not exist
Process 'cloud_controller_ng' Does not exist
Process 'postgresql91' running
Process 'postgresql_node' running
Process 'postgresql_worker_0' running
Process 'postgresql_worker_1' running
Process 'postgresql_worker_2' running
Process 'postgresql_worker_3' running
Process 'postgresql_worker_4' running
Process 'gorouter' running
Process 'postgresql_gateway' Does not exist
System 'system_cf-server' running

When executing cf push for a Rails test app, I get the below error. This corresponds to something I I got earlier when trying to login using the cf login --password c1oudc0w admin command.

SocketError: getaddrinfo: Name or service not known

/home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:763:in initialize' /home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:763:inopen'
/home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:763:in block in connect' /home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/timeout.rb:55:intimeout'
/home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/timeout.rb:100:in timeout' /home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:763:inconnect'
/home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:756:in do_start' /home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:745:instart'
/home/opstack/.rvm/rubies/ruby-1.9.3-p448/lib/ruby/1.9.1/net/http.rb:557:in start' cfoundry-4.3.5.rc1/lib/cfoundry/baseclient.rb:110:instream_url'
cfoundry-4.3.5.rc1/lib/cfoundry/v2/client.rb:82:in stream_url' cf-5.2.2/lib/cf/cli/app/start.rb:55:instream_start_log'
cf-5.2.2/lib/cf/cli/app/start.rb:28:in block in start' cf-5.2.2/lib/cf/spacing.rb:40:inblock in spaced'
cf-5.2.2/lib/cf/spacing.rb:38:in each' cf-5.2.2/lib/cf/spacing.rb:38:inspaced'
cf-5.2.2/lib/cf/cli/app/start.rb:17:in start' mothership-0.5.1/lib/mothership/base.rb:66:inrun'
mothership-0.5.1/lib/mothership/command.rb:72:in block in invoke' cf-5.2.2/lib/manifests/plugin.rb:44:incall'
cf-5.2.2/lib/manifests/plugin.rb:44:in wrap_with_optional_name' cf-5.2.2/lib/manifests/plugin.rb:11:inblock in default_to_app_from_manifest'
mothership-0.5.1/lib/mothership/command.rb:82:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:82:inblock (2 levels) in invoke'
mothership-0.5.1/lib/mothership/command.rb:86:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:86:ininvoke'
mothership-0.5.1/lib/mothership/base.rb:73:in invoke' cf-5.2.2/lib/cf/cli/app/push/create.rb:91:instart_app'
cf-5.2.2/lib/cf/cli/app/push.rb:59:in setup_new_app' cf-5.2.2/lib/cf/cli/app/push.rb:48:inpush'
mothership-0.5.1/lib/mothership/base.rb:66:in run' mothership-0.5.1/lib/mothership/command.rb:72:inblock in invoke'
cf-5.2.2/lib/manifests/plugin.rb:108:in call' cf-5.2.2/lib/manifests/plugin.rb:108:inblock in push_with_manifest'
mothership-0.5.1/lib/mothership/callbacks.rb:74:in with_filters' cf-5.2.2/lib/manifests/plugin.rb:105:inpush_with_manifest'
cf-5.2.2/lib/manifests/plugin.rb:90:in block in wrap_push' cf-5.2.2/lib/cf/spacing.rb:40:inblock in spaced'
cf-5.2.2/lib/cf/spacing.rb:38:in each' cf-5.2.2/lib/cf/spacing.rb:38:inspaced'
cf-5.2.2/lib/manifests/plugin.rb:89:in wrap_push' cf-5.2.2/lib/manifests/plugin.rb:25:inblock in class:ManifestsPlugin'
mothership-0.5.1/lib/mothership/command.rb:82:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:82:inblock (2 levels) in invoke'
mothership-0.5.1/lib/mothership/command.rb:86:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:86:ininvoke'
mothership-0.5.1/lib/mothership/base.rb:55:in execute' cf-5.2.2/lib/cf/cli.rb:195:inblock (2 levels) in execute'
cf-5.2.2/lib/cf/cli.rb:206:in save_token_if_it_changes' cf-5.2.2/lib/cf/cli.rb:194:inblock in execute'
cf-5.2.2/lib/cf/cli.rb:123:in wrap_errors' cf-5.2.2/lib/cf/cli.rb:190:inexecute'
mothership-0.5.1/lib/mothership.rb:45:in start' cf-5.2.2/bin/cf:18:in<top (required)>'
ruby-1.9.3-p448/bin/cf:19:in load' ruby-1.9.3-p448/bin/cf:19:in

I just installed CF V2 with the nice installer (no errors) and when using cf I get the following error when trying to log in: CFoundry::NotFound: :

Someone mentioned this question 2 months ago, but now I repeat install a few problems still exist.
The installation is 5.0.4 cf version.
I hope you can help me to take a look at this error, thank you!

remote@i-326-32007-VM:~/cf_nise_installer$ cf login --password cloudc0w admin -t -v
target: http://api.172.16.19.36.xip.io

REQUEST: GET http://api.172.16.19.36.xip.io/info
REQUEST_HEADERS:
Accept : application/json
Content-Length : 0
RESPONSE: [200]
RESPONSE_HEADERS:
content-length : 264
content-type : application/json;charset=utf-8
date : Fri, 06 Dec 2013 06:48:03 GMT
server : nginx
x-content-type-options : nosniff
x-vcap-request-id : 335475e4-3986-41a7-8788-a94762e1d264
RESPONSE_BODY:
{
"name": "vcap",
"build": "2222",
"support": "http://support.cloudfoundry.com",
"version": 2,
"description": "Cloud Foundry sponsored by Pivotal",
"authorization_endpoint": "http://uaa.172.16.19.36.xip.io",
"token_endpoint": "http://uaa.172.16.19.36.xip.io",
"allow_debug": true
}
<<<
CFoundry::NotFound: :

View the cf version is as follows:
remote@i-326-32007-VM:~/cf_nise_installer$ cf -v
cf 5.4.4

See the error log information is as follows:
remote@i-326-32007-VM:~/.cf$ cat crash
Time of crash:
2013-12-06 14:48:03 +0800

CFoundry::NotFound: :

<<<

cfoundry-4.7.1.rc1/lib/cfoundry/uaaclient.rb:153:in rescue in wrap_uaa_errors' cfoundry-4.7.1.rc1/lib/cfoundry/uaaclient.rb:149:inwrap_uaa_errors'
cfoundry-4.7.1.rc1/lib/cfoundry/uaaclient.rb:17:in prompts' cfoundry-4.7.1.rc1/lib/cfoundry/concerns/login_helpers.rb:6:inlogin_prompts'
cf-5.4.4/lib/cf/cli/start/login.rb:35:in login' mothership-0.5.1/lib/mothership/base.rb:66:inrun'
mothership-0.5.1/lib/mothership/command.rb:72:in block in invoke' mothership-0.5.1/lib/mothership/command.rb:86:ininstance_exec'
mothership-0.5.1/lib/mothership/command.rb:86:in invoke' mothership-0.5.1/lib/mothership/base.rb:55:inexecute'
cf-5.4.4/lib/cf/cli.rb:195:in block (2 levels) in execute' cf-5.4.4/lib/cf/cli.rb:202:insave_token_if_it_changes'
cf-5.4.4/lib/cf/cli.rb:194:in block in execute' cf-5.4.4/lib/cf/cli.rb:123:inwrap_errors'
cf-5.4.4/lib/cf/cli.rb:190:in execute' mothership-0.5.1/lib/mothership.rb:45:instart'
cf-5.4.4/bin/cf:18:in <top (required)>' /home/remote/.rbenv/versions/1.9.3-p448/bin/cf:23:inload'
/home/remote/.rbenv/versions/1.9.3-p448/bin/cf:23:in `

Hi,

when installing the first time, I find this:

--- FAIL: TestLookupHost (0.00 seconds)
hosts_test.go:65: LookupHost("localhost") = [127.0.0.1 127.0.0.1 ::1], has duplicate addresses
FAIL
FAIL net 2.235s

Hi,

I have installed cf_nise_installer by following the steps under Building Devbox on Single Server. It is installed successfully.

Services status:
root@cfoundry2211:~# /var/vcap/bosh/bin/monit summary
The Monit daemon 5.2.4 uptime: 3h 41m

Process 'nats' running
Process 'warden' Does not exist
Process 'dea_next' initializing
Process 'dir_server' running
Process 'health_manager_next' running
Process 'uaa' running
Process 'uaa_cf-registrar' running
Process 'login' running
Process 'login_cf-registrar' running
Process 'collector' running
Process 'cloud_controller_ng' running
Process 'gorouter' running
Process 'postgres' running
System 'system_cfoundry2211' running

i'm able to ping the host api..xip.ioThen i've issue

the command

root@cfoundry2211:~/cf_nise_installer# cf target 'api..xip.io'
Errno::ETIMEDOUT: Connection timed out - connect(2)
For more information, see ~/.cf/crash

Gems for reference:
activemodel (3.2.13)
activesupport (3.2.14, 3.2.13)
addressable (2.3.5)
admin-cf-plugin (3.0.0)
aws-sdk (1.8.5)
bcrypt-ruby (3.0.1)
bigdecimal (1.1.0)
builder (3.1.4, 3.0.4)bundler (1.3.5)
caldecott-client (0.0.2)
cf (3.0.0)
cf-uaa-lib (1.3.10)
cfoundry (2.4.0)
crack (0.3.2)

Please find the remaining gems in the attachment

Please help me in solving this issue

Thanks,
Sasikiran

I'm trying to boot up a Vagrant devobox using your script, and I'm running into an issue during installation.

nise-bosh-vagrant ./cf-release --manifest ./manifests/deploy.yml --memory 4096 --postinstall ./vagrant/postinstall.sh --install
./vagrant/launch_nise_bosh.sh: line 13: nise-bosh-vagrant: command not found

I've checked the console output and the script, and they both confirm that the nise-bosh-vagrant gem is being installed, so I'm a bit stumped as to why this isn't working. Any help would be appreciated.

I've had good success with cf_nise_installer on a local virtual machine where the external IP and the internal IP are the same. I'm trying now to use cf_nise_installer on an AWS EC2 instance in which there is a firewall between my instance and the Internet and the public (external-facing) IP address is different from the private (internal-facing) IP address.

Question: Is there an appropriate modification to some configuration file to support this? It looks like NISE_IP_ADDRESS is used for both. Or is this a question for the CF list? Thanks!

Hello yudai.

I tried to install CloudFoundry V2 using your installer.
But, following error occurred. Do you know about this error?

I show the appropriate section of installing log. I tried to install twice. Same error ocdurred.
( If needed, I will show you all of install log. )

Using director (1.5.0.pre.3) from https://github.com/cloudfoundry/bosh.git (at master)
Using rspec-core (2.13.1)
Using rspec-expectations (2.13.0)
Using rspec-mocks (2.13.1)
Using rspec (2.13.0)
Using bundler (1.3.5)
Your bundle is complete!
Use `bundle show [gemname]` to see where a bundled gem is installed.
+ sudo env     PATH=/home/suda/.rbenv/bin:/home/suda/.rbenv/shims:/home/suda/.rbenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games bundle exec ./bin/nise-bosh -y ../cf-release ../manifests/deploy.yml micro
The following templates and packages for job micro will be installed.
    # postgres
Archive file for postgres not found in /home/suda/cf_nise_installer/cf-release/.final_builds/jobs/postgres/3.tgz.

Environment:

• Ubuntu Server 10.04 (64bit) on VMWare Fusion 5.0
• 6GB RAM, 20GB HDD, 4 CPU

Having an issue staging some kinds of projects, your simple hello world example works fine, but trying the equivalent with a Grails application using a build-pack doesn't work so well. It compiles everything correctly, but fails to stage. Here's the DEA log

{"timestamp":1374191611.850716,"message":"Caught exception: Error uploading: http://removed:[email protected]:9022/staging/droplets/470964f4-9f7d-492c-8556-8d860160eba7/upload (HTTP status: 400 - {"code":170001,"description":"Staging error: staging not in progress for 470964f4-9f7d-492c-8556-8d860160eba7"}\n)","log_level":"warn","source":"Dea::Promise","data":{"backtrace":["/var/vcap/packages/dea_next/lib/dea/promise.rb:69:in resolve'","/var/vcap/packages/dea_next/lib/dea/promise.rb:35:ineach'","/var/vcap/packages/dea_next/lib/dea/promise.rb:35:in run_serially'","/var/vcap/packages/dea_next/lib/dea/staging_task.rb:413:inresolve_staging'","/var/vcap/packages/dea_next/lib/dea/staging_task.rb:49:in block in start'","/var/vcap/packages/dea_next/lib/dea/promise.rb:80:incall'","/var/vcap/packages/dea_next/lib/dea/promise.rb:80:in `block in run'"]},"thread_id":6205580,"fiber_id":13176480,"process_id":2526,"file":"/var/vcap/packages/dea_next/lib/dea/promise.rb","lineno":22,"method":"rescue in block in resolve"}
{"timestamp":1374191619.351904,"message":"varz access","log_level":"debug","source":"Dea::Bootstrap","data":{},"thread_id":6205580,"fiber_id":10743480,"process_id":2526,"file":"/var/vcap/packages/dea_next/vendor/bundle/ruby/1.9.1/gems/vcap_common-2.0.11/lib/vcap/component.rb","lineno":22,"method":"call"}
{"timestamp":1374191619.37618,"message":"healthz access","log_level":"debug","source":"Dea::Bootstrap","data":{},"thread_id":6205580,"fiber_id":10743480,"process_id":2526,"file":"/var/vcap/packages/dea_next/vendor/bundle/ruby/1.9.1/gems/vcap_common-2.0.11/lib/vcap/component.rb","lineno":37,"method":"call"}

Continuing to debug by myself as I'm not sure this is related at all to your installer, the only thing that makes me think it is, is this thread:
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/niObry183ho

Where someone gives a cryptic answer of "there was a HM and CC fixes that have gone in to master in the last day." (a month ago)

I faced this error during "cf login" first. Devbox IP address is 192.168.0.111, but name "uaa.192.168.0.11.xip.io" was not resolved. Fixed this by adding "uaa.192.168.0.11.xip.io" to /etc/hosts and mapping to localhost. But when I try to push my application I face this error again. I've set up dnsmasq to forward all request to "*.192.168.0.11.xip.io" to localhost, but it did not help. Any ideas appreciated. Error log:

<<<
Preparing to start Services>>>.
REQUEST: PUT http://api.192.168.0.111.xip.io/v2/apps/825c52ae-12ff-4301-9eae-8863a77f40d1
REQUEST_HEADERS:
Authorization : PRIVATE DATA HIDDEN
Content-Length : 34
Content-Type : application/json
REQUEST_BODY:
{"console":true,"state":"STARTED"}

. RESPONSE: 201
RESPONSE_HEADERS:
content-length : 1247
content-type : application/json;charset=utf-8
date : Thu, 31 Oct 2013 11:00:47 GMT
server : nginx
x-app-staging-log : http://5d9375ae0160f90d1970a49ccddf4f85.192.168.0.111.xip.io/staging_tasks/fe806fa3d4ca45b495ad2a904f6851a7/file_path?hmac=fb6d6be5f4c0f82113945adc1b2eb14ab65ccbb0b8b7fd76badf2fefe3805d153777e29674f4893741b48d09851ada8f17725fb03b6ca1ffb5cbf1cb2874a29b&path=%2Ftmp%2Fstaged%2Flogs%2Fstaging_task.log&timestamp=1383217247
x-content-type-options : nosniff
x-vcap-request-id : 11b43677-a2f3-49a7-a050-9eaa75f6ce47
RESPONSE_BODY:
{
"metadata":
{ "guid": "825c52ae-12ff-4301-9eae-8863a77f40d1", "url": "/v2/apps/825c52ae-12ff-4301-9eae-8863a77f40d1", "created_at": "2013-10-30T16:28:56+03:00", "updated_at": "2013-10-31T14:00:45+03:00" }

,
"entity": {
"name": "Services",
"production": false,
"space_guid": "79d5666b-c5f5-48b3-ba5f-cfd8a24362b5",
"stack_guid": "55608c92-6301-4cac-9638-74fe59b76760",
"buildpack": null,
"detected_buildpack": "openjdk-1.7.0_45, spring-auto-reconfiguration-0.7.2, tomcat-7.0.47, tomcat-buildpack-support-1.1.1",
"environment_json": {
},
"memory": 512,
"instances": 1,
"disk_quota": 1024,
"state": "STARTED",
"version": "3404d518-6384-42bc-8d64-a7e79b43f6c9",
"command": null,
"console": true,
"debug": null,
"staging_task_id": "fe806fa3d4ca45b495ad2a904f6851a7",
"space_url": "/v2/spaces/79d5666b-c5f5-48b3-ba5f-cfd8a24362b5",
"stack_url": "/v2/stacks/55608c92-6301-4cac-9638-74fe59b76760",
"service_bindings_url": "/v2/apps/825c52ae-12ff-4301-9eae-8863a77f40d1/service_bindings",
"routes_url": "/v2/apps/825c52ae-12ff-4301-9eae-8863a77f40d1/routes",
"events_url": "/v2/apps/825c52ae-12ff-4301-9eae-8863a77f40d1/events"
}
}
<<< ... OK
Time of crash:
2013-10-31 14:00:47 +0300

SocketError: getaddrinfo: Name or service not known

/home/test/.rbenv/versions/1.9.3-p448/lib/ruby/1.9.1/net/http.rb:763:in `initialize'

Hi,

after the installation of CF with NICE went fine, I tried to push a node.js application. I am getting this error:

CFoundry::StackNotFound: 250003: The stack could not be found: The requested app stack lucid64 is not available on this system.

The manifest file looks like this:

---
applications:
- name: foo
  memory: 256M
  instances: 1
  host: foo
  domain: amecheapp.com
  path: .
  command: node index.js
  buildpack: https://github.com/cloudfoundry/heroku-buildpack-nodejs.git

I tried a lot of variations (like not defining a build pack, or use the original domain after installation, installing node manually on the CF system, etc.), but every time I am getting above error.

When asking for the logs, I get this:

192:foo christoph$ cf logs foo
Using manifest file manifest.yml

CFoundry::NotStaged: 170002: App has not finished staging
192:foo christoph$ 

Does anybody have an idea/hunch what the error could be? I'll dig more into logs, but maybe somebody came across this situation before.

Thanks,

Christoph

When running the ./local/start_processes.sh script on Ubuntu Server 10.04 64 bit, the following error message is being displayed:

sudo /var/vcap/bosh/bin/monit start nats
monit: action failed -- There is no service by that name

I have a working installation that's accessible via the *.xip.io domain. I've exported the NISE_DOMAIN variable and re-ran the update section (i.e. launch_nise_bosh), etc. When I start Cloud Foundry again, I'm not able to set my cf target to the new domain name, I get:

$ cf target api.foundry
Setting target to http://api.foundry... FAILED
Target refused connection.

I've also tried a fresh install with the NISE_DOMAIN variable set, but it doesn't seem to have been picked up. Would love to have CF running on an internal domain. Thanks!

After following instructions provided on https://github.com/yudai/cf_nise_installer/tree/snapshot-ea61ec6f8f to install the CF_NG, I am unable ot login.

cf login [email protected] -t results in

  2013-09-03 10:27:40 -0400

CFoundry::BadResponse: :
cfoundry-4.3.6/lib/cfoundry/uaaclient.rb:151:in `rescue in wrap_uaa_errors'
cfoundry-4.3.6/lib/cfoundry/uaaclient.rb:149:in `wrap_uaa_errors'
cfoundry-4.3.6/lib/cfoundry/uaaclient.rb:17:in `prompts'
cfoundry-4.3.6/lib/cfoundry/concerns/login_helpers.rb:6:in `login_prompts'
cf-5.2.0/lib/cf/cli/start/login.rb:35:in `login'
mothership-0.5.1/lib/mothership/base.rb:66:in `run'
mothership-0.5.1/lib/mothership/command.rb:72:in `block in invoke'
mothership-0.5.1/lib/mothership/command.rb:86:in `instance_exec'
mothership-0.5.1/lib/mothership/command.rb:86:in `invoke'
mothership-0.5.1/lib/mothership/base.rb:55:in `execute'
cf-5.2.0/lib/cf/cli.rb:187:in `block (2 levels) in execute'
cf-5.2.0/lib/cf/cli.rb:194:in `save_token_if_it_changes'
cf-5.2.0/lib/cf/cli.rb:186:in `block in execute'
cf-5.2.0/lib/cf/cli.rb:122:in `wrap_errors'
cf-5.2.0/lib/cf/cli.rb:182:in `execute'
mothership-0.5.1/lib/mothership.rb:45:in `start'
cf-5.2.0/bin/cf:16:in `<top (required)>'
/home/virtuser/.rbenv/versions/1.9.3-p448/bin/cf:23:in `load'
/home/virtuser/.rbenv/versions/1.9.3-p448/bin/cf:23:in `<main>'

Looking at the monit summary I see this ..
Process 'uaa'
status Execution failed
monitoring status monitored
data collected Tue Sep 3 10:39:38 2013

In the /var/vcap/data/sys/log/monit/uaa_ctl_err.log I see

/var/vcap/packages/uaa/jre/bin/java: 1: Syntax error: "(" unexpected
/var/vcap/packages/uaa/jre/bin/java: 1: Syntax error: "(" unexpected
/var/vcap/packages/uaa/jre/bin/java: 1: Syntax error: "(" unexpected

When I run the postinstall.sh script, I get the following:

./local/postinstall.sh
+ ./common/postinstall.sh
+ sudo sed -i 's/check process vcap_registrar/check process vcap_registrar_login/' /var/vcap/monit/job/0001_micro.login.monitrc
sed: can't read /var/vcap/monit/job/0001_micro.login.monitrc: No such file or directory

It looks like no monit jobs where installed during the install process. This is an Ubuntu 10.04.4 box. Thanks!

I've successfully installed all of the CF components using the script, but when I try and launch the uaa and login pieces fail to execute. The cf-registrar.log file for both jobs outputs the error "Could not register nil varz credentials". I believe I have traced this to an error being thrown by
/var/vcap/data/packages/uaa/28/vcap-common/lib/cf/registrar.rb (or ../packages/login/..)
It seems to be unable to read the script-generated username and password located in
/var/vcap/jobs/uaa/config/varz.yml (or ../jobs/login/..)
and I can't seem to figure out why. The file is present and the values are there. Inserting a check in the .rb file confirms that the values are being read in as nil, thus failing the check. I've tried setting the values manually but I'm not sure it's having an effect. Not sure where to go from here.

When installing the vagrant devbox, I'm getting

./vagrant/launch_nise_bosh.sh: line 23: nise-bosh-vagrant: command not found

I suppose install.sh should include this gem as well.

Not sure if this is an issue with the installer or the core that is being installed. Workaround is pretty easy:
sudo rm -rf /var/vcap/packages/uaa/jdk

Following is tail of output:

[4853] INFO: Resolving package dependencies...

[4853] INFO: Installing the following packages:

[4853] INFO: * common

[4853] INFO: * libyaml

[4853] INFO: * ruby

[4853] INFO: * nats

[4853] INFO: * health_manager_next

[4853] INFO: * syslog_aggregator

[4853] INFO: * uaa

[4853] INFO: * libpq

[4853] INFO: * mysqlclient

[4853] INFO: * sqlite

[4853] INFO: * cloud_controller_ng

[4853] INFO: * nginx

[4853] INFO: * golang

[4853] INFO: * gorouter

[4853] INFO: * buildpack_cache

[4853] INFO: * insight_agent

[4853] INFO: * dea_next

[4853] INFO: * warden

[4853] INFO: * rootfs_lucid64

[4853] INFO: * git

[4853] INFO: Installing package common

[4853] INFO: The same version of the package is already installed. Skipping

[4853] INFO: Installing package libyaml

[4853] INFO: The same version of the package is already installed. Skipping

[4853] INFO: Installing package ruby

[4853] INFO: The same version of the package is already installed. Skipping

[4853] INFO: Installing package nats

[4853] INFO: The same version of the package is already installed. Skipping

[4853] INFO: Installing package health_manager_next

[4853] INFO: The same version of the package is already installed. Skipping

[4853] INFO: Installing package syslog_aggregator

[4853] INFO: The same version of the package is already installed. Skipping

[4853] INFO: Installing package uaa

[4853] INFO: Running the packaging script for uaa

[4853] INFO: An error occurred while compiling uaa

[4853] INFO: + set -e

• cd /var/vcap/packages/uaa
• mkdir jdk
  mkdir: cannot create directory `jdk': File exists
• [[ 1 != 0 ]]
• echo 'Cannot unpack JDK'
  Cannot unpack JDK
• exit 1

/home/ubuntu/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:206:in block in compile': Compile Package Failure (exit code: 1) (Bosh::Agent::MessageHandlerError) from /home/ubuntu/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:190:inchdir'
from /home/ubuntu/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:190:in compile' from /home/ubuntu/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:64:instart'
from /home/ubuntu/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:31:in process' from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:215:inrun_packaging'
from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:203:in install_package' from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:191:inblock in install_packages'
from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in each' from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:ininstall_packages'
from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:263:in install_job' from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:101:inrun_default_mode'
from /home/ubuntu/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:65:in run' from ./bin/nise-bosh:4:in

We have the ability to override the IP and the domain and this is very helpful. One of the requirements for creating an Amazon AMI that is distributed to the public is that it not contain a default password. Right now the manifest is automatically modified to replace '196.168.10.10' with the real IP. It would be helpful if a similar replacement could be made for 'c1oudc0w' based on an optional environment variable (say, NISE_PASSWORD).

On a new Ubuntu 10.04.3 64-bit server, I entered the following:

export CF_RELEASE_BRANCH=release-candidate
bash < <(curl -s -k -B https://raw.github.com/yudai/cf_nise_installer/master/local/bootstrap.sh)

After about 15 minutes, just after a TZinfo note, I got the following:

+ sudo env PATH=[...] bundle exec ./bin/nise-bosh -y ../cf-release ../manifests/deploy.yml micro
Faild to load release file!

Any suggestions?

I've install cf_nise_installer and services in two VMs and all processes are running,
when I run "cf create-service", I got this error message:

... FAILED
CFoundry::ServerError: 10001: Service broker error: Gateway timeout

I've create-service-auth-token successfully and see the current profile when create-service, thanks for help

Given the current notice on stability, it would be helpful to mention that the scripts check out the cf-release master branch whereas the branch "release-candidate" is guaranteed to be stable.

I get this error when running bootstrap.sh. Seems like it fails when compiling nginx:

gcc -c -pipe  -O -W -Wall -Wpointer-arith -Wno-unused-parameter -Wunused-function -Wunused-variable -Wunused-value -Werror -g  -DNDK_SET_VAR -I src/core -I src/event -I src/event/modules -I src/os/unix -I ../simpl-ngx_devel_kit-bc97eea/objs -I objs/addon/ndk -I /var/vcap/packages/nginx/lua/include -I ../pcre-8.12 -I objs \
                -o objs/src/core/ngx_resolver.o \
                src/core/ngx_resolver.c
src/core/ngx_resolver.c: In function ‘ngx_resolver_process_ptr’:
src/core/ngx_resolver.c:1425:43: error: variable ‘qclass’ set but not used [-Werror=unused-but-set-variable]
src/core/ngx_resolver.c:1425:36: error: variable ‘qtype’ set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
make[1]: *** [objs/src/core/ngx_resolver.o] Error 1
make[1]: Leaving directory `/var/vcap/data/compile/nginx/nginx-0.8.54'
make: *** [build] Error 2

/home/user1/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:210:in `block in compile': Compile Package Failure (exit code: 1) (Bosh::Agent::MessageHandlerError)
        from /home/user1/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:193:in `chdir'
        from /home/user1/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:193:in `compile'
        from /home/user1/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:66:in `start'
        from /home/user1/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:31:in `process'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:215:in `run_packaging'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:203:in `install_package'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:191:in `block in install_packages'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in `each'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in `install_packages'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:263:in `install_job'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:101:in `run_default_mode'
        from /home/user1/cf_nise_installer/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:65:in `run'
        from ./bin/nise-bosh:4:in `<main>'

Please help! :-)

Hi, I've used cf_nise_installer to install Cloud Foundry V2 to Ubuntu Server 10.04. It was really cool and smooth experience,I've got my Controller running and was able to connect using CF tool. (There were no default spaces/domains installed so I had to create some to deploy simple node.js app - hope this is not an issue).

But when I've decided to run some services, I didn't found any of them. Running cf gave following

cf create-service
DL is deprecated, please use Fiddle
Cannot find services matching the given criteria.

So I suppose there were no services installed. According to README I had to run register_service_tokens.sh script to install those, but I could not find it in source (browsing the commit history showed that it was deleted).
So what can I do to have any service provisioned? And also it seems README file needs some updates.

Hi Yudai,
I've installed CFv2 and all process stated running, but when I use cf target , it always says "Target refused connection".
In browser, open CF url and display; "{"code":10000,"description":"Unknown request"}", is it normal?
By the way, if I want to disable xip and use custom host like older vcap, how can I do this job?
Thanks a lot :)

Hi, this is more of a newbie question. I installed CF as instructed (On Ubuntu DevBox without Vagrant), and logged into uaa.x.x.x.x.xip.io - the login was successful. What do I explore next to get started with using CloudFoundry and custommizing it? I found quite lot of material which is either confusing or not guided well enough. Appreciate your time and help.

Hi yudai,

As the title, and so the following script will run into errors:
"
f [ ! -d ~/.rbenv ]; then
git clone https://github.com/sstephenson/rbenv.git ~/.rbenv
git clone https://github.com/sstephenson/ruby-build.git ~/.rbenv/plugins/ruby-build
echo 'export PATH="$HOME/.rbenv/bin:$PATH"' >> ~/.bash_profile
echo 'eval "$(rbenv init -)"' >> ~/.bash_profile
fi
. ~/.bash_profile
"

When installing on Ubuntu 10.04.4 64 bit server, I'm encountering the following error when executing "sudo apt-get -y install git":
WARNING: The following packages cannot be authenticated!
git-core git-man git
E: There are problems and -y was used without --force-yes

The script seems to be aborting when attempting to install "python-pycurl python-software-properties unattended-upgrades" on Ubuntu 10.04 64 bit server.

This may be caused by the script expecting the user to confirm Y/n as part of the operation.

The output I'm seeing is:

sudo apt-get install python-software-properties
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
python-pycurl unattended-upgrades
Suggested packages:
libcurl4-gnutls-dev python-pycurl-dbg bsd-mailx
The following NEW packages will be installed:
python-pycurl python-software-properties unattended-upgrades
0 upgraded, 3 newly installed, 0 to remove and 71 not upgraded.
Need to get 113kB of archives.
After this operation, 1,667kB of additional disk space will be used.
Do you want to continue [Y/n]? Abort.

I ran the installer, but it failed due to a lack of disk space. I sorted the space issue, but I am unable to get the installer to run through again. I have been trying to clean up what was done before by deleting the cf_nise_installer directory, but the bootstrap.sh scripts ends after just a few minutes. What things do I need to clean up in order to start from a pristine state?

Hi,

when installing the fist time, after the phase 'Testing packages.', I get the following error:

/home/christoph/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:206:in block in compile': Compile Package Failure (exit code: 1) (Bosh::Agent::MessageHandlerError) from /home/christoph/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:190:inchdir'
from /home/christoph/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:190:in compile' from /home/christoph/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:64:instart'
from /home/christoph/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-fbb73b1d320c/bosh_agent/lib/bosh_agent/message/compile_package.rb:31:in process' from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:215:inrun_packaging'
from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:203:in install_package' from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:191:inblock in install_packages'
from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in each' from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:ininstall_packages'
from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:263:in install_job' from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:101:inrun_default_mode'
from /home/christoph/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:65:in run' from ./bin/nise-bosh:4:in

Doing an install with
export NISE_IP_ADDRESS='127.0.0.1'
results in 24 lines with the expected address and five lines with the local (incorrect) IP.

ubuntu@ip-172-31-21-219:~$ sudo find /var/vcap -type f ( -iname '*.yml' -o -iname 'postgres_ctl' ) | sudo xargs grep 172.31.21.219
/var/vcap/data/jobs/uaa/31/config/cf-registrar/config.yml:host: 172.31.21.219
/var/vcap/data/jobs/health_manager_next/11/config/health_manager_next.yml:local_route: 172.31.21.219
/var/vcap/data/jobs/nats/12/config/nats.yml:net: 172.31.21.219
/var/vcap/data/jobs/cloud_controller_ng/13/config/cloud_controller_ng.yml:local_route: 172.31.21.219
/var/vcap/bosh/state.yml: ip: 172.31.21.219

local/install.sh line 48 provides a sample target command based on NISE_IP_ADDRESS. I suggest that if NISE_DOMAIN is defined, it should be used instead.

Also, it seems that recently the target command requires 'http://' before the domain name. I'm not sure what changed there...

The installer takes an insane amount to stop and throw this error:

#[5074] INFO: Installing package warden
#[5074] INFO: Running the packaging script for warden
#[5074] INFO: Installing package golang
#[5074] INFO: Running the packaging script for golang
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_cli/lib/cli/release_compiler.rb:163:in `rescue in find_in_indices': Blobstore error: Failed to create object, underlying error: execution expired /home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/1.9.1/openssl/buffering.rb:121:in `sysread' (Bosh::Cli::BlobstoreError)
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/1.9.1/openssl/buffering.rb:121:in `readpartial'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient/session.rb:349:in `readpartial'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient/session.rb:927:in `block in read_body_length'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient/session.rb:925:in `read_body_length'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient/session.rb:688:in `get_body'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient.rb:1065:in `do_get_block'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient.rb:869:in `block in do_request'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient.rb:956:in `protect_keep_alive_disconnected'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient.rb:868:in `do_request'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient.rb:756:in `request'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/gems/httpclient-2.2.4/lib/httpclient.rb:661:in `get'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/blobstore_client/lib/blobstore_client/simple_blobstore_client.rb:38:in `get_file'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/blobstore_client/lib/blobstore_client/s3_blobstore_client.rb:89:in `get_file'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/blobstore_client/lib/blobstore_client/base.rb:50:in `get'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_cli/lib/cli/release_compiler.rb:150:in `find_in_indices'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_cli/lib/cli/release_compiler.rb:109:in `find_package'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:304:in `find_package_archive'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/bosh.rb:225:in `get_source_package'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:64:in `start'
/home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:31:in `process'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:215:in `run_packaging'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:203:in `install_package'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:191:in `block in install_packages'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in `each'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in `install_packages'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:263:in `install_job'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:101:in `run_default_mode'
/home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:65:in `run'
./bin/nise-bosh:4:in `<main>'
    from /home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_cli/lib/cli/release_compiler.rb:121:in `find_in_indices'
    from /home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_cli/lib/cli/release_compiler.rb:109:in `find_package'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:304:in `find_package_archive'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/bosh.rb:225:in `get_source_package'
    from /home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:64:in `start'
    from /home/fidelix/.rbenv/versions/1.9.3-p392/lib/ruby/gems/1.9.1/bundler/gems/bosh-ff1fe58e1e64/bosh_agent/lib/bosh_agent/message/compile_package.rb:31:in `process'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:215:in `run_packaging'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:203:in `install_package'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:191:in `block in install_packages'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in `each'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:189:in `install_packages'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/builder.rb:263:in `install_job'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:101:in `run_default_mode'
    from /home/fidelix/cf_nise_installer/nise_bosh/lib/nise_bosh/runner.rb:65:in `run'
    from ./bin/nise-bosh:4:in `<main>'
fidelix@ubuntu:~$ 

I'm installing through SSH.
This is a fresh 10.04 install. Is there any more info I can put here to help?

Hello,

I have followed the instructions to build and provision a single server Devbox.

I am able to to target the box from a cf client, create and organization and space, however when it comes to pushing a known working application i get the following:
Uploading hello... OK
Starting hello... FAILED
PUT http://api.9.20.135.117.xip.io/v2/apps/58708262-7a2e-4deb-83f4-3e32e14d1a32?
stage_async=true timed out

When I check the app status with cf apps I see:
hello staging failed 1 x 256M hello.9.20.135.117.xip.io

When I check the logs with cf logs hello I see:
Time of crash:
2013-08-22 14:28:16 +0100

CFoundry::StagingError: 170001: Staging error: cannot get instances since stagin
g failed

<<<
REQUEST: GET http://api.9.20.135.117.xip.io/v2/apps/75f1c6db-49cd-4177-af01-0f69
1d1f2d88/instances
REQUEST_HEADERS:
Accept : application/json
Authorization : [PRIVATE DATA HIDDEN]
Content-Length : 0
RESPONSE: [400]
RESPONSE_HEADERS:
content-length : 89
content-type : application/json;charset=utf-8
date : Thu, 22 Aug 2013 13:28:01 GMT
server : thin 1.5.1 codename Straight Razor
x-content-type-options : nosniff
x-vcap-request-id : 02b93909-b446-4c69-93d8-c68cca1fa1cf
RESPONSE_BODY:
{
"code": 170001,
"description": "Staging error: cannot get instances since staging failed"
}

cfoundry-2.4.0/lib/cfoundry/baseclient.rb:167:in handle_error_response' cfoundry-2.4.0/lib/cfoundry/baseclient.rb:146:inhandle_response'
cfoundry-2.4.0/lib/cfoundry/baseclient.rb:87:in request' cfoundry-2.4.0/lib/cfoundry/baseclient.rb:64:inget'
cfoundry-2.4.0/lib/cfoundry/v2/base.rb:53:in instances' cfoundry-2.4.0/lib/cfoundry/v2/app.rb:55:ininstances'
cf-4.2.0/lib/cf/cli/app/logs.rb:19:in logs' mothership-0.5.1/lib/mothership/base.rb:66:inrun'
mothership-0.5.1/lib/mothership/command.rb:72:in block in invoke' cf-4.2.0/lib/manifests/plugin.rb:38:incall'
cf-4.2.0/lib/manifests/plugin.rb:38:in wrap_with_optional_name' cf-4.2.0/lib/manifests/plugin.rb:18:inblock (2 levels) in <class:ManifestsPlug
in>'
mothership-0.5.1/lib/mothership/command.rb:82:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:82:inblock (2 levels) in invoke'
mothership-0.5.1/lib/mothership/command.rb:86:in instance_exec' mothership-0.5.1/lib/mothership/command.rb:86:ininvoke'
mothership-0.5.1/lib/mothership/base.rb:55:in execute' cf-4.2.0/lib/cf/cli.rb:190:inblock (2 levels) in execute'
cf-4.2.0/lib/cf/cli.rb:201:in save_token_if_it_changes' cf-4.2.0/lib/cf/cli.rb:189:inblock in execute'
cf-4.2.0/lib/cf/cli.rb:125:in wrap_errors' cf-4.2.0/lib/cf/cli.rb:185:inexecute'
mothership-0.5.1/lib/mothership.rb:45:in start' cf-4.2.0/bin/cf:13:in<top (required)>'
c:/Ruby193/bin/cf:23:in load' c:/Ruby193/bin/cf:23:in

I have also attempted to push the "hello" application that comes with the install and that results in:
Preparing to start hello... FAILED
Application failed to stage
cat ~/.cf/crash # for more details

Any help with regards to the issue would be greatly appreciated.

Thank you
Sam

A command not found error is displayed for "add-apt-repository" when using the 64 bit Server version of Ubuntu v10.04.

To fix this I installed python-software-properties:

sudo apt-get install python-software-properties

I don't believe this error occurs with the desktop version of Ubuntu 64 bit v10.04

When running the scripts on Ubuntu 10.04.4 64 bit server, the scripts are failing at the Postgres step.

The error I'm seeing is:
sudo env PATH=/home/chris/.rbenc/shims:/home/chris/.rbenv/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games bundle exec ./bin/nise-bosh -y ../cf-release ../.deploy.yml micro -n 10.64.55.179
[sudo] password for chris:
The following templates and packages for job micro will be installed.
# postgres
at depth 1 - 20: unable to get local issuer certificate
/home/chris/.renv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/bundler/gems/bosh-e0c47270ae00/bosh_cli/lib/cli/release_compiler.rb:163:in 'rescue in find_in_indices': Blobstore error: Failed to fetch object, underlying error: #<OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed> /home/chris/.rbenv/versions/1.9.3-p448/lib/ruby/gems/httpclient-2.2.4/lib/httpclient/session.rb:300:in connect' (Bosh::Cli::BlobstoreError)

Compatibility problems with latest cf-release revisions will be reported to this issue.

If you find a problem not reported in this issue, please create another issue and report it there.

ubuntu ~$ export CF_RELEASE_USE_HEAD=yes
ubuntu ~$ bash < <(curl -s -k -B https://raw.github.com/yudai/cf_nise_installer/${INSTALLER_BRANCH:-master}/local/bootstrap.sh)

...

Submodule path 'src/vcap-common': checked out 'fd2546baf9975b942246f0866043d52ecd5d79da'
Initialized empty Git repository in /home/jfoster/cf_nise_installer/cf-release/src/warden/.git/
remote: Counting objects: 7506, done.
remote: Compressing objects: 100% (3880/3880), done.
remote: Total 7506 (delta 3652), reused 6875 (delta 3129)
Receiving objects: 100% (7506/7506), 1.87 MiB | 220 KiB/s, done.
Resolving deltas: 100% (3652/3652), done.
Submodule path 'src/warden': checked out '514389f258762ffe07a8e70ce8b32ccca6b870c6'

• set +x

welcome to...
___
_ |_ |
| |/ / __/
|_/____/

• RBENV_VERSION=1.9.3-p448
• bundle install
  Fetching source index from https://s3.amazonaws.com/bosh-jenkins-gems/
  Fetching gem metadata from https://rubygems.org/........
  Fetching gem metadata from https://rubygems.org/........
  Could not find bosh_common-1.5.0.pre.815 in any of the sources

Hi,
I am not sure, if this is the right issue list, but as I thought that cf_nise_installer_services would be installed within cf_nise_installer, I am posting it here. When I try to run:

bash < <(curl -s -k -B https://raw.github.com/yudai/cf_nise_installer_services/${INSTALLER_BRANCH:-master}/vagrant/bootstrap.sh)

I always get:

+ vagrant ssh -c 'sudo /etc/init.d/vboxadd setup'
/home/cs/cf_nise_installer/cf-release/Vagrantfile:4:in `<top (required)>': undefined method `configure' for Vagrant:Module (NoMethodError)
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config/loader.rb:115:in `load'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config/loader.rb:115:in `block in procs_for_source'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config.rb:41:in `block in capture_configures'
    from <internal:prelude>:10:in `synchronize'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config.rb:36:in `capture_configures'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config/loader.rb:114:in `procs_for_source'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config/loader.rb:51:in `block in set'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config/loader.rb:45:in `each'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/config/loader.rb:45:in `set'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/environment.rb:377:in `block in load_config!'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/environment.rb:392:in `call'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/environment.rb:392:in `load_config!'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/lib/vagrant/environment.rb:327:in `load!'
    from /home/cs/.rbenv/versions/1.9.3-p448/lib/ruby/gems/1.9.1/gems/vagrant-1.0.7/bin/vagrant:40:in `<top (required)>'
    from /home/cs/.rbenv/versions/1.9.3-p448/bin/vagrant:23:in `load'
    from /home/cs/.rbenv/versions/1.9.3-p448/bin/vagrant:23:in `<main>'

Is there anything I am doing wrong? Command executed on Ubuntu 10.0.4 in a VMware Fusion VM.

Hello,

I am trying the install of a nise Bosh machine (tried on 2 different machines with Ubuntu 10.04 64-bit with 4GB ram).
The install succeeds and ends with something like:

CF target: 'cf target http://api.xxx.xxx.xxx.xxx.xip.io'
CF login : 'cf login --password c1oudc0w admin'

However, when i try to start the machine I get the error:

bosh@ubuntu:~/cf_nise_installer$ ./local/start_processes.sh

• ./common/start_processes.sh
• sudo /var/vcap/bosh/bin/monit
  monit daemon at 2428 awakened
• sleep 10
• for process in postgres nats cloud_controller_ng
• sudo /var/vcap/bosh/bin/monit start postgres
• sleep 50
• for process in postgres nats cloud_controller_ng
• sudo /var/vcap/bosh/bin/monit start nats
• sleep 50
• for process in postgres nats cloud_controller_ng
• sudo /var/vcap/bosh/bin/monit start cloud_controller_ng
• sleep 50
• for process in nats_stream_forwarder cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start nats_stream_forwarder
  monit: action failed -- There is no service by that name

I also tried to remove this service from the common start scripts at:

/home/bosh/cf_nise_installer/common/start_processes.sh

Then the startup goes a little further, but finally never comes up completely:

bosh@ubuntu:~/cf_nise_installer$ ./local/start_processes.sh

• ./common/start_processes.sh
• sudo /var/vcap/bosh/bin/monit
  [sudo] password for bosh:
  Starting monit daemon with http interface at [127.0.0.1:2822]
• sleep 10
• for process in postgres nats cloud_controller_ng
• sudo /var/vcap/bosh/bin/monit start postgres
• sleep 40
• for process in postgres nats cloud_controller_ng
• sudo /var/vcap/bosh/bin/monit start nats
• sleep 40
• for process in postgres nats cloud_controller_ng
• sudo /var/vcap/bosh/bin/monit start cloud_controller_ng
• sleep 40
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start cloud_controller_jobs
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start nginx_ccng
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start gorouter
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start health_manager_next
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start uaa
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start uaa_cf-registrar
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start warden
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start dea_next
• sleep 10
• for process in cloud_controller_jobs nginx_ccng gorouter health_manager_next uaa uaa_cf-registrar warden dea_next dir_server
• sudo /var/vcap/bosh/bin/monit start dir_server
• sleep 10
• echo 'Waiting for all processes to start'
  Waiting for all processes to start
• (( i=0 ))
• (( i < 120 ))
• sudo /var/vcap/bosh/bin/monit summary
• tail -n +3
• grep -E 'running$'
  Process 'nats' running
  Process 'nginx_ccng' running
  Process 'gorouter' running
  Process 'postgres' running
• break

bosh@ubuntu:~/cf_nise_installer$ sudo /var/vcap/bosh/bin/monit summary
The Monit daemon 5.2.4 uptime: 16m

Process 'nats' running
Process 'health_manager_next' Execution failed
Process 'uaa' running
Process 'uaa_cf-registrar' running
Process 'cloud_controller_ng' Does not exist
Process 'cloud_controller_jobs' initializing
Process 'nginx_ccng' running
Process 'gorouter' running
Process 'warden' not monitored
Process 'dea_next' not monitored
Process 'dir_server' running
Process 'postgres' running
System 'system_ubuntu' not monitored

Please advise, as I am not able to install this on any machine.

Kind regards,

Installation was running along fine until I hit this error:
Any ideas why?

• CF_RELEASE_URL=https://github.com/cloudfoundry/cf-release.git
• CF_RELEASE_BRANCH=ea61ec6f8f
  ++ cut -f1 '-d '
  ++ rbenv version
• ruby_version=1.9.3-p448
• '[' '!' -d cf-release ']'
• ./local/launch_nise_bosh.sh
  ++ head -n 1
  ++ cut -f1 -d /
  ++ cut -f 6 -d ' '
  ++ grep 'inet .*global'
  ++ ip addr
• NISE_IP_ADDRESS=172.16.108.141
• NISE_IP_ADDRESS=172.16.108.141
• ./common/launch_nsie_bosh.sh
• sed s/192.168.10.10/172.16.108.141/g manifests/micro.yml
• '[' '' '!=' '' ']'
• cd nise_bosh
• bundle install
  Fetching gem metadata from http://rubygems.org/......
  Fetching gem metadata from http://rubygems.org/..
  Could not find bosh_common-1.5.0.pre.877 in any of the sources

Hi,

what's the recommended approach to stop and start again the local devbox using Vagrant after it had been bootstraped once? That's not clear to me from the information in the README.md
Seems like when I use 'vagrant halt' to stop the devbox and the 'vagrant up' to start it again, I can't target Cloudfoundry anymore and get the following error:

CFoundry::TargetRefused: target refused connection (Connection refused - connect(2))

Thanks
Joerg