cf-charmers team mailing list archive

[Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>]

Further investigation shows the same error I was getting locally with the
AWS deployment.

cc/0 is at 100% CPU with this error repeating every 5 to 10 seconds in
/var/log/upstart/cf-cloudcontroller.log

Deprecated: Use -s or --insert-seed flag
/var/lib/cloudfoundry/cfcloudcontroller/app/models/runtime/app.rb:94:in
`<class:App>': undefined method `kill_after_multiple_restarts' for class
`VCAP::CloudController::App' (NameError)
    from
/var/lib/cloudfoundry/cfcloudcontroller/app/models/runtime/app.rb:5:in
`<module:CloudController>'
    from
/var/lib/cloudfoundry/cfcloudcontroller/app/models/runtime/app.rb:4:in
`<top (required)>'
    from
/var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/db.rb:56:in
`require'
    from
/var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/db.rb:56:in
`load_models'
    from
/var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:90:in
`setup_db'
    from
/var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:161:in
`start_cloud_controller'
    from
/var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:111:in
`block in run!'
    from
/var/lib/cloudfoundry/cfcloudcontroller/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`call'
    from
/var/lib/cloudfoundry/cfcloudcontroller/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`run_machine'
    from
/var/lib/cloudfoundry/cfcloudcontroller/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`run'
    from
/var/lib/cloudfoundry/cfcloudcontroller/lib/cloud_controller/runner.rb:104:in
`run!'
    from bin/cloud_controller:12:in `<main>'

I can't understand how I can produce this locally and on AWS but that it
works for you.


-Ben




On Fri, Apr 18, 2014 at 12:15 PM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:

> It worked for me several times, will retry it now.
>
>
> On 18 April 2014 21:53, Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>wrote:
>
>> With a fresh deployment. All status are started.
>>
>>     units:
>>       router/0:
>>         agent-state: started
>>         agent-version: 1.18.1
>>         machine: "0"
>>         open-ports:
>>         - 80/tcp
>>         - 443/tcp
>>         public-address: ec2-54-242-193-242.compute-1.amazonaws.com
>>
>>
>> $ cf login -a http://api.54.242.193.242.xip.io/
>>
>> VERSION:
>> 6.0.2-0bba99f
>>
>> API endpoint: http://api.54.242.193.242.xip.io/
>>
>> REQUEST: [2014-04-18T11:49:59-07:00]
>> GET //v2/info HTTP/1.1
>> Host: api.54.242.193.242.xip.io
>>
>> Accept: application/json
>> Content-Type: application/json
>> User-Agent: go-cli 6.0.2-0bba99f / linux
>>
>>
>>
>> RESPONSE: [2014-04-18T11:49:59-07:00]
>>
>> HTTP/1.1 404 Not Found
>> Content-Length: 9
>> Content-Type: text/html
>> Date: Fri, 18 Apr 2014 18:49:59 GMT
>>
>> Server: thin 1.5.1 codename Straight Razor
>> X-Cascade: pass
>>
>> Not Found
>> Warning: Insecure http API endpoint detected: secure https API endpoints
>> are recommended
>>
>> FAILED
>> Invalid API endpoint.
>> Server error, status code: 404, error code: 0, message:
>> FAILED
>> Invalid API endpoint.
>> Server error, status code: 404, error code: 0, message:
>>
>>
>> So its still not working for me. Could the cf binary be incompatible with
>> the bundle, would I need to downgrade?
>>
>> -Ben
>>
>>
>>
>> On Fri, Apr 18, 2014 at 11:29 AM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:
>>
>>>
>>>
>>> ---------- Forwarded message ----------
>>> From: Alexander Lomov <lomov.as@xxxxxxxxx>
>>> Date: 18 April 2014 21:28
>>> Subject: Re: [Cf-charmers] AWS single node deployment with juju deployer.
>>> To: Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>
>>>
>>>
>>> Hey, Ben.
>>>
>>> You need to do following:
>>> 1. run `juju status router` to get public dns name of your router.
>>> 2. run `host *<router-public-dns>*` command and get public ip of your
>>> router.
>>> 3. run `cf login -a http://api.<router-public-ip>.xip.io`
>>>
>>> Pretty sure it will work.
>>>
>>>
>>> On 18 April 2014 21:04, Benjamin Saller <benjamin.saller@xxxxxxxxxxxxx>wrote:
>>>
>>>> I can deploy the bundle but have been unable to log in to the
>>>> deployment.
>>>>
>>>> With CF_TRACE=true
>>>>
>>>> cf login -a ec2-54-196-120-225.compute-1.amazonaws.com
>>>>
>>>> VERSION:
>>>> 6.0.2-0bba99f
>>>>
>>>> API endpoint: ec2-54-196-120-225.compute-1.amazonaws.com
>>>>
>>>> REQUEST: [2014-04-18T09:14:56-07:00]
>>>> GET /v2/info HTTP/1.1
>>>> Host: ec2-54-196-120-225.compute-1.amazonaws.com
>>>> Accept: application/json
>>>> Content-Type: application/json
>>>> User-Agent: go-cli 6.0.2-0bba99f / linux
>>>>
>>>>
>>>>
>>>> REQUEST: [2014-04-18T09:14:57-07:00]
>>>> GET /v2/info HTTP/1.1
>>>> Host: ec2-54-196-120-225.compute-1.amazonaws.com
>>>> Accept: application/json
>>>> Content-Type: application/json
>>>> User-Agent: go-cli 6.0.2-0bba99f / linux
>>>>
>>>>
>>>>
>>>> RESPONSE: [2014-04-18T09:14:57-07:00]
>>>> HTTP/1.1 404 Not Found
>>>> Content-Length: 9
>>>> Content-Type: text/html
>>>> Date: Fri, 18 Apr 2014 16:14:57 GMT
>>>> Server: thin 1.5.1 codename Straight Razor
>>>> X-Cascade: pass
>>>>
>>>> Not Found
>>>> Warning: Insecure http API endpoint detected: secure https API
>>>> endpoints are recommended
>>>>
>>>> FAILED
>>>> Invalid API endpoint.
>>>> Server error, status code: 404, error code: 0, message:
>>>> FAILED
>>>> Invalid API endpoint.
>>>> Server error, status code: 404, error code: 0, message:
>>>>
>>>>
>>>>
>>>>
>>>> I've even tried putting the CF client on the bootstrap node and running
>>>> from there using the xip.io address, same result.
>>>>
>>>> Any one have any insights?
>>>> -Ben
>>>>
>>>>
>>>>
>>>> On Fri, Apr 18, 2014 at 8:02 AM, Alexander Lomov <lomov.as@xxxxxxxxx>wrote:
>>>>
>>>>> Hey, all.
>>>>>
>>>>> Just to be on the same page about the topic: it is possible to deploy
>>>>> single node configuration of Cloud Foundry to AWS.
>>>>>
>>>>> I added bundle_v001_single_aws_node.yaml file to `bundle` project to
>>>>> support this deployment type (
>>>>> http://bazaar.launchpad.net/~cf-charmers/charms/bundles/cloudfoundry/bundle/view/30/bundle_v001_single_aws_node.yaml
>>>>> ).
>>>>>
>>>>> Also I've created tags `v002` for each CF charm to freeze sources that
>>>>> are needed for this deployment.
>>>>>
>>>>> In order to perform deployment I used following commands from folder
>>>>> of `bundle` project:
>>>>> ```
>>>>> juju bootstrap --constraints "mem=4G arch=amd64"
>>>>> juju deployer -Wvdc bundle_v001_single_aws_node.yaml
>>>>> ```
>>>>>
>>>>>
>>>>> Best wishes,
>>>>> Alex.
>>>>>
>>>>>
>>>>> --
>>>>> Mailing list: https://launchpad.net/~cf-charmers
>>>>> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
>>>>> Unsubscribe : https://launchpad.net/~cf-charmers
>>>>> More help   : https://help.launchpad.net/ListHelp
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Mailing list: https://launchpad.net/~cf-charmers
>>> Post to     : cf-charmers@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~cf-charmers
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>>
>>
>