问题

策展人主人失败了

  • 2018年2月16日
  • 6回复
  • 9意见
T.
徽章 +3
大家好，
我有一个备份Nutanix群集（CE）的问题。没有虚拟机，它被配置为另一个Nutanix的远程站点。
我们遇到了策略主人的问题，拒绝从这个错误开始：

代码： 
检查失败：vdisk_config.to_remove（）&& vdisk_config.has_origination_vdisk_id（）&&！vdisk_config.has_parent_vdisk_id（）&&！vdisk_config.has_expect
_parent_vdisk_id（）vdisk_id：10045 vdisk_size：0 container_id：5961 params {} to_remove：true creation_time_usecs：1512563402344616变形_state：kimmutable closest_named_ancestor：“NFS：4611686018427394362
“vdisk_creator_loc：6 vdisk_creator_loc：3742 vdisk_creator_loc：1110281 nfs_file_name：”c72541c1-9e9b-4b4f-a35a-e8be379e61b7“may_be_parent：true parent_nfs_file_name_hint：”c72541c1-9e9b-4b4f-a35a-e8be379e61
B7“shell_vdisk：true chain_id：”\ 201 \ 226 \ 377 \ 355 {\ 315L％\ 245 \ 037 {\ 037 \ 360 \ 231 \ 204 \ 024“vdisk_uuid：”\ 251 \ 252 \ 027 \ 262 \ 364 \377E \ 000 \ 217pf％\ 354 \ 316 \ 323 \ 022“never_hosted：false


我删除了该磁盘的所有快照（C72541C1-9B-4B4F-A35A-E8BE379E61B7），该磁盘不再存在于存储容器中，但问题仍然存在。

可能是Cassandra上的问题，但我不知道它是如何创建的以及如何解决它。

我可以摧毁群集并丢失所有数据，但我想了解之前发生的事情。

有什么建议？
谢谢。
\r\nI have a problem with a backup nutanix cluster (CE). There are no VMs, it is configured as a remote site of another Nutanix.
\r\nWe are having problems with the curator master, which refuses to start with this error:
\r\n
\r\n
code:<\/b>
Check failed: vdisk_config.to_remove() && vdisk_config.has_originating_vdisk_id() && !vdisk_config.has_parent_vdisk_id() && !vdisk_config.has_expected
_parent_vdisk_id() vdisk_id: 10045 vdisk_size: 0 container_id: 5961 params { } to_remove: true creation_time_usecs: 1512563402344616 mutability_state: kImmutable closest_named_ancestor: \"NFS:4611686018427394362
\" vdisk_creator_loc: 6 vdisk_creator_loc: 3742 vdisk_creator_loc: 1110281 nfs_file_name: \"c72541c1-9e9b-4b4f-a35a-e8be379e61b7\" may_be_parent: true parent_nfs_file_name_hint: \"c72541c1-9e9b-4b4f-a35a-e8be379e61
b7\" shell_vdisk: true chain_id: \"\\201\\226\\377\\355{\\315L%\\245\\037{\\037\\360\\231\\204\\024\" vdisk_uuid: \"\\251\\252\\027\\262\\364\\377E\\000\\217Pf%\\354\\316\\323\\022\" never_hosted: false
<\/pre><\/div>
\r\n
\r\nI deleted all the snapshots for that disk (c72541c1-9e9b-4b4f-a35a-e8be379e61b7), which is no longer present in the storage container, but the problem persists.
\r\n
\r\nProbably the problem is on cassandra, but I have no idea how it was created and how to solve it. 
\r\n
\r\nI can destroy the cluster and lose all the data, but I'd like to understand what happened before.
\r\n
\r\nAny suggestions?
\r\nThanks.","quoteUsername":"tudamp","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
此主题已关闭征询意见

6回复

aluciani
UserLevel 7.
徽章 +34
你还有问题 @tudamp.还
在推特上关注我：https://twitter.com/angeloluciani
@tudamp<\/user-mention> ?","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
T.
徽章 +3
是的，错误仍在这里
P.
秩
UserLevel 3.
徽章 +4
@tudamp.该问题很可能是由于不一致的_shell_vdisk_config，导致策展仪崩溃和/或失败启动和运行（基于所附的代码）。
Vdisk_config文件下的一些vdisks可能会将其“shell_vdisk：”标志设置为“true”，同时没有“unixator_vdisk_id”值设置。这导致策展人进入崩溃的循环

我们可能需要运行一个修复脚本，可以纠正不一致性并提出策展程序服务。运行脚本需要支持的帮助。

以AOS解决了上述问题4.7.4和5.1上面如果AOS版本较旧，则可能会达到相同的。

希望信息有帮助！
@tudamp<\/user-mention> the issue is most likely due to inconsistent_shell_vdisk_configs which is causing the curator to crash and\/or failure to start and run (based on the code that you attached).
\r\nSome vdisks under the vdisk_config file may have their \"shell_vdisk:\" flag set to \"True\" while having no \"originator_vdisk_id\" value set. This causes Curator to enter a crashing loop
\r\n
\r\nWe might need to run a fix script which can correct the inconsistency and bring up the curator service. Running the script would need support assistance.
\r\n
\r\nThe above described issue is resolved in AOS 4.7.4<\/b> and 5.1 above<\/b> and you are likely to hit the same if the AOS version is older to this.
\r\n
\r\n Hope the information helps!","quoteUsername":"Prad_Math","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
T.
徽章 +3
@prad_math.谢谢（你的）信息。
这是一个CE安装，所以我们没有支持。
唯一的解决方案是销毁群集，重新安装/升级到最后一个版本？

再次感谢。
@Prad_Math<\/user-mention> thanks for the info.
\r\nThis is a CE installation, so we don't have support.
\r\nThe only solution is to destroy the cluster, re-install\/upgrade to the last version?
\r\n
\r\nThanks again.","quoteUsername":"tudamp","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
aluciani
UserLevel 7.
徽章 +34
关于这篇文章的想法 @primzy. @andrew_ct.
谢谢
在推特上关注我：https://twitter.com/angeloluciani
@Primzy<\/user-mention> @andrew_ct<\/user-mention>
\r\nThanks","quoteUsername":"aluciani","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Andrew_ct.
UserLevel 5.
徽章 +9
你好，
我只能猜到这里，但如果你可以摧毁群体没有伤害（取决于你的数据）我猜直接安装最新版本是最简单的解决方案，步骤越越好。
否则我会先尝试修复步骤。
\r\nI can only guess here, but if you can destroy the cluster without harm (depends on the data you have) I guess that directly installing the latest version would be the easiest solution, the fewer steps the better.
\r\nOtherwise I'd try repair steps first.","quoteUsername":"andrew_ct","translations":{"Common":{"like":"Like","unlike":"Unlike"},"Forum":{"Quote":"Quote","Share":"Share"}}}">
Learn more about our cookies.<\/a>","cookiepolicy.button":"Accept cookies","cookiepolicy.button.deny":"Deny all","cookiepolicy.link":"Cookie settings","cookiepolicy.modal.title":"Cookie settings","cookiepolicy.modal.content":"We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.<\/a>","cookiepolicy.modal.level1":"Basic
Functional","cookiepolicy.modal.level2":"Normal
Functional + analytics","cookiepolicy.modal.level3":"Complete
Functional + analytics + social media + embedded videos"}}}">
Baidu