Yangzcy423911 commented on issue #3225: URL: https://github.com/apache/apisix/issues/3225#issuecomment-759866918
etcd start etcd --cert-file=server.pem --key-file=server-key.pem --advertise-client-urls=https://127.0.0.1:2379 --listen-client-urls=https://127.0.0.1:2379 log raft2021/01/09 11:15:15 INFO: 8e9e05c52164694d is starting a new election at term 7 raft2021/01/09 11:15:15 INFO: 8e9e05c52164694d became candidate at term 8 raft2021/01/09 11:15:15 INFO: 8e9e05c52164694d received MsgVoteResp from 8e9e05c52164694d at term 8 raft2021/01/09 11:15:15 INFO: 8e9e05c52164694d became leader at term 8 raft2021/01/09 11:15:15 INFO: raft.node: 8e9e05c52164694d elected leader 8e9e05c52164694d at term 8 2021-01-09 11:15:15.560528 I | etcdserver: published {Name:default ClientURLs:[https://127.0.0.1:2379]} to cluster cdf818194e3a8c32 2021-01-09 11:15:15.560639 I | embed: ready to serve client requests 2021-01-09 11:15:15.562946 I | embed: serving client requests on 127.0.0.1:2379 local test curl -k https://127.0.0.1:2379/version {"etcdserver":"3.4.13","etcdcluster":"3.4.0"} apisix test error about config etcd: host: # it's possible to define multiple etcd hosts addresses of the same etcd cluster. - "https://127.0.0.1:2379" # multiple etcd address, if your etcd cluster enables TLS, please use https scheme, # e.g. "https://127.0.0.1:2379". prefix: "/apisix" # apisix configurations prefix timeout: 30 # 30 seconds user: "root" # root username for etcd password: "123456" # root password for etcd apisix restart nginx: [error] open() "/usr/local/apisix/logs/nginx.pid" failed (2: No such file or directory) got malformed version message: "" from etcd etcd log 2021-01-09 11:17:01.293987 I | embed: rejected connection from "127.0.0.1:52492" (error "remote error: tls: unknown certificate authority", ServerName "") This is a mini case , you have try it Thanks ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
