Fleetctl issue
We are facing the following issue after following the tutorial
fleetctl list-machines
Error retrieving list of active machines from fleet API (googleapi: got HTTP response code 404 with body: 404 page not found
)
Possible issues:
etcd is unhealthy and/or lost quorum
connection cannot be established to any etcd servers
curl http://172.17.8.101:2379
404 page not found
Any idea on the issue? We must be doing something very silly.
the same issue . @vbanthia @sorccu any idea ?
Same issue on my mac sierra, Execute without root:
Error retrieving list of active machines from fleet API (googleapi: got HTTP response code 404 with body: 404 page not found
)
Possible issues:
etcd is unhealthy and/or lost quorum
connection cannot be established to any etcd servers
With root perm:
Error retrieving list of units from repository: Get http://domain-sock/fleet/v1/state?alt=json: dial unix /var/run/fleet.sock: connect: no such file or directory
Any solutions ?
The service is not installed/configured. When you login into the vm core-01 I can't find the service:
vagrant ssh core-01
core@core-01 ~ $ netstat -plunt
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp6 0 0 :::22 :::* LISTEN -
udp 0 0 10.0.2.15:68 0.0.0.0:* -
udp6 0 0 fe80::a00:27ff:fef1:546 :::*
The Error also tells us:
etcd is unhealthy and/or lost quorum
same issue ㅠ
The problem seems to be here:
CoreOS has changed the name of the etcd service again.
You need to edit your cloud-config parameters and change etcd2 to etcd-member in the name: line under units: and also change the etcd2: line to etcd-member: further down in the template.
You may also need to comment out the two lines starting the fleet service, the line "- name: fleet.service" and the one below it. Some newer CoreOS builds don't seem to include it and it needs to be commented out of the template.
as per https://discussions.citrix.com/topic/394388-after-coreos-update-to-168853-unit-etcd2service-not-found/
I am trying to fix this but I have no experience with vagrant, so I may not succeed.
This patch gets etcd-member started
0001-change-etcd2-to-etcd-member-as-coreOS-renamed-it.txt
core@core-01 ~ $ netstat -plunt (Not all processes could be identified, non-owned process info will not be shown, you would have to be root to see it all.) Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 127.0.0.1:2379 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:2380 0.0.0.0:* LISTEN - tcp6 0 0 :::22 :::* LISTEN - udp 0 0 10.0.2.15:68 0.0.0.0:* - udp6 0 0 fe80::a00:27ff:fead:546 :::* -
however the issue remains
~/g/s/coreos ❯❯❯ fleetctl list-machines ⏎ Error retrieving list of active machines from fleet API (Get http://172.17.8.101:2379/fleet/v1/machines?alt=json: dial tcp 172.17.8.101:2379: connect: connection refused) Possible issues: etcd is unhealthy and/or lost quorum connection cannot be established to any etcd servers