VMware Cloud Community
zimmi78
Contributor
Contributor
Jump to solution

IaaS Service failed to start after vCAC 6.0.1 Update

Hi,

I updated our vCAC 6.0 Infrastructure to 6.0.1.

IDM Appliance Update worked fine and also vCAC Appliance Update finished without errors.

After the restart the IaaS-Service failed to start.

I continued to upgrade IaaS Server Components because I thought that different versions might cause problems.

IaaS Components update finished without errors as well.

Then I restarted vCAC Appliance once more but the service still failes to start.

iaas-service-failed.JPG

Logged in to the portal, DEM Status shows the following errors:

dem-status.jpg

Does anyone know how to solve this problem?

Thanks!

0 Kudos
1 Solution

Accepted Solutions
igorstoyanov
VMware Employee
VMware Employee
Jump to solution

I believe the log looks ok (the errors are more like warnings that some notifications are not received before the services are started). Based on the log, it looks like that at least part of IaaS is configured (SSO integration is working and so on). So, the IaaS service shows as Failed because of the DEMs (as you pointed out in the initial post). You might also verify this by going to: https://vcacVA-ip/component-registry/services/status/current  and find the "iaas-service" part of the xml. There is going to be an error message there. So, it might be that the DEM is not started. I don't remember the exact windows service name for the DEM service but if you go to the list of windows services you might find some vCAC services that are not started there. If this is the case, just starting the services will change the status (after 2-4 minutes).

Visit http://blogs.vmware.com/orchestrator for the latest in Cloud Orchestration.

View solution in original post

0 Kudos
6 Replies
bhoriuchi
Enthusiast
Enthusiast
Jump to solution

did you run an iisreset on your iaas web host?

0 Kudos
zimmi78
Contributor
Contributor
Jump to solution

Yes, I did an iisreset.

The failed service is on the vcac appliance and it was failed even before iaas components upgrade on the windows machine.

0 Kudos
zimmi78
Contributor
Contributor
Jump to solution

I searched through the catalina.out log and found lots of errors from com.vmware.csp.iaas.blueprint.service (iaas-service). I don't understand what could cause those problems, though. Any ideas whats wrong?

0 Kudos
igorstoyanov
VMware Employee
VMware Employee
Jump to solution

I believe the log looks ok (the errors are more like warnings that some notifications are not received before the services are started). Based on the log, it looks like that at least part of IaaS is configured (SSO integration is working and so on). So, the IaaS service shows as Failed because of the DEMs (as you pointed out in the initial post). You might also verify this by going to: https://vcacVA-ip/component-registry/services/status/current  and find the "iaas-service" part of the xml. There is going to be an error message there. So, it might be that the DEM is not started. I don't remember the exact windows service name for the DEM service but if you go to the list of windows services you might find some vCAC services that are not started there. If this is the case, just starting the services will change the status (after 2-4 minutes).

Visit http://blogs.vmware.com/orchestrator for the latest in Cloud Orchestration.
0 Kudos
zimmi78
Contributor
Contributor
Jump to solution

You were right, a couple of services were not started on the IaaS Server. Thanks a lot.

0 Kudos
moazzamh
Contributor
Contributor
Jump to solution

Can you please enlist the services that I should start to start the iaas-service. I am also doing vcac iaas installation automation and I am also facing the same problem. I want to know which services I need to start

0 Kudos