I'm getting the following error when trying to start the ImageBuilder service:
TimedOut (com.vmware.vapi.std.errors.timed_out) => {
I have tried the following to resolve:
- Made sure Auto Deploy service is running
- Rebooted
- Updating to the latest 6.5 VCSA version - 22000
- Increasing RAM from 10GB to 12GB
- Tried manually starting via ssh using the service-control --start vmware-image-builder command but get teh same timeout error
Error executing start on service imagebuilder. Details {
"resolution": null,
"detail": [
{
"args": [
"imagebuilder"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'imagebuilder '",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
Service-control failed. Error {
"resolution": null,
"detail": [
{
"args": [
"imagebuilder"
],
"id": "install.ciscommon.service.failstart",
"localized": "An error occurred while starting service 'imagebuilder '",
"translatable": "An error occurred while starting service '%(0)s'"
}
],
"componentKey": null,
"problemId": null
}
The VCSA is running in my home lab on a 6.7 ESXi host with 64GB of RAM and an E5-2620 CPU and the host has plenty of resources free. I believe I did the small or tiny deployment when deploying the VCSA. The host is also running 3 embedded ESXi 6.5 hosts with 8GB each, but the VCSA is not running on them, but is running on the physical host itself. I have a very simple setup and only 11 small linux VMs on the embedded hosts, and only one of them running at the moment.
I created a support bundle and tried going through the logs but I'm not seeing anything related to why the service start process would time out, although I'm probably not looking at the right logs.
Thanks for any help and let me know if I can provide more info.