大家好,
我一直从我一直在玩的4个节点社区集群中遇到了这个错误,但不知道如何解决。
2017.07.20
看着Zookeeper,看来动物园管理员只能在3个节点上运行(因为它需要奇怪或可能是什么?)
但是我只在Zookeeper配置中看到了3个节点。
这是正确的吗?
我该怎么做才能停止出现此错误消息?
我尝试在每个节点上开始群集开始,但没有任何区别。
Nutanix对此错误消息说“联系支持”,但作为社区,这不是一个选择。
该主题已关闭以供评论
Zookeper在3个节点上运行,无论您可能拥有多少节点。
如果RF3,则Zookeeper将在5个节点上运行
群集状态如何?
太好了,那就是我想维持法定人数的想法。
这就是令人困惑的。
数据弹性表明还可以。
服务给我红色1
红色错误是针对“所有CVM上的Zookeeper Active”,但没有说出它不在运行的内容。和集群状态
警告警报说“ Zookeeper在所有CVM上都不活跃”
集群状态表示一切都在起来。
2018-09-24 09:09:31信息zookeeper_session.py:102集群正在尝试连接到Zookeeper
2018-09-24 09:09:31信息群集:2214在SVMS上执行操作状态10.0.1.1.111,10.1.1.1.112,112,10.1.1.113,10.1.1.114
群集的状态:开始
锁定模式:禁用
CVM:10.0.1.111 UP
宙斯UP [3115,3144,3145,3146,3226,3242]
清道夫[4122,4149,4150,4151]
sslterminator [4687,4718,4719,4720]
SecureFileSync UP [4692,4742,4743,4744]
Medusa UP [5548,5576,5577,18620,18837]
DynamicringChanger UP [5740,5786,5787,18580]
Pithos UP [5745,5808,5809,17746]
Hera Up [5769,5823,5824,5825]
Stargate UP [5951,5983,5984,6364,19172]
Insightsdb UP [5968,6015,6016,18565]
Insightsdatatransfer [5987,6040,6041,17992,17993]
Ergon UP [6020,6066,6067,17301]
Cerebro UP [6062,6163,6164,18597]
Chronos UP [6078,6197,6198,18127]
策展人UP [6104,6247,6248,18257]
Prism UP [6249,6310,6311,18575,20303,20306]
CIM UP [6257,6315,6316,6389]
AlertManager UP [6282,6350,6351,18585]
Arithmos UP [6338,6386,6387,18616]
Acrocolis UP [6395,6461,6462,18337]
Uhura UP [6422,6531,6533,17337]
SNMP UP [6472,6558,6559,15619]
sysstatcollector UP [6525,6580,6581,6582]
隧道向上[6566,6607,6608]
ClusterHealth UP [6603,6725,6726,17956,17978,17979,19816,23847,23848]
Janus UP [6614,6640,6641]
NutanixGuestTools [6657,6824,6825,17980]
Minervacvm UP [7013,7095,7096,7102,7574]
clusterConfig [7026,7238,7239,7243]
Abac UP [7047,7244,7245,17302]
Aplosengine UP [7087,7252,7253,15632]
APLOS UP [7382,7420,7421,7422,18418,18419]
Lazan UP [7402,7460,7461,20410]
Orion Up [7432,7475,7476,7504]
CVM:10.0.1.112 UP
宙斯UP [3081,3110,3111,3112]
清道夫[4038,4065,4066,4067]
SSLTERMINATOR [4952,4987,4988,4989]
SecureFileSync UP [4957,5008,5009,5010]
Medusa UP [854,1289,5394,5422,5423]
DynamicringChanger UP [651,5577,5608,5609]
Pithos UP [578,5582,5634,5635]
Hera Up [5622,5660,5661,5662]
Stargate UP [2208,5788,5821,5822,6096]
Insightsdb UP [1176,5800,5848,5849]
Insightsdatatransfer [587,588,5836,5877,5878]
Ergon UP [357,5858,5903,5904]
Cerebro UP [1197,5900,5934,5935]
Chronos UP [934,5917,5962,5963]
策展人UP [1422,5950,5998,5999]
Prism UP [1210,3063,3146,6002,6032,6033]
CIM UP [6024,6070,6071,6132]
AlertManager UP [1187,6048,6094,6095]
Arithmos UP [1221,6109,6140,6141]
Acrocolis UP [892,6168,6220,6229]
Uhura UP [539,6219,6295,6296]
SNMP UP [6253,6324,6325,31231]
sysstatcollector UP [6305,6352,6353,6354]
隧道向上[6340,6379,6380]
ClusterHealth UP [313,335,336,2622,6376,6525,6526,11810,11811]
Janus UP [6384,6413,6414]
NutanixGuestTools [925,6417,6518,6520]
Minervacvm UP [6736,6896,6897,31230,31351]
clusterConfig [6889,6941,6942,6945]
Abac UP [1421,6917,6975,6976]
Aplosengine UP [6939,7015,7016,31228]
APLOS UP [1141,1142,7126,7165,7166,7170]
Lazan UP [2822,7151,7191,7192]
Orion Up [7198,7223,7224,7234]
CVM:10.0.1.113 UP,Zeusleader
宙斯UP [3061,3090,3091,3092,3164,3180]
清道夫[4083,4110,4111,4112]
SSLTERMINATOR [4542,4572,4573,4574]
SecureFileSync UP [4560,4599,4600,4601]
Medusa UP [5448,5476,5477,30571,31028]
DynamicringChanger UP [5630,5675,5676,30807]
Pithos UP [5635,5714,5715,30812]
Hera Up [5649,5709,5710,5711]
Stargate UP [5845,5956,5957,6204,32177]
Insightsdb UP [5887,5992,5993,30833]
Insightsdatatransfer [5994,6023,6024,30864,30865]
Ergon UP [6011,6047,6048,31154]
Cerebro UP [6051,6084,6085,30820]
Chronos UP [6062,6117,6118,30829]
策展人UP [6102,6162,6163,31090]
Prism UP [487,6151,6198,6199,19616,30872]
CIM UP [6189,6273,6274,6361]
AlertManager UP [6208,6294,6295,30843]
Arithmos UP [6291,6405,6406,30881]
Acrocolis UP [759,6367,6487,6488]
Uhura UP [6381,6583,6584,30171]
SNMP UP [6421,6562,6563,28353]
sysstatcollector UP [6506,6612,6613,6614]
隧道向上[6549,6637,6638]
ClusterHealth UP [4516,4517,6567,6681,6682,29986,30008,30009,32260]
Janus UP [6582,6709,6710]
NutanixGuestTools UP [6702,6765,6766,30760]
Minervacvm UP [6988,7053,7054,7058,7434]
clusterConfig [7001,7063,7064,7065]
Abac UP [7047,7105,7106,31075]
Aplosengine UP [7085,7132,7133,28413]
APLOS UP [7240,7294,7295,7297,30565,30566]
Lazan UP [810,811,7256,7321,7322,30191]
Orion Up [7282,7343,7344,7358]
CVM:10.0.1.114 UP
宙斯UP [2934,2963,2964,2965,3045,3061]
清道夫[4070,4097,4098,4099]
sslterminator [4588,4619,4620,4621]
SecureFileSync UP [4595,4643,4644,4645]
Medusa UP [5459,5487,5488,29909,30302]
DynamicringChanger UP [5634,5674,5675,30100]
Pithos UP [5639,5707,5708,30149]
Hera Up [5671,5718,5719,5720]
Stargate UP [5846,5876,5877,6153,31081]
Insightsdb UP [5869,5907,5908,30090]
Insightsdatatransfer [5890,5935,5936,30070,30071]
Ergon UP [5915,5961,5962,28867]
Cerebro UP [5954,5993,5994,30106]
Chronos UP [5974,6025,6026,30159]
策展人UP [5999,6059,6060,28909]
Prism UP [6051,6089,6090,30154,31771,31773]
CIM UP [6073,6125,6126,6193]
AlertManager UP [6103,6157,6158,30117]
Arithmos UP [6154,6191,6192,30165]
Acrocolis UP [6226,6264,6265,29818]
Uhura UP [6254,6341,6342,28932]
SNMP UP [6328,6429,6430,27087]
sysstatcollector UP [6371,6493,6494,6497]
隧道向上[6395,6514,6515]
ClusterHealth UP [6478,6684,6685,8427,8428,29163,29190,29191,31291]
Janus UP [6516,6543,6544]
NutanixGuestTools [6548,6576,6577,30077]
Minervacvm UP [6699,6821,6822,6826,7297]
clusterConfig [6709,6855,6856,6857]
Abac UP [6711,6807,6808,30355]
Aplosengine UP [6714,6771,6772,27109]
APLOS UP [7110,7170,7171,7172,29955,29959]
Lazan UP [7133,7211,7212,29075]
Orion Up [7151,7216,7217,7226]
2018-09-24 09:09:39信息群集:2325成功!
连接到10.0.1.112关闭。
你有尊敬的NCC吗?
知道Zookeeper状态
您会发现Zookeeper在哪里运行,看到 /etc /主机。
您应该看到所有CVM的 /etc /主机。
考虑到数据弹性表明一切都很好。和集群状态。
我认为您的集群很好。
您也应该ncc run_all
知道Zookeeper状态
代码:
ncc health_checks system_checks zkinfo_check_plugin
您会发现Zookeeper在哪里运行,看到 /etc /主机。
您应该看到所有CVM的 /etc /主机。
考虑到数据弹性表明一切都很好。和集群状态。
我认为您的集群很好。
您也应该ncc run_all
代码:
NCC Health_checks run_all
感谢那。这就是我得到的。
我看着那里,看到要运行动物园管理器的3个主机,似乎他们正在运行它吗?它至少显示了PID。
跑步:health_checks system_checks zkinfo_check_plugin
[==============================================] 100%
/health_checks/system_checks/zkinfo_check_plugin [失败]
------------------------------------------------------------------------------------------------------------------------+
zkinfo_check_plugin的详细信息:
节点10.0.1.114:
失败:所有动物园管理器服务器都不活跃。非活动服务器是ZK1:9876
警告:无法在9876查看Zookeeper Server ZK1的状态
有关ZKINFO_CHECK_PLUGIN上的详细信息,请参阅KB 1587(http://portal.nutanix.com/kb/1587)或与:ncc health_checks system_checks zkinfo_check_check_check_plugin
+------------------+
|状态|计数|
+------------------+
|失败|1 |
|总计|1 |
+------------------+
谢谢您的帮助。
也许生病尝试将节点重新启动一个小时后,看看它们是否再次快乐。
我看着那里,看到要运行动物园管理器的3个主机,似乎他们正在运行它吗?它至少显示了PID。
跑步:health_checks system_checks zkinfo_check_plugin
[==============================================] 100%
/health_checks/system_checks/zkinfo_check_plugin [失败]
------------------------------------------------------------------------------------------------------------------------+
zkinfo_check_plugin的详细信息:
节点10.0.1.114:
失败:所有动物园管理器服务器都不活跃。非活动服务器是ZK1:9876
警告:无法在9876查看Zookeeper Server ZK1的状态
有关ZKINFO_CHECK_PLUGIN上的详细信息,请参阅KB 1587(http://portal.nutanix.com/kb/1587)或与:ncc health_checks system_checks zkinfo_check_check_check_plugin
+------------------+
|状态|计数|
+------------------+
|失败|1 |
|总计|1 |
+------------------+
谢谢您的帮助。
也许生病尝试将节点重新启动一个小时后,看看它们是否再次快乐。
首先,在找到ZK1在主机文件中的位置之前,您应该在ZK1上执行此命令。
进而
如果看到相同的错误,请重新启动CVM。
进而
代码:
$ Genesis Stop Zookeeper
$ Genesis重新启动或$ cluster开始
如果看到相同的错误,请重新启动CVM。
*没有更改,第一个重新启动。
感谢分享信息!