I have just got an email from my customer describing the weird issue with VMware vCenter Server Appliance (aka VCSA).
The customer is doing weekly native backups of VCSA manually via VAMI. He wanted to run VCSA native backup again but when he tried to log into virtual appliance management interface (VAMI) he is getting the following error message
The customer is doing weekly native backups of VCSA manually via VAMI. He wanted to run VCSA native backup again but when he tried to log into virtual appliance management interface (VAMI) he is getting the following error message
 |
| Error message - This appliance cannot be used or repaired because of failure was encountered. You need to deploy a new appliance. |
The error message includes a resolution. Deploy a new appliance. The recommended solution is the last thing a typical vSphere admin would like to resolve such an issue. Fortunately enough, there is another solution/workaround.
To resolve this issue stop and start all the services on the vCSA,
To restart VCSA services run the following commands:
service-control --stop --all
service-control --start --all
In case, simple services restart does not help, you can have an issue with some recent backup job. In such a case, there is another resolution with an additional workaround
To resolve this issue stop and start all the services on the vCSA,
- Putty/SSH to vCenter server appliance.
- Login to VCSA using the root credentials.
- Enabled "shell".
- Restart VCSA services
To restart VCSA services run the following commands:
service-control --stop --all
service-control --start --all
In case, simple services restart does not help, you can have an issue with some recent backup job. In such a case, there is another resolution with an additional workaround
- Putty/SSH to vCenter server appliance.
- Login to vCSA using the root credentials.
- Enabled "shell".
- Move the /var/vmware/applmgmt/backupRestore-history.json file to /var/tmp/.
- Restart the vCenter Server Appliance.
4 comments:
thanks dude.. but you forgot to paste the most important command: shell.set --enabled true
Thanks! it helped by moving .json file, but appliance management started without restarting.
Hi, I have encountered the same issue and fixed by a bit alternative way in - restarted "applmgmt" only through service-control instead of restarting the vCenter Server Appliance.
Hope this helps as we may be able to avoid scheduling restarting whole vCSA.
thank you greatly! this worked like a charm!
Post a Comment