Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Traun Leyden
    @tleyden
    btw I'm gonna have to bail abruptly soon .. probably around 4:30 depending on when my buddy shows up
    Jesse Vander Does
    @FreakTheMighty
    Cool, NP
    Was great chatting with you.
    Traun Leyden
    @tleyden
    I can still chat
    but I'll have to bail soon and might forget to say bye ;)
    Jesse Vander Does
    @FreakTheMighty
    What does this file do?
    Is it defining services?
    Traun Leyden
    @tleyden
    Jesse Vander Does
    @FreakTheMighty
    Cool thanks
    Traun Leyden
    @tleyden
    the reason it needs to be customized is to pre-populate the system with some files that are needed
    Jesse Vander Does
    @FreakTheMighty
    got it
    I’ve set num_instances to 1, and update channel to stable in config.rb
    Traun Leyden
    @tleyden
    oh wait, that should be channel alpha
    let me update the docs
    Jesse Vander Does
    @FreakTheMighty
    It says alpha in the coreos example, just thought better of it.
    Traun Leyden
    @tleyden
    yeah I originally used stable, but added some features that required alpha
    Jesse Vander Does
    @FreakTheMighty
    K, is it worth forking coreos-vagrant just to store elastic-thought specific setup?
    Traun Leyden
    @tleyden
    if you have launched a cluster and need to modify it the config.rb or user-data, you should run vagrant reload --provision to make the changes take effect (it will restart all machines)
    hmmm, that's not a bad idea
    Jesse Vander Does
    @FreakTheMighty
    I just deleted the machine and re-upped, no problem.
    Traun Leyden
    @tleyden
    how would the fork be kept up to date though?
    (is manual merging the only way?)
    Jesse Vander Does
    @FreakTheMighty
    That’s what I was about to write. Maybe just storing the configs in the project is better.
    Traun Leyden
    @tleyden
    maybe a script like "setup_vagrant.sh" would do the trick nicely
    Jesse Vander Does
    @FreakTheMighty
    I think so
    It would, clone the repo and copy the configs, is that all?
    Traun Leyden
    @tleyden
    yeah, essentially just automate the manual labor you just went through
    Jesse Vander Does
    @FreakTheMighty
    Cool
    Do you keep the Vagrant file in your elastic-thought project directory, or do you keep it in the core-os repo?
    Traun Leyden
    @tleyden
    I keep mine in ~/Vagrant/core-os (and keep my ubuntu vagrant file under ~/Vagrant/ubuntu)
    Jesse Vander Does
    @FreakTheMighty
    k
    Jesse Vander Does
    @FreakTheMighty
    BTW I’ve played with pouchdb a bit.
    Traun Leyden
    @tleyden
    I've never actually played with it yet
    I lean towards mobile apps rather than web apps
    I mean native mobile apps
    but yeah, I think pouchdb is really cool for html5 dev
    Jesse Vander Does
    @FreakTheMighty
    I haven’t investigated much, but after setting up core os and sharing the elastic-thought source with the vagrant image, I ran ./elasticthought-cluster-init.sh -v 3.0.1 -n 3 -u user:passw0rd -p gpu
    After fetching the images I get Error: Cannot sync with the cluster using peers 127.0.0.1:4001 Kick off couchbase cluster 2015/03/23 03:55:59 Update-Wrapper: skipping update 2015/03/23 03:55:59 Connect to etcd on localhost 2015/03/23 03:55:59 verifyEnoughMachinesAvailable() 2015/03/23 03:55:59 getJsonData error: Get http://localhost:49153/fleet/v1/machines: dial tcp 127.0.0.1:49153: connection refused 2015/03/23 03:55:59 Failed: Get http://localhost:49153/fleet/v1/machines: dial tcp 127.0.0.1:49153: connection refused 2015/03/23 03:55:59 Error invoking target: exit status 1 Failed to kick off couchbase server
    Also, I’m curious, why use vagrant and docker in development? Seems like docker alone should suffice.
    I see now that error comes from starting the couchbase container, I’ll have to look into it more.
    Traun Leyden
    @tleyden

    Error: Cannot sync with the cluster using peers 127.0.0.1:4001

    that's a bad error -- 4001 is the etcd port, so it looks like etcd is not setup for some reasons (and etcd is a core component, without that nothing will work)

    I think before running the elasticthought-cluster-init.sh you should have verified the coreos setup with fleetctl list-machines. I'll add that to the readme
    Traun Leyden
    @tleyden
    try running fleetctl list-machines and paste the output
    Jesse Vander Does
    @FreakTheMighty
    From core-01 the output is core@core-01 ~ $ fleetctl list-machines 2015/03/24 05:20:15 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:15 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 100ms 2015/03/24 05:20:15 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:15 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 200ms 2015/03/24 05:20:15 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:15 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 400ms 2015/03/24 05:20:16 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:16 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 800ms 2015/03/24 05:20:16 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:16 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 1s 2015/03/24 05:20:17 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:17 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 1s 2015/03/24 05:20:18 ERROR fleetctl.go:212: error attempting to check latest fleet version in Registry: timeout reached 2015/03/24 05:20:18 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:18 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 100ms 2015/03/24 05:20:18 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:18 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 200ms 2015/03/24 05:20:18 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:18 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 400ms 2015/03/24 05:20:19 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:19 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 800ms 2015/03/24 05:20:19 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:19 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 1s 2015/03/24 05:20:20 INFO client.go:291: Failed getting response from http://127.0.0.1:4001/: dial tcp 127.0.0.1:4001: connection refused 2015/03/24 05:20:20 ERROR client.go:213: Unable to get result for {Get /_coreos.com/fleet/machines}, retrying in 1s Error retrieving list of active machines: timeout reached
    Jesse Vander Does
    @FreakTheMighty
    Are you saying etcd isn’t setup on my computer, or on the VMs?
    Traun Leyden
    @tleyden
    On the vms, in coreos.
    I think you might have a bad etcd discovery token. In the config.rb there are instructions to uncomment some stuff which will pull a fresh token each time coreos is started.
    (On my phone, will give more details later)
    Jesse Vander Does
    @FreakTheMighty
    Cool, I'll investigate.