{"action":"closed","issue":{"url":"https://api.github.com/repos/coreos/etcd/issues/2378","labels_url":"https://api.github.com/repos/coreos/etcd/issues/2378/labels{/name}","comments_url":"https://api.github.com/repos/coreos/etcd/issues/2378/comments","events_url":"https://api.github.com/repos/coreos/etcd/issues/2378/events","html_url":"https://github.com/coreos/etcd/issues/2378","id":59012084,"number":2378,"title":"Cluster start unhealthy after resting. (https server -> client)","user":{"login":"agokjr","id":692138,"avatar_url":"https://avatars.githubusercontent.com/u/692138?v=3","gravatar_id":"","url":"https://api.github.com/users/agokjr","html_url":"https://github.com/agokjr","followers_url":"https://api.github.com/users/agokjr/followers","following_url":"https://api.github.com/users/agokjr/following{/other_user}","gists_url":"https://api.github.com/users/agokjr/gists{/gist_id}","starred_url":"https://api.github.com/users/agokjr/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/agokjr/subscriptions","organizations_url":"https://api.github.com/users/agokjr/orgs","repos_url":"https://api.github.com/users/agokjr/repos","events_url":"https://api.github.com/users/agokjr/events{/privacy}","received_events_url":"https://api.github.com/users/agokjr/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-02-26T03:23:03Z","updated_at":"2015-03-03T14:28:40Z","closed_at":"2015-03-03T14:28:40Z","body":"> etcd v2.0.3\r\n> etcdctl v2.0.3\r\n\r\nEnvironment flags (extracted when did force new cluster to try and reset)\r\n```\r\nexport ETCD_NAME=coreos-test-01\r\nexport ETCD_ADVERTISE_CLIENT_URLS=https://XXX.XXX.XXX.XX1:2379,https://XXX.XXX.XXX.XX1:4001\r\nexport ETCD_CA_FILE=/etc/ssl/certs/etcd.pem\r\nexport ETCD_CERT_FILE=/etc/etcd/etcd.crt\r\nexport ETCD_DATA_DIR=/var/lib/etcd\r\nexport ETCD_INITIAL_ADVERTISE_PEER_URLS=https://XXX.XXX.XXX.XX1:2380\r\nexport ETCD_INITIAL_CLUSTER=coreos-test-01=https://XXX.XXX.XXX.XX1:2380,coreos-test-02=https://XXX.XXX.XXX.XX2:2380,coreos-test-03=https://XXX.XXX.XXX.XX3:2380,coreos-test-04=https://XXX.XXX.XXX.XX4:2380\r\nexport ETCD_INITIAL_CLUSTER_TOKEN=etcd-test\r\nexport ETCD_KEY_FILE=/etc/etcd/etcd.key.insecure\r\nexport ETCD_LISTEN_CLIENT_URLS=https://0.0.0.0:2379,https://0.0.0.0:4001\r\nexport ETCD_LISTEN_PEER_URLS=https://XXX.XXX.XXX.XX1:2380\r\nexport ETCD_PEER_CA_FILE=/etc/ssl/certs/etcd.pem\r\nexport ETCD_PEER_CERT_FILE=/etc/etcd/etcd.crt\r\nexport ETCD_PEER_KEY_FILE=/etc/etcd/etcd.key.insecure\r\n```\r\nCerts are generated using etcd-ca\r\nAlso Noticed that fleet keeps on having machines drop off and then show up with every thing restarting on the machine.\r\n\r\nFleet has many of these in the log\r\n```\r\nFeb 26 01:50:27 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:28 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:28 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:28 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:28 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:28 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:34 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:34 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:36 coreos-test-01 fleetd[786]: INFO client.go:291: Failed getting response from https://XXX.XXX.XXX.XX1:4001/: cancelled\r\nFeb 26 01:50:37 coreos-test-01 fleetd[786]: ERROR server.go:185: Server monitor triggered: Monitor timed out before successful heartbeat\r\n```\r\n\r\nI am not sure what to do next on this one. Things seemed fine until I turned on Server to client https."}}