I had a complete working setup of Nutanix Community Edition along with Prism Central deployed. I was able to access my prism central through UI and Rest API for working with virtual machines.
But suddenly i was disconnected from my PCVM today morning and was not able to access anymore. I tried to do ssh and logged in through PC UI but I couldn’t. I am able to log into both my AHV VM and CVM. In CVM, cluster status is showing all services are up and running.
Can you please help me here. Attaching the required screenshots.
@ktelep@Kcmount@JeroenTielen
Page 1 / 1
Are the prism central vm's started? And ssh into the prism central vm and run "cluster start”
I am not able to ssh into the PCVM. Can you please let me know how to start PCVM if not started.
The highlighted one is my PCVM.
Open the console from the PCVM from Prism Element. Then login with admin or nutanix user. Then run the cluster start option.
When I am trying to launch the web console for Prism Element got this. Not sure why this is coming now but earlier it was working because I configured PC using PE console.
Logging into CVM via SSH and from there logging into PCVM is not working. Throwing the below error.
Oke so first fix your normal cluster by enabling internet access to it.
Can you show me the output of this command from the CVM: ping www.nutanix.com
Oke, so you cluster does have internet access. Why is the pulse not working? It there something being blocked by the firewall?
Does Prism Central is available in the trial version for 45 days only?
We don’t have configured any firewall and all remains working till today morning. All of sudden it’s stopped and PCVM was inaccessible.
You should first focus on your cluster self before you continue on prism central. ;)
but you can try the following.
ssh into cvm and run acli vm.on <pc vm name>
This will start you prism central vm. And when it is started you can ssh into the pcvm and run: cluster start
I think the VM is not exist.
No, the vm does exist. But you hosts don't have enough free memory to start the vm. Stop other virtual machines to free up memory.
Able to do the pulse configuration. I can see the PCVM details in Prism Element.
Tried to launch Prism Central Console and see this error.
Can you please let me know how to fix this
JeroenTielen can you please have a look into the above screenshot and let me know what may be the issue.
When I am trying to launch PCVM Console from Prism Element, getting the above error.
Looks like your disks are wearing out. Can you check the smart status or disk status?
#################################################### # TIMESTAMP : Fri Aug 09 09:23:26 2024 (UTC +0000) # #################################################### Cluster Name: UAG-Cluster Cluster Id: 1597370837881680529 Cluster UUID: 00061f37-aed7-d63c-162b-005056817291 Cluster Version: 6.5.2 NCC Version: 4.6.2.1-3f9070e4 CVM ID(Svmid) : 2 CVM external IP : 10.108.60.34 Hypervisor IP : 10.108.60.33 Hypervisor version : Nutanix 20220304.342 Node serial : cfa2daf8-9e71-4383-af56-2fe47af92c1c Model : CommunityEdition Node Position : A Block S/N : 99b7a1f2
Ergon service is down/inaccessible on nodes with ips 10.108.60.34 Cluster health service is down/inaccessible on nodes 10.108.60.34 Running /health_checks/hardware_checks/disk_checks/disk_usage_check WARN ] -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
Detailed information for disk_usage_check: Node 10.108.60.34: WARN: Unable to parse response from 10.108.60.34: Before shifting - -s 9 90 /home/nutanix/ncc/bin/ncc --debug=False --ncc_interactive=false --ncc_global=false --ncc_plugin_dir=/home/nutanix/ncc/bin/plugins --ncc_logging_dir=/home/nutanix/data/logs --ncc_enable_intrusive_plugins=False --ncc_master_ip=10.108.60.34 --ncc_plugin_output_file=/home/nutanix/data/logs/ncc-output-latest.log-disk_usage_check --ncc_execution_token=None --acquire_ncc_lock=False --ncc_send_email=False --send_email_force=False --is_run_all=False --cvm_list=10.108.60.34 health_checks hardware_checks disk_checks disk_usage_check Original timeout: -s, Modified timeout: 0 After shifting - 9 90 /home/nutanix/ncc/bin/ncc --debug=False --ncc_interactive=false --ncc_global=false --ncc_plugin_dir=/home/nutanix/ncc/bin/plugins --ncc_logging_dir=/home/nutanix/data/logs --ncc_enable_intrusive_plugins=False --ncc_master_ip=10.108.60.34 --ncc_plugin_output_file=/home/nutanix/data/logs/ncc-output-latest.log-disk_usage_check --ncc_execution_token=None --acquire_ncc_lock=False --ncc_send_email=False --send_email_force=False --is_run_all=False --cvm_list=10.108.60.34 health_checks hardware_checks disk_checks disk_usage_check Fri Aug 9 09:23:37 UTC 2024 Fri Aug 9 09:23:37 UTC 2024
Refer to KB 1523 (http://portal.nutanix.com/kb/1523) for details on disk_usage_check or Recheck with: ncc health_checks hardware_checks disk_checks disk_usage_check --cvm_list=10.108.60.34 +-----------------------+ | State | Count | +-----------------------+ | Warning | 1 | | Total Plugins | 1 | +-----------------------+ Plugin output written to /home/nutanix/data/logs/ncc-output-latest.log
JeroenTielen Please find the required details below.
I am doing the Nutanix CE setup on a Vmware ESxi Host. My Host capacity is 1.2 TB. I have done this setup with 128 GB RAM / Memory.
From the output of above command, disk_usage and disk_online checks are in warning state. This means that the Data Disk Usage is more than 90% for several hour and the disk is offline as well. Attaching the screenshots of various metrics details from PE for reference.
Host Metrics
VM Metrics
Disk Metrics
When u r guessing it’s related to memory issue, does that mean RAM size or disk size?
According to the usage percentage of memory what we can see in PE, only PCVM is having a higher RAM usage. If we want to increase the RAM size for CVM or PCVM, what is steps to do this?
If we need to increase the RAM size, let me know in which RAM we need to add more memory.
Please let me know how to fix this because it’s completely intermittent and got stuck here.
