Virtual Machine tasks fails with error "A general system error occurred: PBM error occurred during PreReconfigureCallback: Fault cause: vmodl.fault.SystemError"
search cancel

Virtual Machine tasks fails with error "A general system error occurred: PBM error occurred during PreReconfigureCallback: Fault cause: vmodl.fault.SystemError"

book

Article ID: 414573

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • Virtual machine tasks such as power on,clone,migrate and deploy or create new virtual machine fails with below error  
"A general system error occurred: PBM error occurred during PreReconfigureCallback: Fault cause: vmodl.fault.SystemError"
  • VDI/Citrix VM provision also fails with similar error
  • when we check for VM details from edit settings it may be identified that the HD size not loading for longer time and when we expand it shows 0 bytes and does not show any details

  • vCenter -->Configuration -->Security -->Storage providers list may also show empty
  • /var/log/vmware/vmware-sps/sps.log indicates sps service is failing to retrieve datastore/array details and it also indicates vpxd client login failures and connection refused error to storage providers
YYYY-MM-DDTHH:MM:SS.809Z [pool-27-thread-3] ERROR opId=sms-l4i2130-55 com.vmware.vim.sms.provider.vasa.version.VersionStrategyHelper - Update provider related array info failed!
com.vmware.vim.sms.fault.DBPersistenceException
        at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.updateKvProviderInfo(VasaProviderInfoPersistenceManager.java:124)
        at com.vmware.vim.sms.provider.vasa.version.VersionStrategyHelper.updateProviderInfo(VasaProviderInfoPersistenceManager.java:102)
        at com.vmware.vim.sms.provider.vasa.version.VersionStrategyHelper.updateProviderRelatedArrayInfo(VersionStrategyHelper.java:46)
        at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.refreshArrays(VasaProviderImpl.java:975)
        at com.vmware.vim.sms.provider.vasa.VasaProviderImpl$1.run(VasaProviderImpl.java:835)
        at com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcherImpl.processProviderRelatedArrayInfo(VersionStrategyHelper.java:102)
        at com.vmware.vim.sms.provider.vasa.version.VersionStrategyHelper.updateLatestArrayTopology(VersionStrategyHelper.java:93)
        at com.vmware.vim.sms.provider.vasa.version.Version2Strategy.updateOnline(Version2Strategy.java:111)
        at com.vmware.vim.sms.provider.vasa.VasaProviderImpl.updateProviderImpl(VasaProviderImpl.java:345)
        at com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcherImpl.handleHeartbeatSuccess(AlarmDispatcher.java:211)
        at com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcherImpl$1.run(AlarmDispatcherImpl.java:103)
        at com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcherImpl$1.run(AlarmDispatcherImpl.java:114)
        at java.util.concurrent.Executors$RunnableAdapter.call(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:30)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
        at java.lang.Thread.run(Thread.java:748)

YYYY-MM-DDTHH:MM:SS.006Z [pool-13-thread-12] ERROR opId=q3-s4 - com.vmware.vim.vmomi.client.impl.Task.CustomThreadPoolExecutor - [VLSI-client] Request took 9035 millis to execute. | Slow run() method execution Alert
YYYY-MM-DDTHH:MM:SS.006Z [pool-13-thread-12] WARN opId=q3-s4 - com.vmware.vim.storage.common.serviceclient.vpxd.VpxdClientLifeCycle - VirtualMachine:vm-1234:72XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX:XXXXXXXX64:VmReplicationGroupPropertyProviderAdapter:XXXXXXX-lXXX-hX:7XXXXXXXcom.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl: login to VPXD service failed.
YYYY-MM-DDTHH:MM:SS.006Z [pool-13-thread-12] WARN opId=q3-s4 - com.vmware.vim.storage.common.serviceclient.vpxd.VpxdClientLifeCycle - VirtualMachine:vm-1234:72XXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX:XXXXXXXX64:VmReplicationGroupPropertyProviderAdapter:XXXXXXX-lXXX-hX:7XXXXXXXcom.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl: login to VPXD service failed.
        at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl.login(VpxdClientImpl.java:53)
        at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientImpl.login(VpxdClientImpl.java:173)
        at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientLifeCycle.login(VpxdClientLifeCycle.java:111)
        at com.vmware.vim.storage.common.serviceclient.vpxd.impl.VpxdClientManagerImpl.login(VpxdClientManagerImpl.java:272)
        at com.vmware.vim.vmomi.client.common.impl.HttpExchange.run(HttpExchange.java:99)
        at com.vmware.vim.vmomi.client.common.impl.HttpExchange$1.handleEvent(HttpExchange.java:559)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolStack$1.handleEvent(HttpProtocolStack.java:187)

YYYY-MM-DDTHH:MM:SS.040Z [pool-28-thread-11] INFO  opId=sps-sMain-6XXXX-XXX-XX-14 com.vmware.vim.sms.health.ServiceHealthPoller - Ran service health check
YYYY-MM-DDTHH:MM:SS.454Z [pool-27-thread-3] ERROR opId=sps-sMain-6XXXX-XXX-XX-14 com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcher - Error: org.apache.axis2.AxisFault: Connection refused (Connection refused) occurred as provider: https://VASA.PROVIDER.FQDN:8080/verson.xml is offline
YYYY-MM-DDTHH:MM:SS [pool-27-thread-1] ERROR opId=pss-Main-425145-135-425401 error=org.apache.axis2.AxisFault: Connection refused (Connection refused) occurred as provider: https://VASA.PROVIDER.FQDN:8080/verson.xml is offline
YYYY-MM-DDTHH:MM:SS [pool-27-thread-1] ERROR opId=pss-Main-425145-135-425401 error=org.apache.axis2.AxisFault: Connection refused (Connection refused) occurred as provider: https://VASA.PROVIDER.FQDN:8080/verson.xml is offline 

 

Environment

VMware vCenter Server

Cause

This error occurs when the Profile-Driven Storage service is not running or is not accepting connections.

A "sps services vcenter PBM error" typically indicates a problem with the Profile-Driven Storage (PBM) service, which is also known as the Profile-Driven Storage (sps) service.

Resolution

To resolve the issue, ensure that the Profile-Driven Storage service is running.

  1. SSH to the VCSA using PuTTY or similar SSH client.
  2. Enter the shell of the vCSA.
  3. Run the following command to check the status of the service:
    service-control --status vmware-sps
  4. If the service is not running, then run the following command to start the vmware-sps service:
    service-control --start vmware-sps
  5. If the service is already running, then run the following command to restart the vmware-sps service:
    service-control --restart vmware-sps

Additional Information

Once vmware-sps service is restarted, /var/log/vmware/vmware-sps/sps.log indicates datastores are synchronizing

YYYY-MM-DDTHH:MM:SS [pool-24-thread-1] INFO datastore info: Synchronizing datastore ds://vmfs/volumes/xxxxxxxxx-xxxxxxxxx-xxxx-xxxxxxxxxxxxx/ 
YYYY-MM-DDTHH:MM:SS [pool-24-thread-1] INFO datastore info: Synchronizing datastore ds://vmfs/volumes/xxxxxxxxx-xxxxxxxxx-xxxx-xxxxxxxxxxxxx/ 
YYYY-MM-DDTHH:MM:SS [pool-24-thread-1] INFO datastore info: Synchronizing datastore ds://vmfs/volumes/xxxxxxxxx-xxxxxxxxx-xxxx-xxxxxxxxxxxxx/ 
YYYY-MM-DDTHH:MM:SS [pool-24-thread-1] INFO datastore info: Synchronizing datastore ds://vmfs/volumes/xxxxxxxxx-xxxxxxxxx-xxxx-xxxxxxxxxxxxx/

vCenter -->Configuration -->Security -->Storage providers will be listed as well.

Powered by Wolken Software