VMware Cloud Community
virtualtech_wor
Enthusiast
Enthusiast
Jump to solution

Profile Driven Storage Service Not Starting on VCSA after 6.0 U2 to U3

Hi,

After I patched VCSA 6.0 U2 to U3, vMotion is not working. Migrate virtual machine tasks are failing with this error.

A general system error occurred: PBM error occurred during PreMigrate-CheckCallback: Invalid response code: 503 Service Unavailable Invoking prechecks System

As referred to other articles for troubleshooting this error, suggested to:

1. First solution: restart the vmware-sps service on VCSA. I started the service, it shows running for some time and turns into stopped status after some time.

2, Second solution: stop web client service, start sps service and start web client service.

These 2 solutions didn't work in my case. still seeing the same issue.

Please advise how do we go about fixing this error?

Regards.

0 Kudos
1 Solution

Accepted Solutions
virtualtech_wor
Enthusiast
Enthusiast
Jump to solution

Based on the errors we were observing in the logging and that the VCSA was recently upgraded, it was found the following rpm packages were not upgraded properly when the full patch ISO was applied to the vCenter Server...
vmware-certificate-client
vmware-directory-client

We were able to manually upgrade these packages on the appliance and restart the vmware-sps service and the issue with vMotion is now resolved.

View solution in original post

0 Kudos
4 Replies
mhampto
VMware Employee
VMware Employee
Jump to solution

On the ESXi hosts, what errors are appearing in the /var/log/hostd file when this occurs?

0 Kudos
RajeevVCP4
Expert
Expert
Jump to solution

clean shutdown then power on

Rajeev Chauhan
VCIX-DCV6.5/VSAN/VXRAIL
Please mark help full or correct if my answer is use full for you
0 Kudos
virtualtech_wor
Enthusiast
Enthusiast
Jump to solution

Based on the errors we were observing in the logging and that the VCSA was recently upgraded, it was found the following rpm packages were not upgraded properly when the full patch ISO was applied to the vCenter Server...
vmware-certificate-client
vmware-directory-client

We were able to manually upgrade these packages on the appliance and restart the vmware-sps service and the issue with vMotion is now resolved.

0 Kudos
TMOKB
Contributor
Contributor
Jump to solution

I'm having what appears to be the same problem. Do you still have the commands (and file locations on the ISO) for installing the RPMs?

0 Kudos