found invalid file/dir fixtures under data dir /var/lib/etcd (Ignore this if you are upgrading etcd) Jul 11 08:13:19 localhost etcd: the server is already initialized for peers on https://192.168.3.162:2380 Jul
ec52139 fix: filter out invalid memory modules info coming from Talos nodes 8e87031 fix: bump loadbalancer timeout settings bc0ed26 feat: introduce websocket, HTTP requests monitoring 857401f feat: add HTTP logging (static, gateway), and websocket logging eb612a3 fix: do hard stop of events...
if err := CleanDir(etcdDataDir); err != nil { klog.Warningf("[reset] Failed to delete contents of the etcd directory: %q, error: %v", etcdDataDir, err) } else { fmt.Printf("[reset] Deleted contents of the etcd data directory: %v\n", etcdDataDir) } } } else { fmt.Printl...
{"level":"info","ts":"2022-07-11T12:57:37.491Z","caller":"flags/flag.go:113","msg":"recognized and used environment variable","variable-name":"ETCD_DATA_DIR","variable-value":"/bitnami/etcd/data"} {"level":"info","ts":"2022-07-11T12:57:37.491Z","caller":"flags/flag.go:1...
(under VMWare). The problem looked to be that kubeadm was starting etcd, which was looking up some name to figure out what interface to bind to. That name resolved to my ISPs catchall name-not-found IP- and etcd naturally couldn't bind to that IP, which meant it couldn't stay up,...
Allow non-WAL files in etcd --wal-dir directory. Previously, existing files such as lost+found in WAL directory prevent etcd server boot. Now, WAL directory that contains only lost+found or a file that's not suffixed with .wal is considered non-initialized. Fix ETCD_CONFIG_FILE env var...
extern const int ERROR_GRPC_OK; extern const int ERROR_GRPC_CANCELLED; extern const int ERROR_GRPC_UNKNOWN; extern const int ERROR_GRPC_INVALID_ARGUMENT; extern const int ERROR_GRPC_DEADLINE_EXCEEDED; extern const int ERROR_GRPC_NOT_FOUND; extern const int ERROR_GRPC_ALREADY_EXISTS; extern ...
./etcd -f -name machine0 -data-dir machine0 -cert-file=./fixtures/ca/server.crt -key-file=./fixtures/ca/server.key.insecureThere are a few new options we're using:-f - forces a new machine configuration, even if an existing configuration is found. (WARNING: data loss!) -cert-file...
{"errorCode":100,"message":"Key Not Found","cause":"/foo"} Watching a prefix We can watch a path prefix and get notifications if any key change under that prefix. In one terminal, we send a watch request: curl -L http://127.0.0.1:4001/v1/watch/foo ...
./etcd -f -name machine0 -data-dir machine0 -cert-file=./fixtures/ca/server.crt -key-file=./fixtures/ca/server.key.insecure There are a few new options we're using: -f - forces a new machine configuration, even if an existing configuration is found. (WARNING: data loss!) -cert-...