Created
June 10, 2015 12:59
-
-
Save arthur-c/af1f79494af8d37a9b6e to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
systemctl restart etcd2^C | |
aws-beta-coreos-04 ~ # journalctl -u etcd2 | |
-- Logs begin at Wed 2015-06-10 12:54:13 , end at Wed 2015-06-10 12:56:05 . -- | |
Jun 10 12:54:37 aws-beta-coreos-04 systemd[1]: Started etcd2. | |
Jun 10 12:54:37 aws-beta-coreos-04 systemd[1]: Starting etcd2... | |
Jun 10 12:54:40 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:54:40 etcd: listening for peers on http://172.31.28.82:2380 | |
Jun 10 12:54:40 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:54:40 etcd: listening for client requests on http://0.0.0.0:2379 | |
Jun 10 12:54:40 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:54:40 etcdserver: datadir is valid for the 2.0.1 format | |
Jun 10 12:54:41 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:54:41 discovery: found self 3f0bf881864e2ad6 in the cluster | |
Jun 10 12:54:41 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:54:41 discovery: found 1 peer(s), waiting for 2 more | |
Jun 10 12:55:42 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:55:42 discovery: during waiting for other nodes connection to https://discovery.etcd.io timed out, retrying | |
Jun 10 12:55:45 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:55:45 discovery: found self 3f0bf881864e2ad6 in the cluster | |
Jun 10 12:55:45 aws-beta-coreos-04 etcd2[617]: 2015/06/10 12:55:45 discovery: found 1 peer(s), waiting for 2 more | |
Jun 10 12:55:53 aws-beta-coreos-04 systemd[1]: Stopping etcd2... | |
Jun 10 12:55:53 aws-beta-coreos-04 systemd[1]: etcd2.service: main process exited, code=exited, status=2/INVALIDARGUMENT | |
Jun 10 12:55:53 aws-beta-coreos-04 systemd[1]: Unit etcd2.service entered failed state. | |
Jun 10 12:55:53 aws-beta-coreos-04 systemd[1]: etcd2.service failed. | |
Jun 10 12:55:53 aws-beta-coreos-04 systemd[1]: Started etcd2. | |
Jun 10 12:55:53 aws-beta-coreos-04 systemd[1]: Starting etcd2... | |
Jun 10 12:55:53 aws-beta-coreos-04 etcd2[749]: 2015/06/10 12:55:53 etcd: listening for peers on http://172.31.28.82:2380 | |
Jun 10 12:55:53 aws-beta-coreos-04 etcd2[749]: 2015/06/10 12:55:53 etcd: listening for client requests on http://0.0.0.0:2379 | |
Jun 10 12:55:53 aws-beta-coreos-04 etcd2[749]: 2015/06/10 12:55:53 etcdserver: datadir is valid for the 2.0.1 format | |
Jun 10 12:55:54 aws-beta-coreos-04 systemd[1]: etcd2.service: main process exited, code=exited, status=1/FAILURE | |
Jun 10 12:55:54 aws-beta-coreos-04 systemd[1]: Unit etcd2.service entered failed state. | |
Jun 10 12:55:54 aws-beta-coreos-04 systemd[1]: etcd2.service failed. | |
Jun 10 12:56:04 aws-beta-coreos-04 systemd[1]: etcd2.service holdoff time over, scheduling restart. | |
Jun 10 12:56:04 aws-beta-coreos-04 systemd[1]: Started etcd2. | |
Jun 10 12:56:04 aws-beta-coreos-04 systemd[1]: Starting etcd2... | |
Jun 10 12:56:04 aws-beta-coreos-04 etcd2[758]: 2015/06/10 12:56:04 etcd: listening for peers on http://172.31.28.82:2380 | |
Jun 10 12:56:04 aws-beta-coreos-04 etcd2[758]: 2015/06/10 12:56:04 etcd: listening for client requests on http://0.0.0.0:2379 | |
Jun 10 12:56:04 aws-beta-coreos-04 etcd2[758]: 2015/06/10 12:56:04 etcdserver: datadir is valid for the 2.0.1 format | |
Jun 10 12:56:05 aws-beta-coreos-04 systemd[1]: etcd2.service: main process exited, code=exited, status=1/FAILURE | |
Jun 10 12:56:05 aws-beta-coreos-04 systemd[1]: Unit etcd2.service entered failed state. | |
Jun 10 12:56:05 aws-beta-coreos-04 systemd[1]: etcd2.service failed. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment