whichdew commented on issue #331:
URL: https://github.com/apache/apisix-docker/issues/331#issuecomment-1181619625
> and error logs about this?
## apisix-dashboard
```shell
-> kubectl logs -f -n apisix apisix-dashboard-77555778bd-nxrl7
{"level":"warn","ts":"2022-07-12T10:52:24.819Z","caller":"clientv3/retry_interceptor.go:62","msg":"retrying
of unary invoker
failed","target":"endpoint://client-46296962-bb03-4456-b834-99a37783b207/apisix-etcd:2379","attempt":0,"error":"rpc
error: code = DeadlineExceeded desc = latest balancer error: all SubConns are
in TransientFailure, latest connection error: connection error: desc =
\"transport: Error while dialing dial tcp 10.110.249.227:2379: connect:
connection refused\""}
2022-07-12T10:52:24.820Z ERROR storage/etcd.go:147 etcd get
failed: context deadline exceeded
2022-07-12T10:52:24.820Z ERROR store/storehub.go:76 GenericStore
init error: etcd get failed: context deadline exceeded
2022-07-12T10:52:24.820Z ERROR server/store.go:32 init stores
fail: %!w(*errors.errorString=&{etcd get failed: context deadline exceeded})
2022-07-12T10:52:24.820Z ERROR cmd/root.go:79 The Manager API
server start failed: etcd get failed: context deadline exceeded
Error: etcd get failed: context deadline exceeded
```
## apisix-etcd
```
-> kubectl describe pod -n apisix apisix-etcd-0
Name: apisix-etcd-0
Namespace: apisix
Priority: 0
Node: pve/192.168.1.4
Start Time: Tue, 12 Jul 2022 17:26:37 +0800
Labels: app.kubernetes.io/instance=apisix
app.kubernetes.io/managed-by=Helm
app.kubernetes.io/name=etcd
controller-revision-hash=apisix-etcd-656bbf6ffc
helm.sh/chart=etcd-7.0.4
statefulset.kubernetes.io/pod-name=apisix-etcd-0
Annotations: checksum/token-secret:
61ac7b55e6de95aec1f7673faa1ca134b40fe1d997210cee87a864d934b3832e
Status: Running
IP: 10.244.0.68
IPs:
IP: 10.244.0.68
Controlled By: StatefulSet/apisix-etcd
Containers:
etcd:
Container ID:
containerd://fda489ccde5d81099a96eb0463e6affaf7e9d06a69f9db4ef6df65e42605bb42
Image: docker.io/bitnami/etcd:3.4.18-debian-10-r14
Image ID:
docker.io/bitnami/etcd@sha256:ce0f7334f0b31f341c0bcea4b9cec6fb1e37837400fd16c257f9f6e84e35192b
Ports: 2379/TCP, 2380/TCP
Host Ports: 0/TCP, 0/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 1
Started: Tue, 12 Jul 2022 18:55:14 +0800
Finished: Tue, 12 Jul 2022 18:57:17 +0800
Ready: False
Restart Count: 19
Liveness: exec [/opt/bitnami/scripts/etcd/healthcheck.sh]
delay=60s timeout=5s period=30s #success=1 #failure=5
Readiness: exec [/opt/bitnami/scripts/etcd/healthcheck.sh]
delay=60s timeout=5s period=10s #success=1 #failure=5
Environment:
BITNAMI_DEBUG: false
MY_POD_IP: (v1:status.podIP)
MY_POD_NAME: apisix-etcd-0 (v1:metadata.name)
MY_STS_NAME: apisix-etcd
ETCDCTL_API: 3
ETCD_ON_K8S: yes
ETCD_START_FROM_SNAPSHOT: no
ETCD_DISASTER_RECOVERY: no
ETCD_NAME: $(MY_POD_NAME)
ETCD_DATA_DIR: /bitnami/etcd/data
ETCD_LOG_LEVEL: info
ALLOW_NONE_AUTHENTICATION: yes
ETCD_AUTH_TOKEN:
jwt,priv-key=/opt/bitnami/etcd/certs/token/jwt-token.pem,sign-method=RS256,ttl=10m
ETCD_ADVERTISE_CLIENT_URLS:
http://$(MY_POD_NAME).apisix-etcd-headless.apisix.svc.cluster.local:2379,http://apisix-etcd.apisix.svc.cluster.local:2379
ETCD_LISTEN_CLIENT_URLS: http://0.0.0.0:2379
ETCD_INITIAL_ADVERTISE_PEER_URLS:
http://$(MY_POD_NAME).apisix-etcd-headless.apisix.svc.cluster.local:2380
ETCD_LISTEN_PEER_URLS: http://0.0.0.0:2380
ETCD_INITIAL_CLUSTER_TOKEN: etcd-cluster-k8s
ETCD_INITIAL_CLUSTER_STATE: new
ETCD_INITIAL_CLUSTER:
apisix-etcd-0=http://apisix-etcd-0.apisix-etcd-headless.apisix.svc.cluster.local:2380,apisix-etcd-1=http://apisix-etcd-1.apisix-etcd-headless.apisix.svc.cluster.local:2380,apisix-etcd-2=http://apisix-etcd-2.apisix-etcd-headless.apisix.svc.cluster.local:2380
ETCD_CLUSTER_DOMAIN:
apisix-etcd-headless.apisix.svc.cluster.local
Mounts:
/bitnami/etcd from data (rw)
/opt/bitnami/etcd/certs/token/ from etcd-jwt-token (ro)
/var/run/secrets/kubernetes.io/serviceaccount from
kube-api-access-cdttn (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
data:
Type: PersistentVolumeClaim (a reference to a
PersistentVolumeClaim in the same namespace)
ClaimName: data-apisix-etcd-0
ReadOnly: false
etcd-jwt-token:
Type: Secret (a volume populated by a Secret)
SecretName: apisix-etcd-jwt-token
Optional: false
kube-api-access-cdttn:
Type: Projected (a volume that contains injected data
from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional: <nil>
DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute
op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute
op=Exists for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 10m (x117 over 90m) kubelet Readiness probe
failed: command "/opt/bitnami/scripts/etcd/healthcheck.sh" timed out
Warning BackOff 6m45s (x229 over 85m) kubelet Back-off restarting
failed container
Warning Unhealthy 102s (x33 over 90m) kubelet Liveness probe failed:
command "/opt/bitnami/scripts/etcd/healthcheck.sh" timed out
```
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
