-
Notifications
You must be signed in to change notification settings - Fork 9.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"Error: context deadline exceeded" #8793
Comments
Did you check 3 other nodes in your cluster? Server logs should have some warnings? |
@dchambon Ping? |
Hi @gyuho , Sorry for the late reply. I manage to have my ETCD v3 cluster working. I actually changed the configuration to use the discovery mecanism and then it works. |
For etcd v3, if you didn't provide ca, key, cert for the client, then you would met the errors. (ref: https://zhuanlan.zhihu.com/p/47228920) |
@gemfield I cannot tell you how much this helped me running an |
@steaksauce- |
I'm not a developer (and do not know Go). I use the CLI options to pass in these options. Here is the example from the article that @gemfield provided: If I recall, I had to modify the options slightly because the CLI changed, but you should be able to run |
I needed to use etcdctl with etcd installed on CoreOS (Container Linux). In my case the following worked (executed from CoreOS shell prompt): $ sudo ETCDCTL_API=3 etcdctl --cacert /etc/ssl/etcd/etcd/peer-ca.crt --cert /etc/ssl/etcd/etcd/peer.crt --key /etc/ssl/etcd/etcd/peer.key get --prefix / --keys-only I used sudo as a quick solution to the permission problem "Error: open /etc/ssl/etcd/etcd/peer.crt: permission denied". |
Just to repeat and emphasize, this "context deadline exceeded" also happens (3.3.13) when using This is true even with This is unexpected because --auto-tls seems like a feature that "should just work" and there is no corresponding --auto-tls option for etcdctl. Overall etcd needs better error reporting for all TLS issues. "context deadline exceeded" is a meaningless error message, making troubleshooting difficult. |
if you are running on openstack or any cloud please make sure to allow the ports in security groups |
Summary
I am trying to build a simple etcd cluster using coreos from scratch.
Environment
To set up my VM, I am using the github script with the following command
My ignition file is valid and the associated configuration is:
Once my env is up and running, I have the following:
Issue
If I try to execute a simple etcdctl command. I have the following exception:
Log shows:
and journalctl:
So no explicit exceptions in the console. I tried to change the ETCDCTL_API but still an error is raised when I try to use etcd:
I guess I am doing something wrong with my configuration but I can't find out...
Thanks in advance for your help.
The text was updated successfully, but these errors were encountered: