You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Existing open issues along with etcd frequently asked questions have been checked and this is not a duplicate.
What happened?
When trying to start an ETCd member with a unix socket for advertise peer url, or client urls the address is not accepted and required the url to be in host:port format.
etcd --name server0 --initial-advertise-peer-urls unix:///tmp/c139ad0d297f3e31eb4e517e7822aa64/test \
--listen-peer-urls unix:///tmp/c139ad0d297f3e31eb4e517e7822aa64/test \
--listen-client-urls http://127.0.0.1:2480 \
--advertise-client-urls http://127.0.0.1:2380 \
--initial-cluster-token wag-test \
--initial-cluster server0=unix:///tmp/c139ad0d297f3e31eb4e517e7822aa64/test
invalid value "unix:///tmp/c139ad0d297f3e31eb4e517e7822aa64/test"for flag -initial-advertise-peer-urls: URL address does not have the form "host:port": unix:///tmp/c139ad0d297f3e31eb4e517e7822aa64/test
Usage:
<omitted>
What did you expect to happen?
To be able to create a unix socket at any file location without requirement for the format host:port
How can we reproduce it (as minimally and precisely as possible)?
I don't believe that this has been fully resolved:
./etcd --listen-client-urls=unix:///tmp/socket \
--advertise-client-urls=unix:///tmp/socket
{"level":"warn","ts":"2024-09-04T12:32:54.642135-0700","caller":"embed/config.go:687","msg":"Running http and grpc server on single port. This is not recommended for production."}
{"level":"info","ts":"2024-09-04T12:32:54.642234-0700","caller":"etcdmain/etcd.go:73","msg":"Running: ","args":["./etcd","--listen-client-urls=unix:///tmp/socket","--advertise-client-urls=unix:///tmp/socket"]}
{"level":"warn","ts":"2024-09-04T12:32:54.642252-0700","caller":"etcdmain/etcd.go:75","msg":"failed to verify flags","error":"--advertise-client-urls \"unix:///tmp/socket\" must be \"host:port\" (missing port in address)"}
Bug report criteria
What happened?
When trying to start an ETCd member with a unix socket for advertise peer url, or client urls the address is not accepted and required the url to be in
host:port
format.What did you expect to happen?
To be able to create a unix socket at any file location without requirement for the format
host:port
How can we reproduce it (as minimally and precisely as possible)?
Anything else we need to know?
No response
Etcd version (please run commands below)
Etcd configuration (command line flags or environment variables)
etcd --name server0 --initial-advertise-peer-urls unix:///tmp/wag-c139ad0d297f3e31eb4e517e7822aa64/test
--listen-peer-urls unix:///tmp/wag-c139ad0d297f3e31eb4e517e7822aa64/test
--listen-client-urls http://127.0.0.1:2480
--advertise-client-urls http://127.0.0.1:2380
--initial-cluster-token wag-test
--initial-cluster server0=unix:///tmp/wag-c139ad0d297f3e31eb4e517e7822aa64/test
Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)
N/A
Relevant log output
No response
The text was updated successfully, but these errors were encountered: