5 Essential Tips for Maximizing Your Experience at Nutanix .NEXT for Bloggers
Looks like you may have missed a step in the instructions. Please double check your zk_server_config_file (I didn't see genesis in there it still shows zookeeper_monitor): ================================== Open the zookeeper configuration file.nutanix@cvm$ vi /home/nutanix/data/zookeeper_monitor/zk_server_config_filePress A to edit values in the file.Update the fields in the file.[b]Change # LAST MODIFIER: field_entry to # LAST MODIFIER: GENESIS[/b]Increment the existing number by one in the # ZOOKEEPER CONFIG VERSION field. For example, you would change # ZOOKEEPER CONFIG VERSION 3 to # ZOOKEEPER CONFIG VERSION 4Update the entries for each Controller VM (zk1, zk2, zk3, and so on) to match the IP addresses (ip_address) of the Controller VMs.[b]# LAST MODIFIER: GENESIS[/b][b]# ZOOKEEPER CONFIG VERSION existing_number+1[/b]ip_address zk2 # DON'T TOUCH THIS LINEip_address zk1 # DON'T TOUCH THIS LINEip_address zk3 # DON'T TOUCH THIS LINEip_address zkN # DON'T TOUCH THIS LINE ==========
Hi This is expected behavior. All of the compute/storage nodes (6035c) will only run AHV. Hopefully that helps!
Genesis should be started on the nodes in order to create the cluster. You'll want to determine what is in the genesis.out file to see why genesis is not starting. From that CVM, cd to ~/data/logs and enter 'tail -f genesis.out'. Once you have the messages in that log, post to here and we can take a look. That log will constantly overwrite itself as genesis crashes and tries to restart; the tail -f will allow messages to scroll on the console.
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.
