Pbm error occurred during premigratecheckcallback connection refused

Pbm error occurred during premigratecheckcallback connection refused

vcenter01:/storage/log/vmware/vmware-sps # vi sps.log

3634794, 6.0.0, Linux, release^M

2018-08-15T14:58:46.016Z [WrapperSimpleAppMain] INFO opId= com.vmware.sps.StorageMain — Starting PBM container using config file: ../conf/pbm-spring-config.xml

2018-08-15T14:58:46.027Z [WrapperSimpleAppMain] INFO opId= com.vmware.pbm.app.PbmLocalService — Using Spring configuration file: ‘../conf/pbm-spring-config.xml’

2018-08-15T14:58:46.028Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] Loading pbm.properties.upgrade

2018-08-15T14:58:46.028Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] source server GUID bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.028Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] sourceServerGUID :bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.030Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.vim.storage.common.util.UUIDFactory — propFile — pbm.properties serverGuidKey- pbm.serverGuid defaultServerGuid- ##PBM_SERVER_GUID## guidToUse- bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.090Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.vim.storage.common.util.UUIDFactory — Assigning GUID to server instance — bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.133Z [WrapperSimpleAppMain] INFO opId= com.vmware.pbm.util.SpringService — Initializing Spring from ‘../conf/pbm-spring-config.xml’ and ‘pbm.properties’

2018-08-15T14:58:46.268Z [WrapperSimpleAppMain] INFO opId= org.springframework.beans.factory.xml.XmlBeanDefinitionReader — Loading XML bean definitions from class path resource [../conf/pbm-spring-config.xml]

2018-08-15T14:58:46.520Z [WrapperSimpleAppMain] INFO opId= org.springframework.beans.factory.config.PropertyPlaceholderConfigurer — Loading properties file from class path resource [pbm.properties]

Type :quit to exit Vim 2,1 Top

vcenter01:/storage/log/vmware/vmware-sps # vi vmware-sps-gc.log.0.current

Java HotSpot(TM) 64-Bit Server VM (24.91-b03) for linux-amd64 JRE (1.7.0_91-b15), built on Oct 2 2015 03:25:25 by «java_re» with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

Memory: 4k page, physical 8193988k(284452k free), swap 27258872k(11164808k free)

CommandLine flags: -XX:ErrorFile=/var/log/vmware/vmware-sps//java_error%p.log -XX:+ForceTimeHighResolution -XX:GCLogFileSize=1048576 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/vmware/vmware-sps/ -XX:InitialHeapSize=33554432 -XX:MaxHeapSize=205520896 -XX:MaxPermSize=134217728 -XX:NumberOfGCLogFiles=10 -XX:ParallelGCThreads=1 -XX:+PrintGC -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintReferenceGC -XX:+PrintTenuringDistribution -XX:ThreadStackSize=256 -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC

2018-08-15T14:58:45.991+0000: 0.519: [GC2018-08-15T14:58:45.996+0000: 0.524: [SoftReference, 0 refs, 0.0000260 secs]2018-08-15T14:58:45.996+0000: 0.524: [WeakReference, 78 refs, 0.0000110 secs]2018-08-15T14:58:45.996+0000: 0.524: [FinalReference, 693 refs, 0.0005320 secs]2018-08-15T14:58:45.997+0000: 0.524: [PhantomReference, 0 refs, 1 refs, 0.0000110 secs]2018-08-15T14:58:45.997+0000: 0.524: [JNI Weak Reference, 0.0000090 secs]

Desired survivor size 1048576 bytes, new threshold 7 (max 15)

[PSYoungGen: 9216K->1008K(10240K)] 9216K->1859K(32256K), 0.0060660 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

2018-08-15T14:58:46.215+0000: 0.743: [GC2018-08-15T14:58:46.219+0000: 0.747: [SoftReference, 0 refs, 0.0000240 secs]2018-08-15T14:58:46.219+0000: 0.747: [WeakReference, 49 refs, 0.0000100 secs]2018-08-15T14:58:46.219+0000: 0.747: [FinalReference, 652 refs, 0.0006780 secs]2018-08-15T14:58:46.220+0000: 0.748: [PhantomReference, 0 refs, 0 refs, 0.0000100 secs]2018-08-15T14:58:46.220+0000: 0.748: [JNI Weak Reference, 0.0000070 secs]

Desired survivor size 1048576 bytes, new threshold 7 (max 15)

[PSYoungGen: 10224K->1008K(19456K)] 11075K->3084K(41472K), 0.0055730 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]

«vmware-sps-gc.log.0.current» 18L, 2804C 1,1 Top

Java HotSpot(TM) 64-Bit Server VM (24.91-b03) for linux-amd64 JRE (1.7.0_91-b15), built on Oct 2 2015 03:25:25 by «java_re» with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

Memory: 4k page, physical 8193988k(284452k free), swap 27258872k(11164808k free)

CommandLine flags: -XX:ErrorFile=/var/log/vmware/vmware-sps//java_error%p.log -XX:+ForceTimeHighResolution -XX:GCLogFileSize=1048576 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/vmware/vmware-sps/ -XX:InitialHeapSize=33554432 -XX:MaxHeapSize=205520896 -XX:MaxPermSize=134217728 -XX:NumberOfGCLogFiles=10 -XX:ParallelGCThreads=1 -XX:+PrintGC -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintReferenceGC -XX:+PrintTenuringDistribution -XX:ThreadStackSize=256 -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC

2018-08-15T14:58:45.991+0000: 0.519: [GC2018-08-15T14:58:45.996+0000: 0.524: [SoftReference, 0 refs, 0.0000260 secs]2018-08-15T14:58:45.996+0000: 0.524: [WeakReference, 78 refs, 0.0000110 secs]2018-08-15T14:58:45.996+0000: 0.524: [FinalReference, 693 refs, 0.0005320 secs]2018-08-15T14:58:45.997+0000: 0.524: [PhantomReference, 0 refs, 1 refs, 0.0000110 secs]2018-08-15T14:58:45.997+0000: 0.524: [JNI Weak Reference, 0.0000090 secs]

Desired survivor size 1048576 bytes, new threshold 7 (max 15)

[PSYoungGen: 9216K->1008K(10240K)] 9216K->1859K(32256K), 0.0060660 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

Источник

Be-Virtual.net

Lately, I encountered some issues related to VMware vSAN in my Lab environment. The error message that was popping up all the time was “PBM error occurred during PreCloneCheckCallback“.

So how did the problem occur? First, we start with some background information. My Lab environment is powered-on when needed and powered-off when not needed. This is, of course, a little bit different than a production 24×7 environment that you have in your datacenters worldwide.

The environment was booted successfully at first glance. We are talking about Domain Controllers, vCenter Server, VMware NSX-V, nested ESXi Hosts, and vRealize Automation. When I started deploying virtual machines with a vRealize Automation (vRA) based on blueprints with vSphere Templates issues started to occur.

vRealize Automation was failing on the provisioning task and was cleaning up the deployment because of the failed state (default behavior). So it was time to dig into the underlying infrastructure.

Environment

When the issue occurred the following software versions were used in my lab environment:

• VMware vCenter 6.5 Update 2B
• VMware vRealize Automation 7.3.1
• VMware ESXi 6.5 Update 2
• VMware vSAN 6.6

Error message(s)

Here is all the information that can be found in various locations surrounding the issue. Lets start with the screenshots. The first one is from VMware vCenter and the second one is from vRealize Automation. As you can see there is clearly a problem.

Источник

Pbm error occurred during premigratecheckcallback connection refused

Good Day Everyone.

I have a VCENTER SERVER 6.0U2 running on windows server 2008R2

Few days ago, i use the VCETNER 6.0U3 ISO to in-place upgrade my VCENTER.

But the upgrade is failed because some issue, the installation auto rollback itself.

After rollback, some of the function is unable to use in the VCENTER like web client and Vmotion.

But the most important service is Vmotion. When process the Vmotion Migrate, will show up error:

«A general system error occurred: PBM error occurred during PreMigrateCheckCallback: No connection could be made because the target machine actively refused it.»

According of the VMWARE KB

The Profile-Driven Storage service maybe not running, after i check out of the window service, confirm the service is not running.

When i right click start the service, the service cannot start. According the log of the service (vmware-spssps.log)

[WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] pbm.properties.upgrade not found

[WrapperSimpleAppMain] DEBUG opId= com.vmware.vim.storage.common.util.UUIDFactory — propFile — pbm.properties serverGuidKey- pbm.serverGuid defaultServerGuid- ##PBM_SERVER_GUID## guidToUse- null

Anyone have a idea?

1. Any action can fix this issue?

2. Can i use program and features, change option to repair my VCENTER?

3. The worst case is reinstall the VCENTER? Can i using the old VCENTER database when reinstall to keep all of the setting of VCENTER?

Like the assigned SAN Storage LUN, cluster, network setting.

Источник

Ken Umemoto’s vReality

I’m a Sr. Systems Engineer at a Global Environmental Engineering company. I’ve been in IT since 1999 and from 2005, my focus has been VMware datacenter products. More recently, my attention has been for Microsoft Azure services. As the Global Service Owner for VMware Datacenter products, I’ve had the pleasure of having in-depth and hands-on experience with not only VMware products, but server, storage and networking technologies.

Pages

Monday, August 14, 2017

Storage vMotion Error: A general system error occurred: PBM error occurred during PreMigrateCheckCallback: Connection refused

I just tried to perform a Storage vMotion on a VM and received the following error:

I took a look at the services running on the vCSA by running » service-control —status «. It appears the VMware vSphere Profile-Driven Storage Service (vmware-sps) had stopped.

To get the service running, just run the following command: service-control —start vmware-sps

I was then able to successfully perform a storage vMotion.

Bonus info:
Here’s a list of services running on the vsphere 6.X vCSA:

Источник

Pbm error occurred during premigratecheckcallback connection refused

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

I have just build a VM in my ESXi 6 server and when I want to power it on, it’s throwing error as ‘A general system error occurred: connection refused’

Please see attached screenshot.

Help is appreciated.

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report Inappropriate Content

Hope you have access to vCenter Appliance, Try restarting this «VMware vCenter workflow manager service»

To resolve this issue, start the VMware vCenter workflow manager service.

Windows vCenter Server

1. On the server that runs vCenter Server, open Start > Run , type services.msc and press Enter .
2. Right-click VMware vCenter workflow manager service and click start.
3. Attempt to power on the virtual machine again.

vCenter Server Appliance (VCSA)

1. Connect to the VCSA shell as root. For more information, see:

Run this command to restart the VMware vCenter workflow service ( vmware-vpx-workflow

# service vmware-vpx-workflow restart

Источник

Skip to content

Lately, I encountered some issues related to VMware vSAN in my Lab environment. The error message that was popping up all the time was “PBM error occurred during PreCloneCheckCallback“.

So how did the problem occur? First, we start with some background information. My Lab environment is powered-on when needed and powered-off when not needed. This is, of course, a little bit different than a production 24×7 environment that you have in your datacenters worldwide.

The environment was booted successfully at first glance. We are talking about Domain Controllers, vCenter Server, VMware NSX-V, nested ESXi Hosts, and vRealize Automation. When I started deploying virtual machines with a vRealize Automation (vRA) based on blueprints with vSphere Templates issues started to occur.

vRealize Automation was failing on the provisioning task and was cleaning up the deployment because of the failed state (default behavior). So it was time to dig into the underlying infrastructure.

Environment

When the issue occurred the following software versions were used in my lab environment:

• VMware vCenter 6.5 Update 2B
• VMware vRealize Automation 7.3.1
• VMware ESXi 6.5 Update 2
• VMware vSAN 6.6

Error message(s)

Here is all the information that can be found in various locations surrounding the issue. Lets start with the screenshots. The first one is from VMware vCenter and the second one is from vRealize Automation. As you can see there is clearly a problem.

And here is an overview of the error message(s). Here is the vRealize Automation log entry related to the VMware vSAN issue:

Error in Execute DynamicOps.Common.Client.HtmlResponseException: Service Unavailable (503)

Here is the VMware vCenter log entry related to the VMware vSAN issue:

A general system error occurred - PBM error occurred during PreCloneCheckCallback (2118557)

Solution

The solution is quick but is more like a quick fix because it comes back every time I re-start my lab environment (cold boot).

Procedure:

• Open a web browser.
• Navigate to your vCenter Server URL (https://%vc%/vsphere-client).
• Login with a user that has administrator credentials (administrator@vsphere.local).
• Navigate to Hosts & Clusters > Select the vCenter Object.
• Click on the Configure tab.
• Click on the Storage Providers.
• Click on the following two buttons:
  • Synchronizes all Storage Providers with the current state of the environment.
  • Rescan the storage provider for new storage systems and storage capabilities.
• After pressing the buttons, you don’t see any tasks running on the vCenter Server (expected behavior). After 5 seconds everything should be working and provisioning should be possible.

Wrap-up

Thanks for reading this blog post. If you have any comments, please respond in the comment section below!

Pbm error occurred during premigratecheckcallback

vcenter01:/storage/log/vmware/vmware-sps # vi sps.log

3634794, 6.0.0, Linux, release^M

2018-08-15T14:58:46.016Z [WrapperSimpleAppMain] INFO opId= com.vmware.sps.StorageMain — Starting PBM container using config file: ../conf/pbm-spring-config.xml

2018-08-15T14:58:46.027Z [WrapperSimpleAppMain] INFO opId= com.vmware.pbm.app.PbmLocalService — Using Spring configuration file: ‘../conf/pbm-spring-config.xml’

2018-08-15T14:58:46.028Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] Loading pbm.properties.upgrade

2018-08-15T14:58:46.028Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] source server GUID bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.028Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.pbm.app.PbmLocalService — [getServerGUIDFromSourceVC] sourceServerGUID :bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.030Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.vim.storage.common.util.UUIDFactory — propFile — pbm.properties serverGuidKey- pbm.serverGuid defaultServerGuid- ##PBM_SERVER_GUID## guidToUse- bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.090Z [WrapperSimpleAppMain] DEBUG opId= com.vmware.vim.storage.common.util.UUIDFactory — Assigning GUID to server instance — bb753721-9fd0-4e76-adb0-cf8d2ef7750f

2018-08-15T14:58:46.133Z [WrapperSimpleAppMain] INFO opId= com.vmware.pbm.util.SpringService — Initializing Spring from ‘../conf/pbm-spring-config.xml’ and ‘pbm.properties’

2018-08-15T14:58:46.268Z [WrapperSimpleAppMain] INFO opId= org.springframework.beans.factory.xml.XmlBeanDefinitionReader — Loading XML bean definitions from class path resource [../conf/pbm-spring-config.xml]

2018-08-15T14:58:46.520Z [WrapperSimpleAppMain] INFO opId= org.springframework.beans.factory.config.PropertyPlaceholderConfigurer — Loading properties file from class path resource [pbm.properties]

Type :quit to exit Vim 2,1 Top

vcenter01:/storage/log/vmware/vmware-sps # vi vmware-sps-gc.log.0.current

Java HotSpot(TM) 64-Bit Server VM (24.91-b03) for linux-amd64 JRE (1.7.0_91-b15), built on Oct 2 2015 03:25:25 by «java_re» with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

Memory: 4k page, physical 8193988k(284452k free), swap 27258872k(11164808k free)

CommandLine flags: -XX:ErrorFile=/var/log/vmware/vmware-sps//java_error%p.log -XX:+ForceTimeHighResolution -XX:GCLogFileSize=1048576 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/vmware/vmware-sps/ -XX:InitialHeapSize=33554432 -XX:MaxHeapSize=205520896 -XX:MaxPermSize=134217728 -XX:NumberOfGCLogFiles=10 -XX:ParallelGCThreads=1 -XX:+PrintGC -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintReferenceGC -XX:+PrintTenuringDistribution -XX:ThreadStackSize=256 -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC

2018-08-15T14:58:45.991+0000: 0.519: [GC2018-08-15T14:58:45.996+0000: 0.524: [SoftReference, 0 refs, 0.0000260 secs]2018-08-15T14:58:45.996+0000: 0.524: [WeakReference, 78 refs, 0.0000110 secs]2018-08-15T14:58:45.996+0000: 0.524: [FinalReference, 693 refs, 0.0005320 secs]2018-08-15T14:58:45.997+0000: 0.524: [PhantomReference, 0 refs, 1 refs, 0.0000110 secs]2018-08-15T14:58:45.997+0000: 0.524: [JNI Weak Reference, 0.0000090 secs]

Desired survivor size 1048576 bytes, new threshold 7 (max 15)

[PSYoungGen: 9216K->1008K(10240K)] 9216K->1859K(32256K), 0.0060660 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

2018-08-15T14:58:46.215+0000: 0.743: [GC2018-08-15T14:58:46.219+0000: 0.747: [SoftReference, 0 refs, 0.0000240 secs]2018-08-15T14:58:46.219+0000: 0.747: [WeakReference, 49 refs, 0.0000100 secs]2018-08-15T14:58:46.219+0000: 0.747: [FinalReference, 652 refs, 0.0006780 secs]2018-08-15T14:58:46.220+0000: 0.748: [PhantomReference, 0 refs, 0 refs, 0.0000100 secs]2018-08-15T14:58:46.220+0000: 0.748: [JNI Weak Reference, 0.0000070 secs]

Desired survivor size 1048576 bytes, new threshold 7 (max 15)

[PSYoungGen: 10224K->1008K(19456K)] 11075K->3084K(41472K), 0.0055730 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]

«vmware-sps-gc.log.0.current» 18L, 2804C 1,1 Top

Java HotSpot(TM) 64-Bit Server VM (24.91-b03) for linux-amd64 JRE (1.7.0_91-b15), built on Oct 2 2015 03:25:25 by «java_re» with gcc 4.3.0 20080428 (Red Hat 4.3.0-8)

Memory: 4k page, physical 8193988k(284452k free), swap 27258872k(11164808k free)

CommandLine flags: -XX:ErrorFile=/var/log/vmware/vmware-sps//java_error%p.log -XX:+ForceTimeHighResolution -XX:GCLogFileSize=1048576 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/var/log/vmware/vmware-sps/ -XX:InitialHeapSize=33554432 -XX:MaxHeapSize=205520896 -XX:MaxPermSize=134217728 -XX:NumberOfGCLogFiles=10 -XX:ParallelGCThreads=1 -XX:+PrintGC -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintGCTimeStamps -XX:+PrintReferenceGC -XX:+PrintTenuringDistribution -XX:ThreadStackSize=256 -XX:+UseCompressedOops -XX:+UseGCLogFileRotation -XX:+UseParallelGC

2018-08-15T14:58:45.991+0000: 0.519: [GC2018-08-15T14:58:45.996+0000: 0.524: [SoftReference, 0 refs, 0.0000260 secs]2018-08-15T14:58:45.996+0000: 0.524: [WeakReference, 78 refs, 0.0000110 secs]2018-08-15T14:58:45.996+0000: 0.524: [FinalReference, 693 refs, 0.0005320 secs]2018-08-15T14:58:45.997+0000: 0.524: [PhantomReference, 0 refs, 1 refs, 0.0000110 secs]2018-08-15T14:58:45.997+0000: 0.524: [JNI Weak Reference, 0.0000090 secs]

Desired survivor size 1048576 bytes, new threshold 7 (max 15)

[PSYoungGen: 9216K->1008K(10240K)] 9216K->1859K(32256K), 0.0060660 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]

Источник

Be-Virtual.net

Lately, I encountered some issues related to VMware vSAN in my Lab environment. The error message that was popping up all the time was “PBM error occurred during PreCloneCheckCallback“.

So how did the problem occur? First, we start with some background information. My Lab environment is powered-on when needed and powered-off when not needed. This is, of course, a little bit different than a production 24×7 environment that you have in your datacenters worldwide.

The environment was booted successfully at first glance. We are talking about Domain Controllers, vCenter Server, VMware NSX-V, nested ESXi Hosts, and vRealize Automation. When I started deploying virtual machines with a vRealize Automation (vRA) based on blueprints with vSphere Templates issues started to occur.

vRealize Automation was failing on the provisioning task and was cleaning up the deployment because of the failed state (default behavior). So it was time to dig into the underlying infrastructure.

Environment

When the issue occurred the following software versions were used in my lab environment:

• VMware vCenter 6.5 Update 2B
• VMware vRealize Automation 7.3.1
• VMware ESXi 6.5 Update 2
• VMware vSAN 6.6

Error message(s)

Here is all the information that can be found in various locations surrounding the issue. Lets start with the screenshots. The first one is from VMware vCenter and the second one is from vRealize Automation. As you can see there is clearly a problem.

Источник

port115

Occasionally, and by that I mean very rarely, VM’s can refuse to migrate on or off VSAN storage (I know, I know, why would you every want to migrate off VSAN?).

The error will look something similar to:

A general system error occurred: PBM error occurred during PreMigrateCheckCallback: pbm.fault.PBMFault; Internal error during SPBM validation;
No VASA Provider for schema namespace (VSAN) found.

You’ll also find that you can’t create new storage providers.

The official reason is: Official: This issue occurs due to inconsistent data between the Storage Management Service (SMS) and the Storage Based Policy Manager (SPBM).

While VMware claim that this is only an issue with VSAN 5.5, I have seen it occur in VSAN 6.0. To be fair it was in my lab, and I was testing “dirty” power down of VSAN hosts.

NB: As this is a VASA related issue it might work for other storage providers too. In the testing I’ve done its been non-disruptive but as always proceed with caution.

1. In the vSphere Web Client Navigate to the vCenter Server (Not the VSAN Cluster)
2. Select the Configure tab on the right.
3. Select the Storage Providers Menu Item.
4. In the Storage Providers window pane: click the storage icon with the red circular arrows.
5. Once done, the Cluster with VSAN will be scanned and you should be able to move your VM’s about.

Источник

VMware SRM and the PBM & PreCloneCheckCallback error

Quick post here. I recently updated my environment to vCenter 6.0 Update 1 and VMware Site Recovery Manager 6.1 and after my first attempted test failover (and subsequent ones) the test would always fail when it tried to power on the virtual machines. Some powered-on and some didn’t. The following errors appeared for about half of my VMs:

“Error – A general system error occurred: PBM error occurred during PreMigrateCheckCallback: Invalid response code: 503 Service Unavailable”

Alrighty. That means what? At first I thought maybe it was a VMware tools issue, so I made sure I had the latest and greatest installed on all of my VMs.

Re-attempted the test recovery and it failed again. No rhyme or reason to it, different VMs, no relationship to hosts or datastores or anything that I could tell. The datastores were recovered and the proper VMs registered but failed to power on.

If I tried to manually power them on in the Web Client, all of the power-on options were gone (well grayed-out). Looking in the logs there was not much more interesting,

2015-09-14T15:23:40.487-07:00 [02176 error ‘LocalPbmServer’] Exception caught while performing GetContent
–> std::exception ‘class Vmacore::Soap::InvalidResponseException’ “Invalid response code: 503 Service Unavailable”
2015-09-14T15:23:40.487-07:00 [02176 warning ‘LocalPbmServer’] Failed to connect: std::exception ‘class Vmacore::Soap::InvalidResponseException’ “Invalid response code: 503 Service Unavailable”

But I then realized that PBM probably means Policy Based Management or something close which probably means the Profile Driven Storage service. I clicked on the vCenter Storage Provider screen and sure enough the following error popped up:

Popped over to the service management page and gave it a start:

You can always just run the following too:

service vmware-sps start

And voila! My next test recovery worked like a charm. So I am not sure if this was a freak thing, a version thing or just the upgrade and the service wasn’t started (most likely). But there you go, pretty simple fix. Wish the error was a bit more clear though.

So I hit up google and found a KB article and a community post:

Neither is related to SRM so I thought it was worth putting a post together.

Источник

Ken Umemoto’s vReality

I’m a Sr. Systems Engineer at a Global Environmental Engineering company. I’ve been in IT since 1999 and from 2005, my focus has been VMware datacenter products. More recently, my attention has been for Microsoft Azure services. As the Global Service Owner for VMware Datacenter products, I’ve had the pleasure of having in-depth and hands-on experience with not only VMware products, but server, storage and networking technologies.

Pages

Monday, August 14, 2017

Storage vMotion Error: A general system error occurred: PBM error occurred during PreMigrateCheckCallback: Connection refused

I just tried to perform a Storage vMotion on a VM and received the following error:

I took a look at the services running on the vCSA by running » service-control —status «. It appears the VMware vSphere Profile-Driven Storage Service (vmware-sps) had stopped.

To get the service running, just run the following command: service-control —start vmware-sps

I was then able to successfully perform a storage vMotion.

Bonus info:
Here’s a list of services running on the vsphere 6.X vCSA:

Источник