实战

回到首页 个人中心 反馈问题 注册登录
下载APP
首页 课程 实战 体系课 手记 专栏 慕课教程

nodeport边缘端纳管异常certificate is valid for:xxx

来源：4-4 cloudcore通过Deployment的方式运行

慕斯卡5536101

2022-12-10

老师用空帮忙看下，nodeport方式边缘纳管异常，详细信息如下

12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: F1210 22:57:46.350924 32522 certmanager.go:93] Error: failed to get edge certificate from the cloudcore, error: Get “https://192.168.255.53:30002/edge.crt”: x509: certificate is valid for 10.164.207.77, not 192.168.255.5
图片描述

图片描述图片描述

12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.933569   32522 server.go:70] Version: v1.8.2
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.937832   32522 sql.go:21] Begin to register twin db model
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.938063   32522 module.go:34] Module twin registered successfully
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.946959   32522 client.go:78] "Connecting to docker on the dockerEndpoint" endpoint="unix:///var/run/docker.sock"
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.947474   32522 client.go:97] "Start docker client with request timeout" timeout="0s"
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.960472   32522 docker_service.go:242] "Hairpin mode is set" hairpinMode=hairpin-veth
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.960675   32522 cni.go:239] "Unable to update cni config" err="no networks found in /etc/cni/net.d"
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.971800   32522 hostport_manager.go:72] "The binary conntrack is not installed, this can cause failures in network connection cleanup."
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.971816   32522 hostport_manager.go:72] "The binary conntrack is not installed, this can cause failures in network connection cleanup."
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.973859   32522 docker_service.go:257] "Docker cri networking managed by the network plugin" networkPluginName="kubernetes.io/no-op"
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.984306   32522 docker_service.go:264] "Docker Info" dockerInfo=&{ID:MUAZ:RIWF:T2FL:XFYS:6A6P:MNXJ:LTDI:KTKW:GZW2:ZBD3:OYP2:C35J Containers:0 ContainersRunning:0 ContainersPaused:0 ContainersStopped:0 Images:9 Driver:overlay2 DriverStatus:[[Backing Filesystem xfs] [Supports d_type true] [Native Overlay Diff true] [userxattr false]] SystemStatus:[] Plugins:{Volume:[local] Network:[bridge host ipvlan macvlan null overlay] Authorization:[] Log:[awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog]} MemoryLimit:true SwapLimit:true KernelMemory:true KernelMemoryTCP:true CPUCfsPeriod:true CPUCfsQuota:true CPUShares:true CPUSet:true PidsLimit:true IPv4Forwarding:true BridgeNfIptables:true BridgeNfIP6tables:true Debug:false NFd:25 OomKillDisable:true NGoroutines:36 SystemTime:2022-12-10T22:57:45.97480844+08:00 LoggingDriver:json-file CgroupDriver:cgroupfs CgroupVersion:1 NEventsListener:0 KernelVersion:3.10.0-693.el7.x86_64 OperatingSystem:CentOS Linux 7 (Core) OSVersion:7 OSType:linux Architecture:x86_64 IndexServerAddress:https://index.docker.io/v1/ RegistryConfig:0xc0000f9ea0 NCPU:1 MemTotal:2080653312 GenericResources:[] DockerRootDir:/var/lib/docker HTTPProxy: HTTPSProxy: NoProxy: Name:vms131.rhce.cc Labels:[] ExperimentalBuild:false ServerVersion:20.10.21 ClusterStore: ClusterAdvertise: Runtimes:map[io.containerd.runc.v2:{Path:runc Args:[] Shim:<nil>} io.containerd.runtime.v1.linux:{Path:runc Args:[] Shim:<nil>} runc:{Path:runc Args:[] Shim:<nil>}] DefaultRuntime:runc Swarm:{NodeID: NodeAddr: LocalNodeState:inactive ControlAvailable:false Error: RemoteManagers:[] Nodes:0 Managers:0 Cluster:<nil> Warnings:[]} LiveRestoreEnabled:false Isolation: InitBinary:docker-init ContainerdCommit:{ID:770bd0108c32f3fb5c73ae1264f7e503fe7b2661 Expected:770bd0108c32f3fb5c73ae1264f7e503fe7b2661} RuncCommit:{ID:v1.1.4-0-g5fd4c4d Expected:v1.1.4-0-g5fd4c4d} InitCommit:{ID:de40ad0 Expected:de40ad0} SecurityOptions:[name=seccomp,profile=default] ProductLicense: DefaultAddressPools:[] Warnings:[]}
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.984324   32522 docker_service.go:277] "Setting cgroupDriver" cgroupDriver="cgroupfs"
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.984360   32522 edged.go:690] RemoteRuntimeEndpoint: "unix:///var/run/dockershim.sock", remoteImageEndpoint: "unix:///var/run/dockershim.sock"
12月 10 22:57:45 vms131.rhce.cc edgecore[32522]: I1210 22:57:45.984363   32522 edged.go:693] Starting the GRPC server for the docker CRI shim.
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067270   32522 remote_runtime.go:62] parsed scheme: ""
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067295   32522 remote_runtime.go:62] scheme "" not registered, fallback to default scheme
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067326   32522 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/run/dockershim.sock  <nil> 0 <nil>}] <nil> <nil>}
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067342   32522 clientconn.go:948] ClientConn switching balancer to "pick_first"
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067393   32522 remote_image.go:50] parsed scheme: ""
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067401   32522 remote_image.go:50] scheme "" not registered, fallback to default scheme
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067410   32522 passthrough.go:48] ccResolverWrapper: sending update to cc: {[{/var/run/dockershim.sock  <nil> 0 <nil>}] <nil> <nil>}
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.067415   32522 clientconn.go:948] ClientConn switching balancer to "pick_first"
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.229835   32522 kuberuntime_manager.go:222] "Container runtime initialized" containerRuntime="docker" version="20.10.21" apiVersion="1.41.0"
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.229883   32522 edged.go:575] --cgroups-per-qos enabled, but --cgroup-root was not specified.  defaulting to /
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248069   32522 container_manager_linux.go:278] "Container manager verified user specified cgroup-root exists" cgroupRoot=[]
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248127   32522 container_manager_linux.go:283] "Creating Container Manager object based on Node Config" nodeConfig={RuntimeCgroupsName: SystemCgroupsName: KubeletCgroupsName: ContainerRuntime:docker CgroupsPerQOS:true CgroupRoot:/ CgroupDriver:cgroupfs KubeletRootDir:/var/lib/edged ProtectKernelDefaults:false NodeAllocatableConfig:{KubeReservedCgroupName: SystemReservedCgroupName: ReservedSystemCPUs: EnforceNodeAllocatable:map[] KubeReserved:map[] SystemReserved:map[] HardEvictionThresholds:[]} QOSReserved:map[] ExperimentalCPUManagerPolicy:none ExperimentalTopologyManagerScope:container ExperimentalCPUManagerReconcilePeriod:0s ExperimentalMemoryManagerPolicy: ExperimentalMemoryManagerReservedMemory:[] ExperimentalPodPidsLimit:0 EnforceCPULimits:false CPUCFSQuotaPeriod:0s ExperimentalTopologyManagerPolicy:none}
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248153   32522 topology_manager.go:120] "Creating topology manager with policy per scope" topologyPolicyName="none" topologyScopeName="container"
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248170   32522 container_manager_linux.go:314] "Initializing Topology Manager" policy="none" scope="container"
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248179   32522 container_manager_linux.go:319] "Creating device plugin manager" devicePluginEnabled=false
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248281   32522 module.go:34] Module edged registered successfully
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248294   32522 module.go:34] Module websocket registered successfully
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248304   32522 module.go:34] Module eventbus registered successfully
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248336   32522 metamanager.go:45] Begin to register metaManager db model
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.248381   32522 module.go:34] Module metaManager registered successfully
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: W1210 22:57:46.248390   32522 module.go:37] Module servicebus is disabled, do not register
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: W1210 22:57:46.248401   32522 module.go:37] Module edgestream is disabled, do not register
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: W1210 22:57:46.248406   32522 module.go:37] Module testManager is disabled, do not register
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: table `device` already exists, skip
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: table `device_attr` already exists, skip
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: table `device_twin` already exists, skip
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: table `sub_topics` already exists, skip
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: table `meta` already exists, skip
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: table `meta_v2` already exists, skip
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.258737   32522 core.go:24] Starting module twin
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.258800   32522 core.go:24] Starting module edged
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.258889   32522 core.go:24] Starting module websocket
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.258940   32522 core.go:24] Starting module eventbus
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.258981   32522 core.go:24] Starting module metaManager
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.259779   32522 process.go:113] Begin to sync sqlite
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.260172   32522 edged.go:294] Starting edged...
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: E1210 22:57:46.260527   32522 csi_plugin.go:224] kubernetes.io/csi: CSIDriverLister not found on KubeletVolumeHost
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.260617   32522 fs_resource_analyzer.go:67] "Starting FS ResourceAnalyzer"
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.260874   32522 http.go:40] tlsConfig InsecureSkipVerify true
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.278483   32522 common.go:96] start connect to mqtt server with client id: hub-client-sub-1670684266
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.278505   32522 common.go:98] client hub-client-sub-1670684266 isconnected: false
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279254   32522 client.go:150] finish hub-client sub
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279275   32522 common.go:96] start connect to mqtt server with client id: hub-client-pub-1670684266
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279280   32522 common.go:98] client hub-client-pub-1670684266 isconnected: false
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279634   32522 client.go:166] finish hub-client pub
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279653   32522 eventbus.go:63] Init Sub And Pub Client for externel mqtt broker tcp://127.0.0.1:1883 successfully
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279741   32522 client.go:91] edge-hub-cli subscribe topic to $hw/events/upload/#
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.279969   32522 client.go:91] edge-hub-cli subscribe topic to $hw/events/device/+/state/update
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.280139   32522 client.go:91] edge-hub-cli subscribe topic to $hw/events/device/+/twin/+
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.280292   32522 client.go:91] edge-hub-cli subscribe topic to $hw/events/node/+/membership/get
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.280607   32522 client.go:91] edge-hub-cli subscribe topic to SYS/dis/upload_records
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.320332   32522 client.go:91] edge-hub-cli subscribe topic to +/user/#
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: I1210 22:57:46.320628   32522 client.go:99] list edge-hub-cli-topics status, no record, skip sync
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: F1210 22:57:46.350924   32522 certmanager.go:93] Error: failed to get edge certificate from the cloudcore, error: Get "https://192.168.255.53:30002/edge.crt": x509: certificate is valid for 10.164.207.77, not 192.168.255.53
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: goroutine 124 [running]:
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: k8s.io/klog/v2.stacks(0xc000010001, 0xc0002fa3c0, 0xe0, 0xe9)
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/vendor/k8s.io/klog/v2/klog.go:1021 +0xb9
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: k8s.io/klog/v2.(*loggingT).output(0x4656de0, 0xc000000003, 0x0, 0x0, 0xc0001a4770, 0x42ee3cc, 0xe, 0x5d, 0x0)
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/vendor/k8s.io/klog/v2/klog.go:970 +0x19b
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: k8s.io/klog/v2.(*loggingT).printf(0x4656de0, 0xc000000003, 0x0, 0x0, 0x0, 0x0, 0x2cc7bd2, 0x9, 0xc000587c00, 0x1, ...)
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/vendor/k8s.io/klog/v2/klog.go:751 +0x191
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: k8s.io/klog/v2.Fatalf(...)
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/vendor/k8s.io/klog/v2/klog.go:1509
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: github.com/kubeedge/kubeedge/edge/pkg/edgehub/certificate.(*CertManager).Start(0xc0008e5ba0)
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/edge/pkg/edgehub/certificate/certmanager.go:93 +0x12b
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: github.com/kubeedge/kubeedge/edge/pkg/edgehub.(*EdgeHub).Start(0xc0008e5ba0)
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/edge/pkg/edgehub/edgehub.go:65 +0x445
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: created by github.com/kubeedge/beehive/pkg/core.StartModules
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: /root/codes/src/github.com/kubeedge/kubeedge/vendor/github.com/kubeedge/beehive/pkg/core/core.go:23 +0x1f5
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: goroutine 1 [chan receive]:
12月 10 22:57:46 vms131.rhce.cc edgecore[32522]: github.com/kubeedge/beehive/pkg/core.GracefulShutdown()

根据老师指导排查结果：
1，[root@vms51 ~]# kubectl get svc -n kubeedge
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE
cloudcore NodePort 10.96.3.114 10000:30000/TCP,10002:30002/TCP 6d12h

NodePort: cloudhub 30000/TCP
Endpoints: 10.161.120.225:10000,10.164.207.90:10000
Port: certandreadyz 10002/TCP
TargetPort: 10002/TCP
NodePort: certandreadyz 30002/TCP
Endpoints: 10.161.120.225:10002,10.164.207.90:10002
2，ip设置为httpServer: https://192.168.255.51:30002， 51为k8s一个节点
3，token也更新过

这是cloudcore pod的报错
W1216 06:12:09.835902 1 iptables.go:88] failed to delete all rules in tunnel port iptables chain: error flushing chain “TUNNEL-PORT”: exit status 1: iptables: No chain/target/match by that name.
I1216 06:12:09.940341 1 server.go:258] Ca and CaKey don’t exist in local directory, and will read from the secret
I1216 06:12:10.030625 1 server.go:303] CloudCoreCert and key don’t exist in local directory, and will read from the secret
I1216 06:12:10.126615 1 signcerts.go:100] Succeed to creating token
I1216 06:12:10.126734 1 server.go:44] start unix domain socket server
I1216 06:12:10.139528 1 uds.go:71] listening on: //var/lib/kubeedge/kubeedge.sock
I1216 06:12:10.148294 1 server.go:64] Starting cloudhub websocket server
I1216 06:12:11.637157 1 upstream.go:63] Start upstream devicecontroller
I1217 05:11:05.361064 1 log.go:181] http: TLS handshake error from 10.161.49.0:1205: remote error: tls: bad certificate
I1217 05:11:16.246508 1 log.go:181] http: TLS handshake error from 10.161.49.0:3128: remote error: tls: bad certificate
I1217 05:11:26.788354 1 log.go:181] http: TLS handshake error from 10.161.49.0:47506: remote error: tls: bad certificate

写回答

1回答

暮闲

2022-12-17

排查一下：

  1. kubectl get svc -n kubeedge 查看有关kubedge的几个svc是否启动

  2. kubeedge云端IP是否指定正确

  3. 边缘端的token是否有更新，会不会是用到之前的token

0
1
慕斯卡5536101
老师，我把这几项排查结果追加到问题的最后了，这几项都没有问题
2022-12-17
共1条回复

云原生+边缘计算项目实战-KubeEdge打造边缘管理平台

抢位前沿技术，获得先发优势

258 学习 · 265 问题

查看课程

相似问题

请问边缘aI应用和边缘计算管理平台两个实战项目有联系吗？

回答 1

云端deploy删除了，但是边缘端容器一直up，即使在边缘端rm，rmi也没用

回答 1

这章没有说清楚边缘计算控制平台是部署在云端还是边缘端

回答 1

logs/exec节纳入边缘节点报错!~

回答 2

进行边缘AI模型升级时，向边缘端9443发送数据连接失败

回答 1

打开慕课网App查看更多内容