Connecting Cloud Innovators: Building Community at .NEXT 2024
We moved a NX3000 to a new environment but one of the nodes died. So we had to reimage that node. The other two where still up and running. But after a power-failure on the rack, the two nodes rebooted but won't come up anymore. Genesis showing some failures:2016-08-18 14:38:40 INFO node_manager.py:3492 Svm has configured ip 10.160.35.124 and device eth0 has ip 10.160.35.1242016-08-18 14:38:43 INFO node_manager.py:3542 Setting up key based SSH access to host hypervisor for the first time...2016-08-18 14:38:43 INFO hypervisor_ssh.py:32 Trying to access hypervisor with provided key...2016-08-18 14:38:46 INFO hypervisor_ssh.py:40 Failed.2016-08-18 14:38:46 INFO hypervisor_ssh.py:44 Trying to access hypervisor with provided password...2016-08-18 14:38:49 INFO hypervisor_ssh.py:52 Failed2016-08-18 14:38:49 ERROR node_manager.py:3547 Failed to set up key based SSH access to hypervisor, most likely because we do not have the correct password cached. Please run fix_host_ssh command manually to
When we want to reconfigure for HA, installation of the fdm always fails with the following error: syslog.log:2014-09-10T07:34:33Z fdm-installer: VIB Nutanix_bootbank_pynfs_5.0.0-0.0.1 violates extensibility rule checks: [u'(line 22: col 0) Element vib failed to validate content'] We need to remove pynfs, reconfigure for HA and then we can re-install pynfs again. Is there a workaround in stead of keep on removing and reinstalling pynfs? Regards John Grinwis
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.