一看就是和CM的guid有关系,所以就从这方面着手解决问题。 报错解决: [root@master var]#find/ -name cm_guid # 找到cm_guid这个文件所在的目录/opt/cm-5.15.1/lib/cloudera-scm-agent/cm_guid [root@master var]#rm-rf /opt/cm-5.15.1/lib/cloudera-scm-agent/cm_guid # 删除这个目录(所有节点) [ro...
[29/Apr/2019 10:35:16 +0000] 2754 MainThread agent ERROR Error, CM server guid updated, expected f4ec230a-2f55-460f-b132-cb45a16c3a1b, received 4760feb5-8e8c-416c-8337-2910fef890a0 [29/Apr/2019 10:35:18 +0000] 2754 MainThread agent INFO CM server guid: f4ec230a-2f55-460f...
[15/Oct/2019 14:46:51 +0000] 4516 MainThread agent ERROR Error, CM server guid updated, expected 8115403a-7f9c-463f-b6d4-45fed899215b, received 87bf3025-6565-4a83-851b-81cdcaa936b6 [15/Oct/2019 14:46:56 +0000] 4516 MainThread agent ERROR Error, CM server guid updated, expect...
需要确认 GUID 不匹配的原因。这可能是由于: 重新安装或更新 CM Server:在重新安装或更新 Cloudera Manager 时,如果没有正确清理旧的配置,可能会导致 GUID 不一致。 网络问题或配置错误:如果 CM Server 和 Agent 之间的通信存在问题,或者配置不正确,也可能导致此类错误。 3. 修改配置文件以恢复正确的 GUID 如果确...
cloudera-scm-agent.log 发现 Error, CM server guid updated, expected 52d0d6ec-debc-4ba3-931a-2393718ba0f7, received 163a18a5-3123-4ffe-ba47-c4334f29b60e 找到cm_guid这个文件所在的目录并删除 重新启动agent service cloudera-scm-agent restart 运行正常：
1 详细错误 2 解决,删除cm_guid然后重启服务 产生的原因是服务器以前作为集群节点安装过agent服务,再次使用时没有卸载干净。 解决办法: rm -rf /var/lib/cloudera-scm-agent/cm_guid service cloudera-scm-agent resta
"ERROR Error, CM server guid updated, expected 93c963d9-3566-4f25-847a-faffb020866b, received ba4e4402-6ab3-4cdc-a403-39415df12824" There is a 'cm_guid' file that is used by the Cloudera Manager (CM) server to know which host belong to it. It appears that this host may have...
Remove-CMDuplicateHardwareIdGuid Remove-CMDuplicateHardwareIdMacAddress Remove-CMEndpointProtectionPoint Remove-CMEnrollmentPoint Remove-CMEnrollmentProxyPoint Remove-CMExchangeServer Remove-CMFallbackStatusPoint Remove-CMFileReplicationRoute Remove-CMFolder Remove-CMGlobalCondition Remove-CMHardwareRequirement Remove...
GUID: 0000000a-0000-0000-c000-000000000000 This and Microsoft Intune Enrollment are needed to allow corporate devices to enrol into Intune/MEM without you ending up in a catch 22: You’ll be prompted to set up MFA during the enrollment of the phone, but won’t be able to set up MFA ...
Remove-CMDuplicateHardwareIdGuid Remove-CMDuplicateHardwareIdMacAddress Remove-CMEndpointProtectionPoint Remove-CMEnrollmentPoint Remove-CMEnrollmentProxyPoint Remove-CMExchangeServer Remove-CMFallbackStatusPoint Remove-CMFileReplicationRoute Remove-CMFolder Remove-CMGlobalCondition Remove-CMHardwareRequirement Remov...