Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- [root@ag-bastion-server logging-infra]# oc -n openshift-logging describe pods elasticsearch-cdm-ow0umgcw-1-8567cfdc98-45625
- Name: elasticsearch-cdm-ow0umgcw-1-8567cfdc98-45625
- Namespace: openshift-logging
- Priority: 0
- PriorityClassName: <none>
- Node: log0.openshift.redacted.io/10.21.21.47
- Start Time: Mon, 30 Mar 2020 02:27:08 -0400
- Labels: cluster-name=elasticsearch
- component=elasticsearch
- es-node-client=true
- es-node-data=true
- es-node-master=true
- node-name=elasticsearch-cdm-ow0umgcw-1
- pod-template-hash=8567cfdc98
- tuned.openshift.io/elasticsearch=true
- Annotations: k8s.v1.cni.cncf.io/networks-status:
- [{
- "name": "openshift-sdn",
- "interface": "eth0",
- "ips": [
- "10.130.0.53"
- ],
- "default": true,
- "dns": {}
- }]
- openshift.io/scc: restricted
- Status: Running
- IP: 10.130.0.53
- Controlled By: ReplicaSet/elasticsearch-cdm-ow0umgcw-1-8567cfdc98
- Containers:
- elasticsearch:
- Container ID: cri-o://02246907da01df4119a01397c11686d4c664351551dd55c24fdc15dc9f7a3a1e
- Image: registry.redhat.io/openshift4/ose-logging-elasticsearch5@sha256:89fd15bfb36a07b9e990cf963f1c822f3d2620ee553e49e4d8911d995a553e53
- Image ID: registry.redhat.io/openshift4/ose-logging-elasticsearch5@sha256:89fd15bfb36a07b9e990cf963f1c822f3d2620ee553e49e4d8911d995a553e53
- Ports: 9300/TCP, 9200/TCP
- Host Ports: 0/TCP, 0/TCP
- State: Running
- Started: Mon, 30 Mar 2020 02:27:17 -0400
- Ready: True
- Restart Count: 0
- Limits:
- memory: 2Gi
- cpu: 200m
- memory: 2Gi
- Readiness: exec [/usr/share/elasticsearch/probe/readiness.sh] delay=10s timeout=30s period=5s #success=1 #failure=3
- Environment:
- DC_NAME: elasticsearch-cdm-ow0umgcw-1
- NAMESPACE: openshift-logging (v1:metadata.namespace)
- KUBERNETES_TRUST_CERT: true
- SERVICE_DNS: elasticsearch-cluster
- CLUSTER_NAME: elasticsearch
- INSTANCE_RAM: 2Gi
- HEAP_DUMP_LOCATION: /elasticsearch/persistent/heapdump.hprof
- RECOVER_AFTER_TIME: 5m
- READINESS_PROBE_TIMEOUT: 30
- POD_LABEL: cluster=elasticsearch
- IS_MASTER: true
- HAS_DATA: true
- Mounts:
- /elasticsearch/persistent from elasticsearch-storage (rw)
- /etc/openshift/elasticsearch/secret from certificates (rw)
- /usr/share/java/elasticsearch/config from elasticsearch-config (rw)
- /var/run/secrets/kubernetes.io/serviceaccount from elasticsearch-token-96zth (ro)
- proxy:
- Container ID: cri-o://e0940c80420f634d69fdeb79f75ea7f17acd1b9ff5d589125d4988a7e4cffaa0
- Image: registry.redhat.io/openshift4/ose-oauth-proxy@sha256:975b577cf5f343207000b2fcd68c1b181d518a6669ab3727577978c29de6b482
- Image ID: registry.redhat.io/openshift4/ose-oauth-proxy@sha256:975b577cf5f343207000b2fcd68c1b181d518a6669ab3727577978c29de6b482
- Port: 60000/TCP
- Host Port: 0/TCP
- Args:
- --https-address=:60000
- --provider=openshift
- --upstream=https://127.0.0.1:9200
- --tls-cert=/etc/proxy/secrets/tls.crt
- --tls-key=/etc/proxy/secrets/tls.key
- --upstream-ca=/etc/proxy/elasticsearch/admin-ca
- --openshift-service-account=elasticsearch
- -openshift-sar={"resource": "namespaces", "verb": "get"}
- -openshift-delegate-urls={"/": {"resource": "namespaces", "verb": "get"}}
- --pass-user-bearer-token
- --cookie-secret=7Os2vyw4jXn03QNEHp0uSg==
- State: Running
- Started: Mon, 30 Mar 2020 02:27:17 -0400
- Ready: True
- Restart Count: 0
- Limits:
- memory: 64Mi
- Requests:
- cpu: 100m
- memory: 64Mi
- Environment: <none>
- Mounts:
- /etc/proxy/elasticsearch from certificates (rw)
- /etc/proxy/secrets from elasticsearch-metrics (rw)
- /var/run/secrets/kubernetes.io/serviceaccount from elasticsearch-token-96zth (ro)
- Conditions:
- Type Status
- Initialized True
- Ready True
- ContainersReady True
- PodScheduled True
- Volumes:
- elasticsearch-config:
- Type: ConfigMap (a volume populated by a ConfigMap)
- Name: elasticsearch
- Optional: false
- elasticsearch-storage:
- Type: EmptyDir (a temporary directory that shares a pod's lifetime)
- Medium:
- SizeLimit: <unset>
- certificates:
- Type: Secret (a volume populated by a Secret)
- SecretName: elasticsearch
- Optional: false
- elasticsearch-metrics:
- Type: Secret (a volume populated by a Secret)
- SecretName: elasticsearch-metrics
- Optional: false
- elasticsearch-token-96zth:
- Type: Secret (a volume populated by a Secret)
- SecretName: elasticsearch-token-96zth
- Optional: false
- QoS Class: Burstable
- Node-Selectors: kubernetes.io/os=linux
- node-role.kubernetes.io/logs=
- Tolerations: node.kubernetes.io/disk-pressure:NoSchedule
- node.kubernetes.io/memory-pressure:NoSchedule
- node.kubernetes.io/not-ready:NoExecute for 300s
- node.kubernetes.io/unreachable:NoExecute for 300s
- Events:
- Type Reason Age From Message
- ---- ------ ---- ---- -------
- Normal Scheduled 48m default-scheduler Successfully assigned openshift-logging/elasticsearch-cdm-ow0umgcw-1-8567cfdc98-45625 to log0.openshift.redacted.io
- Normal Pulled 48m kubelet, log0.openshift.redacted.io Container image "registry.redhat.io/openshift4/ose-logging-elasticsearch5@sha256:89fd15bfb36a07b9e990cf963f1c822f3d2620ee553e49e4d8911d995a553e53" already present on machine
- Normal Created 48m kubelet, log0.openshift.redacted.io Created container elasticsearch
- Normal Started 48m kubelet, log0.openshift.redacted.io Started container elasticsearch
- Normal Pulled 48m kubelet, log0.openshift.redacted.io Container image "registry.redhat.io/openshift4/ose-oauth-proxy@sha256:975b577cf5f343207000b2fcd68c1b181d518a6669ab3727577978c29de6b482" already present on machine
- Normal Created 48m kubelet, log0.openshift.redacted.io Created container proxy
- Normal Started 48m kubelet, log0.openshift.redacted.io Started container proxy
- Warning Unhealthy 47m (x5 over 47m) kubelet, log0.openshift.redacted.io Readiness probe failed: Elasticsearch node is not ready to accept HTTP requests yet [response code: 503]
- Warning Unhealthy 47m (x5 over 47m) kubelet, log0.openshift.redacted.io Readiness probe failed: cat: /opt/app-root/src/init_failures: No such file or directory
- Warning Unhealthy 44m (x4 over 48m) kubelet, log0.openshift.redacted.io Readiness probe failed: Elasticsearch node is not ready to accept HTTP requests yet [response code: 000]
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement