(abc123)", event: &pleg.PodLifecycleEvent{ID:"abc123", Type:"ContainerDied", Data:"def456"}SyncLoop(<em
浏览 2提问于2020-08-12得票数 0
1回答
"rule manager" group=kubelet.rules msg="Evaluating rule failed" rule="record: node_quantile:kubelet_pleg_relist_duration_seconds:histogram_quantile\nexpr: histogram_quantile(0.5, sum by(instance, le) (rate(kubelet_pleg_relist_duration_seconds_bucket:histogr
浏览 2提问于2021-05-04得票数 3
1回答
[Name]) INNER JOIN PLeg pjl ON pjl.InventoryLegID = il.InventoryLegID[Name])) INNER JOIN PLeg pjl ON pjl.InventoryLegID = il.InventoryLegID[Name])) INNER JOIN PLeg pjl ON pjl.InventoryLe
浏览 8提问于2022-06-07得票数 -1
回答已采纳
Sat, 19 Nov 2022 17:17:30 -0600 Fri, 18 Nov 2022 11:03:06 -0600 KubeletNotReady PLEGis not healthy: pleg was last seen active 30h17m27.791101751s ago; threshold is 3m0s
如何互传这些信息？
浏览 20提问于2022-11-19得票数 0
昨天晚上，我的Kubernetes集群终止了我的2个节点，我不知道具体发生了什么。Conditions:---- ------ ----------------- ---------
浏览 0提问于2018-09-05得票数 0
goroutine 386 [chan send, 1140 minutes]:
k8s.io/kubernetes/pkg/kubelet/pleg.beta.0.24+753b2dbc622f5c/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/kubelet/pleg/generic.go:26
浏览 1提问于2019-06-17得票数 0
回答已采纳
1回答
中的各种并发健康错误(这种类型的条目很多，很多)：12:53:18.126428 1036LastTransitionTime:2019-08-09 12:53:18.126363615 +0000 UTC m=+3924434.1879528
浏览 1提问于2019-08-09得票数 1
): "k8s-master-192.168.1.84_default(9391883ad78c50e752d5748347ef9aa2)", event: &pleg.PodLifecycleEvent): "k8s-master-192.168.1.84_default(9391883ad78c50e752d5748347ef9aa2)", event: &pleg.PodLifecycleEvent): "k8s-master-192.168.1.84_default(9391883ad
浏览 2提问于2016-06-08得票数 0
1回答
但是大约10个小时后，节点变为'not ready‘，并且节点describe向我显示两个错误:1.容器运行时关闭，PLEG不健康: 1h32m35.942907195s前，pleg最后一次看到活动状态55 +0000 Wed, 19 Dec 2018 19:27:24 +0000 KubeletNotReady container runtime is down,PLEGis not healthy: pleg was lastseen active 1h32m35.94290
浏览 132提问于2018-12-21得票数 8
Node0296 kubelet[2283]: I1228 23:59:02.205026 2283 kubelet.go:1823] skipping pod synchronization - PLEGis not healthy: pleg was last seen active 3m0.611016853s ago; threshold is 3m0s. docker日志： DEC 28 23
浏览 74提问于2019-12-31得票数 0
回答已采纳
1回答
我已经有了一种组合两张数据的工作方法；但是，它比我所希望的要慢一些。我想知道是否有人知道更快的合并数据的方法。我需要将两者结合起来，以便将第2页中的乘客和货物信息添加到第1页任务的正确部分。这使我对该任务有一个完整、详细的看法。我将这些数
浏览 2提问于2015-08-21得票数 0
回答已采纳
对主实例上的kubelet日志的研究显示了重复的错误，与首次发现故障的时间相吻合：
I0805 03:17:54.597295 2730 kubelet.go:1928] SyncLoop (PLEG): "kube-scheduler-ip-x-x-x-x.z-west-y.compute.internal_kube-system(181xxyyzz)", event: &pleg.PodLifecycleEvent
浏览 2提问于2020-08-11得票数 1
ffffffffffffffffffffffffffffffff"
MESSAGE: "I0203 22:41:11.925928 1843 kubelet.go:1816] SyncLoop (PLEG): "pnovotnak-manhole-123456789-82l2h_test(a-uuid)", event: &pleg.PodLifecycleEvent{ID:"another-uuid"
浏览 0提问于2017-02-03得票数 9
警告ContainerGCFailed是问题所在，还是应该由我来调查： PLEG is not healthy: pleg was last seen active 4m19.322678359s agoWed, 18 Nov 2020 14:36:56 +1100 Wed, 18 Nov 2020 14:35:45 +1100 KubeletNotReady PLEGis not healthy: pleg was last seen active 4m19.322678359s ago
浏览 52提问于2020-11-18得票数 0
2回答
post.pledge_amount}}</td> <td>{{post.pledge_date}}</td>
我正在尝试从数组中获取client_id pleg_fname
浏览 0提问于2015-06-14得票数 2
回答已采纳
Fri, 07 May 2021 16:14:05 +0100 Fri, 07 May 2021 16:11:05 +0100 KubeletNotReady PLEGis not healthy: pleg was last seen active 6m22.485400578s ago; threshold is 3m0s InternalIP因为集群也很大 CPU: 5GBSWAP: 1GB
Disk Image: 60GB 机器: Mac Core i7，32 G
浏览 2499提问于2021-05-10得票数 1
2回答
): "kube-dns-v20-765f4cf698-zlms6_kube-system(1d10753c-ee18-11e8-a6f7-000d3a727bf3)", event: &pleg.PodLifecycleEvent): "kube-dns-v20-3003781527-lw6p9_kube-system(1cf6caec-ee18-11e8-a6f7-000d3a727bf3)", event: &pleg.PodLifecycleEvent16:52:43 k8s-agent-CA5
浏览 0提问于2018-11-14得票数 2
1870] "Skipping pod synchronization" err="[container runtime status check may not have completed yet, PLEGis not healthy: pleg has yet to be successful]"
I1021 12:04:55.571567 78816 shared_informer.go:247
浏览 0提问于2021-10-21得票数 1
回答已采纳
kubelet.go:1846] skipping pod synchronization - [container runtime status check may not have completed yet PLEGis not healthy: pleg has yet to be successful]
I0117 14:31:27.623347 2841 server.go:137] Startingkubelet.go:1846] skipping pod synchronization - [container runtime stat
浏览 1082提问于2019-01-17得票数 0
回答已采纳
07 02:44:46 ip-172-21-56-148 kubelet[1568]: I0107 02:44:46.592800 1568 kubelet.go:1917] SyncLoop (PLEG): "slotmachine-1688723297-sk8bn_cog-prod01(2bc8665e-30f5-11ea-a92d-024aeca0bafc)", event: &pleg.PodLifecycleEvent07 02:45:00 ip-172-21-56-148 kubelet[1568]: I0107
浏览 34提问于2020-01-07得票数 2
回答已采纳
扫码
添加站长 进交流群
领取专属 10元无门槛券
手把手带您无忧上云
相关资讯
热门标签
云服务器
ICP备案
对象存储
腾讯会议
实时音视频活动推荐
腾讯云开发者
