-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
live-0-6dcff4f549-rvm6h pod failed occasionally #196
Comments
make parameters: |
we meet this issue in high reproduce rate. |
The cause of this bug has been found. But after solving this problem, We found that there is a certain probability that a new problem will occur in the deployment of CDN in a multi-machine environment : Result: error pod logs: |
HW: ICE,SKY
OS: CentOS 8.3.2011,RHEL 8.3, ubuntu,
Case:CIR_BMRA_RegionDC_CDN_Xeon
Command:ansible-playbook -i cdn_inventory.ini playbooks/cir.yml --extra-vars "profile=basic"
Result:
kubectl get pod -A*
NAMESPACE NAME READY STATUS RESTARTS AGE
default cdn-8668b855ff-7rqrt 1/1 Running 0 106s
default kafka-5b4b8845bc-wsv5b 1/1 Running 1 106s
default live-0-6dcff4f549-rvm6h 0/1 CrashLoopBackOff 4 105s
default redis-54fbcb48dd-ttb98 1/1 Running 0 106s
default vod-0-b7cddccdd-qlxrn 1/1 Running 0 106s
default vod-0-b7cddccdd-zfrhc 1/1 Running 0 106s
default zookeeper-674686784d-dz4xt 1/1 Running 0 106s
kube-system coredns-7677f9bb54-h8wck 1/1 Running 2 29m
kube-system coredns-7677f9bb54-qkjrw 1/1 Running 1 29m
kube-system dns-autoscaler-5b7b5c9b6f-hv6hd 1/1 Running 1 29m
kube-system docker-registry-docker-registry-545dd99446-5x8p4 2/2 Running 0 26m
kube-system kube-apiserver-aq09-00-wc 1/1 Running 0 106s
kube-system kube-controller-manager-aq09-00-wc 1/1 Running 4 31m
kube-system kube-flannel-jm7hf 1/1 Running 1 30m
kube-system kube-flannel-qhwmr 1/1 Running 1 30m
kube-system kube-multus-ds-amd64-52pm6 1/1 Running 1 29m
kube-system kube-multus-ds-amd64-hbmqf 1/1 Running 1 29m
kube-system kube-proxy-qmfjp 1/1 Running 1 30m
kube-system kube-proxy-sgqwt 1/1 Running 2 30m
kube-system kube-scheduler-aq09-00-wc 1/1 Running 1 19m
kube-system kubernetes-dashboard-86c6f9df5b-pvgxn 1/1 Running 2 29m
kube-system kubernetes-metrics-scraper-678c97765c-9fm99 1/1 Running 2 29m
kube-system nginx-proxy-ar09-07-cyp 1/1 Running 2 30m
kube-system node-feature-discovery-controller-5bf5c49849-q4knn 1/1 Running 0 22m
kube-system node-feature-discovery-worker-skh7d 1/1 Running 0 22m
monitoring collectd-tn28r 3/3 Running 0 18m
monitoring node-exporter-c4bw8 2/2 Running 0 21m
monitoring node-exporter-fdgmx 2/2 Running 0 21m
monitoring prometheus-k8s-0 5/5 Running 1 21m
monitoring prometheus-operator-5bb8cb9d8f-4nkd9 2/2 Running 0 21m
monitoring tas-telemetry-aware-scheduling-575ccbc9d4-p5dd4 2/2 Running 4 19m
Error log for this issue:
Events:
Type Reason Age From Message
Warning FailedScheduling 47s default-scheduler 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
Warning FailedScheduling 47s default-scheduler 0/2 nodes are available: 2 pod has unbound immediate PersistentVolumeClaims.
Normal Scheduled 45s default-scheduler Successfully assigned default/live-0-6dcff4f549-rj7g2 to av09-07-wp
Normal AddedInterface 44s multus Add eth0 [10.244.1.25/24]
Normal Pulled 24s (x3 over 44s) kubelet Container image "tc_transcode_xeon:latest" already present on machine
Normal Created 24s (x3 over 44s) kubelet Created container live-0
Normal Started 24s (x3 over 43s) kubelet Started container live-0
Warning BackOff 10s (x4 over 39s) kubelet Back-off restarting failed container
[root@av09-06-wp build]# kubectl logs live-0-6dcff4f549-rj7g2
ffmpeg version 4.2.2 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 7 (Ubuntu 7.5.0-3ubuntu1~18.04)
configuration: --prefix=/usr/local --libdir=/usr/local/lib --enable-shared --disable-static --disable-doc --disable-htmlpages --disable-manpages --disable-podpages --disable-txtpages --extra-cflags=-w --enable-gpl --enable-nonfree --enable-libass --enable-libfreetype --disable-xlib --disable-sdl2 --disable-hwaccels --disable-vaapi --enable-libv4l2 --enable-indev=v4l2 --enable-libopus --enable-libvpx --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libsvtav1 --enable-libsvthevc --enable-libsvtvp9 --enable-libdav1d
libavutil 56. 31.100 / 56. 31.100
libavcodec 58. 54.100 / 58. 54.100
libavformat 58. 29.100 / 58. 29.100
libavdevice 58. 8.100 / 58. 8.100
libavfilter 7. 57.100 / 7. 57.100
libswscale 5. 5.100 / 5. 5.100
libswresample 3. 5.100 / 3. 5.100
libpostproc 55. 5.100 / 55. 5.100
Input #0, mov,mp4,m4a,3gp,3g2,mj2, from '/var/www/archive/3115738.mp4':
Metadata:
major_brand : mp42
minor_version : 0
compatible_brands: mp42mp41isomavc1
creation_time : 2019-10-22T12:48:08.000000Z
Duration: 00:00:18.79, start: 0.000000, bitrate: 25358 kb/s
Stream #0:0(und): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709), 3840x2160, 25102 kb/s, 24 fps, 24 tbr, 24 tbn, 48 tbc (default)
Metadata:
creation_time : 2019-10-22T12:48:08.000000Z
handler_name : L-SMASH Video Handler
encoder : AVC Coding
Stream #0:1(und): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 253 kb/s (default)
Metadata:
creation_time : 2019-10-22T12:48:08.000000Z
handler_name : L-SMASH Audio Handler
rtmp://cdn-service/dash/media_0_1: Input/output error
The text was updated successfully, but these errors were encountered: