VMmark 3 Exceute VMmark3.properties Error: Get Current Controller Null Exception ... ?

[Donjonduan]

Hi all,

I configured vmmark.properties according to the manual, after the implementation of "java -jar tools/VMmark3Service.jar -c VMmark3.properties" suggested the following error.

---------------------------------------------------------------------------------------

VMmark3Service_v1.0.0 Finished

Summary::

/root/VMmark3/provisioning-output/vmmark3-output/

Get Current Controller Null Exception : Review Log and Configuration :  :: Error Detail (if applicable): check template Error Output:: Found 0 Errors

TimeElapsed: 4 (secs)

Get Current Controller Null Exception : Review Log and Configuration :  :: Error Detail (if applicable): check template Error Output:: Found 0 Errors

TimeElapsed: 4 (secs)

...

------------------------------------------------------------------------------------------

Additional config Files:

Thanks!

[fredab2]

Looking at the vm3pro.log file you attached,  you don't have any ProvisioningDatastores defined.

          ProvisioningDatastores = \

Define a Provisioning Datastore for each VMmark3 VM you want to deploy where the initial part /vmfs/volumes is assumed. So to deploy DS3DB on LUN = /vmfs/volumes/ds3db_lun and DS3WebA on LUN = /vmfs/volumes/ds3web_lun then your ProvisioningDatastores line would look like the following:

          ProvisioningDatastores = DS3DB:ds3db_lun,DS3WebA:ds3web_lun

Fred

[Donjonduan]

Hi Fred,

     Thank you for your answer ! According to your meaning, will provisioning Datastore changed to /vmfs/volumes/EX6Uxxx. But still suggested on the Datastore error.

" Exception Caught: Provision targetDatastore Null VM Exception : Review Log and Configuration : Unable to locate targetDatastore: "

In ESXi shell use df -h or esxcli storage command can see the Datastore mount is normal(Including VC) ,

Try replacing the volume name with UUID as if it werre wrong.

Tks!

Atteched:     vmmark3.properties and log

[fredab2]

I looked at the current VMmark3.properties you sent and the previous log file you sent. And you had the correct format in the first attempt you sent  which is:

CORRECT

-------------

ProvisioningDatastores = \

Client:EX6U3CLI,\

DS3WebA:EX6U3QTR,\

DS3WebB:EX6U3NOT,\

So please put the VMmark3.properties back to the above format (no /vmfs/volumes). Rerun provisioning and zip up the entire directory /root/VMmark3/provisioning-output/vmmark3-output and send to me.

Fred

[Donjonduan]

Hi Fred,

     Change to the above format, Run Java... after the error still.

Tks!

attached: vmmark3-output dir

[jpschnee]

Hello,

A couple of things to try and help us sort out your issue.

1. Can you try a manual deploy of the VM you specified 'vmmark3'?
   1. From the vSphere Web UI.  Right click on the VM and select "Clone to Virtual Machine".
   2. Select the Datacenter specified "VC6U3".
   3. Select the Cluster specified "VMMARK3SRV".
   4. Select the Host "10.0.90.3"
   5. Select the Datstore "EX6U3QTR"
   6. Check the boxes for "Customize this virtual machine's hardware (Experimental)" and "Power on virtual machine after creation"
   7. Change the Network Adapter 1 to use the virtual switch specified "DVLAN200" and make sure the Connect... box is selected.
   8. Click Finish
   9. Once it's done, report back on the status of this manual operation.
2. In your VMmark3.properties file please set "DebugLevel = 3" and rerun.  Afterward, please zip up the output and attach to this thread.

[Donjonduan]

Hi jpschnee

     I have tried manual deploy of the VM, But a new error. " Updated vmmark3 to use NetworkLabel DVLAN200 and verified connected state   ERROR MAIN : Exception Caught: Provisioning Validation FAILEDReview Log For Details : exit Setting true" I try to ping 192.168.200.x in vmmark3 or PrimeClient, They are alive.

Tks!

Attached:

[jpschnee]

The error:

ERROR MAIN : Provisioning Validation FAILED

2017-07-28T19:26:50.651 [main] ERROR MAIN : Exception Caught: Provisioning Validation FAILEDReview Log For Details : exitSetting true

Is telling you to review the provisioning log.  When I reviewed yours I see that the first error was:

2017-07-28T19:26:48.747 [main] ERROR vCSc : VM: ElasticDB0 Already Present

The problem is that you have successfully deployed tile 0 (20 VMs) but are attempting to tell the provisioning service to deploy tile 0 again.  If you want to re-deploy tile0 you'll need to delete the VMs first.  The service jar can do this via the tileDelete command, see the help output for details.  If you want to deploy the second tile (tile 1), then you'll need to update your VMmark3.properties file and change the following:

RunName = vmmark3-output-tile1

ProvisioningSource = tile0

ProvisioningNumTiles = 2  // don't forget to uncomment this in your file.