- Prism services have not started yet. Please try again later, Prism Central login issue.
- If you are facing this issue in Prism Central 5.17.1 or higher version.
Prism services have not started yet. Please try again later, Prism Central login issue.
When accessing the Nutanix Prism Central or Prism Element Web Console, you may see the following error in your browser.
Prism services have not started yet. Please try again later Nutanix Gateway not reachable. Http request error.
The solution is to restart the Prism services on the CVM of the Prism leader.
First find the Prism leader and restart the prism service. To verify the prism service leader in cluster run the following command :-
nutanix@NTNX-Prod_CVM$ curl http://0:2019/prism/leader && echo
You will see the below output
{"leader":"x.x.x.198:9080", "is_local":false}
from the above output we can see that prism leader is x.x.x.198
SSH to Prism Leader x.x.x.198 and run the following command to restart Prism service.
There will be no production related issue after running below commands :-
nutanix@NTNX-Prod_CVM$ genesis stop prism nutanix@NTNX-Prod_CVM$ cluster start
If you are facing this issue in Prism Central 5.17.1 or higher version.
Then you have to change the new compute resource of Prism Central.
If the below requirements if the resources are low will get the same issue.
| Sr.No | PC Size | vCPU | Memory [GB] | Guest VMs Supported (across all clusters) |
| 1 | Small | 6 | 26 GB | 2500 (scale out: 5000) |
| 2 | Large | 10 | 44 GB | 12500 (scale out: 25000) |
Additional memory requirements if any additional services are enabled in Prism Central:
| Sr.No | PC Size | Calm/Leap or any service | Micro segmentation | Prism Ultimate Features* [GB] |
| 1 | Small | 4 | 1 | 4 |
| 2 | Large | 8 | 1 | 8 |
Run the below NCC check if you see any alert like “Configured resource for the Prism Central VM is inadequate.”
nutanix@Prod-PCVM$ ncc health_checks system_checks pc_vm_resource_resize_check
Below is the output of the above command :-
Running : health_checks system_checks pc_vm_resource_resize_check
[==================================================] 100%
/health_checks/system_checks/pc_vm_resource_resize_check [ PASS ]
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
+-----------------------+
| State | Count |
+-----------------------+
| Pass | 1 |
| Total Plugins | 1 |
+-----------------------+
Plugin output written to /home/nutanix/data/logs/ncc-output-latest.logIncrease the size of the Prism Central restart is required, also make sure you are increasing the compute size when Prism Central VM is in powered off state.
Prism Central also has additional automation and devops features like Karbon, Objects, Files, etc. that do not require any additional memory resources allocated.
The current feature capabilities of Prism Central require resource on the Prism Central VM to be increased for optimum performance.
Follow the below steps for changing the resources of prism central.
- Launch the console of Prism Central from Prism Element
- You can take putty or ssh to the Prism Central IP
- Run the command
nutanix@ProdPCVM$cluster stop
Once all services are down,shutdown the Prism Central machine from PE or with below command
nutanix@ProdPCVM$ sudo shutdown
Once Prism Central is shutdown open the console and update the setting as per your requirement
You can also use acli to change the resources of the Prism Central.
Take the putty of any Nutanix controller Virtual Machine, and run the below command.
nutanix•N1NX-192-168-19-87-A-PCVN:- acli vm.update <Prism Central VM Name> memory=<SIZE>G num_vcpus=<number of vcpus required>- Power on Prism Central VM with console or acli (VM.on Prism Central VM name)
- Take the putty of Prism Central and wait for genesis and zookeeper services to be running:
nutanix•N1NX-192-168-19-87-A-PCVN:- genesis status
- Start cluster services with below command
nutanix•N1NX-192-168-19-87-A-PCVN:- cluster start
- Check the cluster status with below command
nutanix@N1NX-192-168-19-87-A-PCVN:- cs
2020-09-11 21:16:08 INFO zookeeper_session.py:176 cluster is attempting to connect to Zookeeper
2020-09-11 21:16:08 INFO cluster:2722 Executing action status on SVMs 192.168.19.87
The state of the cluster: start
Lockdown node: Disabled
CVM: 192.168.19.87 Up, ZeusLeader
Zeus UP [5086, 5121, 5122, 5123, 5133, 51503
Scavenger UP [3978, 3539, 3535, 3536]
SSLTerminator UP [5655, 5726, 5727, 5728]
Medusa UP [5698, 5753, 5754, 5755, 5965]
DynamickingChanger UP [9790, 10090, 10091, 108807
VipMonitor UP [2479, 2553, 2554, 2555, 2556]
InsightsDB UP [9812, 10105, 10106, 10570]
InsightsDataTransfer UP [9837, 10216, 10217, 10263, 10264, 10265, 10266, 10267,10268, 10269]
Ergon UP [9890, 10223, 10224, 10227]
Athena UP [9924, 10225, 10226, 102283
Prism UP [10279, 10559, 10560, 10948, 13324, 13634]
AlertManager UP [10311, 10666, 10667, 11160]
Catalog UP [10323, 10617, 10618, 10621]
Atlas UP [10334, 10750, 10751, 10754]
Uhura UP [10349, 10847, 10848, 108551
SysStatCollector UP [10361, 10763, 10764, 10767]
ClusterConfig UP [10374, 10850, 10851, 10858]
Mercury UP [10401, 10888, 10889, 10997)
APLOSEngine UP [10438, 10853, 10854, 10860]
APLOS UP [13277, 13502, 13503, 13506]
StatsGatevay UP [13301, 13527, 13528, 13700]
Laren UP [13337, 13568, 13569, 135713
Kanon UP [13360, 13590, 13591, 13593)
Delphi UP [14787, 15001, 15002, 15003]
Metropolis UP [14796, 15010, 15011, 15245]
Flow UP [14811, 14989, 14990, 149913
Magneto UP [14828, 15080, 15081, 15082]
Search UP [16347, 16428, 16429, 16430, 16491, 16494, 16495, 16840]
XPlay UP [16366, 16631, 16632, 267891
XTrim UP [16392, 16637, 16638, 166393
ClusterHealth UP [16418, 16641, 17822, 17827, 17836, 17911, 17912, 17916,17921, 17922, 17930, 17931, 17933, 17934, 17936, 17941, 18034,18035, 18084, 18085, 18094, 18095]
Neuron UP [16443, 16699, 16701, 17550, 17597, 17598]
2020-09-11 21:16:09 INFO cluster:2879 Success!
nutanixANTNX-192-168-19-87-A-PCVM:-$
Now login with Prism credentails
See also :- AHV TO ANY HYPERVISOR MIGRATION