Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    manyan.chen
    @manyan
    @tleyden can you provide a command to start/restart a couchbase node using docker? one of the node went down last night, as you can see the docker ps return me empty list, would like to restart it, but can no find the command, cheers
    Traun Leyden
    @tleyden
    @manyan sorry, just now seeing your message.
    @manyan can you give me a little more background on how you are running it? Is this under coreos? let me know the blog post or instructions you are working off of
    Traun Leyden
    @tleyden
    @PaulCapestany the coreos/fleet stuff is broken for me too: couchbaselabs/couchbase-server-coreos#17. I'm pretty sure I broke things when I made some changes to make things work with Kubernetes.
    Traun Leyden
    @tleyden
    ok, fixed and I the instructions have been consolidated into this README
    Paul Capestany
    @PaulCapestany
    @tleyden just now seeing your message, I seemed to still run into issues even with updated code + README → couchbaselabs/couchbase-server-coreos#18
    Traun Leyden
    @tleyden
    can you paste the output of "docker log afd91d66eab3"?
    (the container id of the sync gw container that seems to have failed)
    or fleetctl journal --lines 1000 sync_gw_node@1.service
    Paul Capestany
    @PaulCapestany
    sure
    oh, hmm, already killed off that cluster, starting up a new one
    Paul Capestany
    @PaulCapestany
    @tleyden — I just edited couchbaselabs/couchbase-server-coreos#18 and updated all the log files with info from a brand new cluster (and added extra stuff you'd asked for)
    I'm surprised that the config emitted had "server":"http://127.0.0.1:8091", rather than {{ .COUCHBASE_IP }}, though I don't know if that's the root problem
    Traun Leyden
    @tleyden
    that whole approach of rewriting the file from a template feels super hacky.
    I guess the thing writing the file is probably writing it one place, and thing reading the file is looking for it in a different place... what those places are is not immediately apparent.
    I guess confd would probably be a cleaner approach. any thoughts?
    Paul Capestany
    @PaulCapestany
    @tleyden your README (and the issue I opened) uses --config-url=http://git.io/b9PK which sets "server":"http://127.0.0.1:8091"
    Traun Leyden
    @tleyden
    egads
    good catch, I need to fix that
    Paul Capestany
    @PaulCapestany
    though I'd also used my own config file with {{ .COUCHBASE_IP }} and still had same issues I think
    retrying now though to triple check
    Paul Capestany
    @PaulCapestany
    yeah, same issue even when using {{ .COUCHBASE_SERVER_IP }} https://gist.github.com/PaulCapestany/b58b26d44b4cb6fd1f34
    Paul Capestany
    @PaulCapestany
    @tleyden I think I may have tracked things down a bit further → https://github.com/couchbaselabs/couchbase-server-coreos/issues/18#issuecomment-106026386
    Traun Leyden
    @tleyden
    just posted to the ticket
    Traun Leyden
    @tleyden
    @PaulCapestany merged. glad you remembered to run go generate!
    to use that change, you'll need to follow the instructions here: https://github.com/tleyden/couchbase-cluster-go#running-on-the-latest-code
    Paul Capestany
    @PaulCapestany
    yeah
    Traun Leyden
    @tleyden
    (so that it pulls the latest couchbase-cluster-go rather than using the version baked into the docker image)
    Paul Capestany
    @PaulCapestany
    one thing I noticed though is that go generate output seems to differ a bit (not just in generated bytes), for example removing a ~ ... does that matter?
    couchbase-cluster-go (Git) 2015-05-27 14-11-19.png
    Paul Capestany
    @PaulCapestany
    @tleyden I think etcdctl set /couchbase.com/enable-code-refresh true may not be working as expected since I just spun up new cluster and am still getting Error reading config file sync_gateway: open sync_gateway: no such file or directory -- rest.ParseCommandLine() at config.go:294
    Traun Leyden
    @tleyden

    example removing a ~ ... does that matter?

    I don't think so

    still getting Error reading config

    which command did you use to kick off the cluster? also can you paste the logs from the "cluster kick off" command?

    Paul Capestany
    @PaulCapestany
    I set up cluster with:
    etcdctl set /couchbase.com/enable-code-refresh true && \
    sudo docker run --net=host tleyden5iwx/couchbase-cluster-go couchbase-fleet launch-cbs \
      --version latest \
      --num-nodes 3 \
      --userpass "user:passw0rd" \
    && \
    sudo docker run --net=host tleyden5iwx/couchbase-cluster-go sync-gw-cluster launch-sgw \
      --num-nodes=1 \
      --config-url=https://gist.githubusercontent.com/PaulCapestany/d24c9ca8223faab66b25/raw/638729f249f65dd6a275b67d467ac46938e9005e/pac_sg_config.json \
      --create-bucket todos \
      --create-bucket-size 512 \
      --create-bucket-replicas 1
    interestingly, those logs show 2015/05/27 21:43:26 Update-Wrapper: updating to latest code
    so it looks like update-wrapper.go is trying to do its thing, logs show new downloads being triggered too..
    Paul Capestany
    @PaulCapestany
    oops, logs I'd posted above were from journalctl, here's the actual output from running the cluster kickoff commands: https://gist.github.com/PaulCapestany/35065c2fa242291a5015
    Traun Leyden
    @tleyden
    crap, it's not spitting out the sync gw fleet units.
    can you run fleetctl cat on the sync gateway units and paste the output? was this a "fresh cluster"? I wonder if the old unit files never got overwritten?
    could you try running https://github.com/tleyden/couchbase-cluster-go#destroying-the-cluster first and then trying again?
    btw it's possible to get into the container and see the couchbase-cluster-go commit id via:
    $ docker exec -ti <container_id> bash
    # cd /opt/go/src/github.com/tleyden/couchbase-cluster-go
    # git status
    Paul Capestany
    @PaulCapestany
    yeah i just came to same conclusion about fleet units
    they don't get updated it seems
    still show old ones
    (and yeah, it was a totally fresh cluster)
    Paul Capestany
    @PaulCapestany
    and yeah... git status shows that couchbase-cluster-go is on freshest commit. seems like fleet unit files just don't get swapped out with current enable-code-refresh implementation
    Traun Leyden
    @tleyden
    we need to have it spit out the sync gateway unit files into the logs so we can see that it's generating the correct unit files
    Paul Capestany
    @PaulCapestany
    would it make sense to use an automatic hook to deploy new docker images when there are commits to the couchbase-cluster-go repo? cuz that's what you're basically trying to do with enable-code-refresh, or no?
    Traun Leyden
    @tleyden
    yes and no, enable-code-refresh should have a much tighter loop since it doesn't have to wait for a docker image rebuilt (can take up to 30 mins)