Skip to main content

painful etcd configuration

I'm not sure what happened but my etcd configuration stopped working. I recently acquired two Intel NUC devices and while they were a pain in the ass to configure the BIOS (I found this link and everything is all better from the boot)

Next it was a matter of selecting the topology. This is normally an easy task but lately I have experienced a few bugs which I cannot explain. The one good news is that I have been able to try and try again.

$ sudo rm -rf /var/lib/etcd2/proxy
$ sudo systemctl stop etcd2
$ sudo coreos-cloudinit --from-file ./cloud-config.yml
$ sudo systemctl start etcd2
$ sudo journalctl -f -u etcd2

And then test the health of the system


$ etcdctl --debug cluster-health 

But for some strange reason my proxy node (worker) seems to lose a healthy connection to the etcd leader.

Mar 21 00:50:43 corenuc2 systemd[1]: Started etcd2.
Mar 21 00:50:43 corenuc2 etcd2[4036]: proxy: listening for client requests on http://0.0.0.0:4001
Mar 21 00:51:13 corenuc2 etcd2[4036]: could not get cluster response from http://0.0.0.0:2380: Get http://0.0.0.0:2380/members: dial tcp 0.0.0.0:2380: connection refused
Mar 21 00:51:13 corenuc2 etcd2[4036]: proxy: could not retrieve cluster information from the given urls
Mar 21 00:51:19 corenuc2 etcd2[4036]: proxy: zero endpoints currently available
Mar 21 00:51:19 corenuc2 etcd2[4036]: proxy: zero endpoints currently available
Mar 21 00:51:26 corenuc2 etcd2[4036]: proxy: zero endpoints currently available
Mar 21 00:51:26 corenuc2 etcd2[4036]: proxy: zero endpoints currently available


My SOLO etcd server:
coreos:
  etcd2:
    name: etcdserver
    initial-cluster: etcdserver=http://192.168.86.113:2380
    listen-client-urls: http://127.0.0.1:2379,http://192.168.86.113:2379,http://127.0.0.1:4001,http://192.168.86.113:4001
    #listen-client-urls: http://0.0.0.0:2379,http://0.0.0.0:4001
    advertise-client-urls: http://192.168.86.113:2379
    initial-advertise-peer-urls: http://192.168.86.113:2380 

    listen-peer-urls: http://192.168.86.113:2380,http://192.168.86.113:7001


My worker with etcd configured as a proxy
coreos:
  etcd2:
    proxy: on
    name: etcdworker
    initial-cluster: etcdserver=http://192.168.86.113:2380

    listen-client-urls: http://0.0.0.0:2379,http://0.0.0.0:4001

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…