PowerCLI service failed to start

[tjlst15]

I'm unable to start my benchmark due to the PowerCLI service failing to start.  This is the error I'm getting:

VMmark2 PSfe 1.2

  Increased PowerCLI Service Delay : 5 : 5

  Starting Up VMmark2PS Workers :   Increased delay(5) : Started 4

  Loadtime  = 00:00:18.84

  Polling Workers State ::

   1 : Error!

   3 : Error!

   5 : Error!

   7 : Error!

Error Initializing Workers

  Errors Found : 4

  Workers Ready : 0

Error Initializing Workers (4) : Halting Workers : Purging Qs : Done

I've found this similar issue on another thread, but it doesn't seem to apply to my situation: VMmark2 PowerCLI Service Failed to Start :: Workers Ready:0

[fredab2]

Can you upgrade PowerShell to version 2 or later (I believe you are running v1.0)?

     \System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;c:\windows\ruby;c:\windows\ruby\bin;C:\Program Files (x86)\Symantec\Critical System Protection\Agent\IPS\bin;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;.

Regards,

Fred

[tjlst15]

The version of powershell is 3.0:

PS C:\VMmark2\results\Results_20141014063954_testing> $PSversionTable.PSVersion

Major  Minor  Build  Revision

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

3      0      -1     -1

[fredab2]

Try and increase the "RMQ_PowerCLI" and "RMQ_WorkerDelay"  inside  VMMARK2.CONFIG .

     RMQ_WorkerDelay=60

     RMQ_PowerCLI_Delay=120

If this still fails,  please zip up and send C:\vmmark2\tmp directory from Prime Client.

Regards,

Fred

[tjlst15]

That did not work.  have same error.  tmp direectory is attached.

[stephenhowellvc]

Looks like I have the same error. Was this ever resolved?

[lroderic]

Hello. It looks like it wasn't resolved. Please set DEBUGFLAG=1, rerun, and post the Results zip file. Thanks.

Lisa

[dadayayak]

I got the same errors and no useful error messages for debug.

[lroderic]

A couple of things. Your VMMARK2.CONFIG says the client is vclient0 and your mail domain is maildomain0.datrium.com. The error at the bottom of STAX_Job_14.log says it's trying to communicate with primeclient.maildomain0.vmmark.datrium.com. Would you please check that the names you supply to VMMARK2.CONFIG are the actual names of the client and the domain?

Lisa

[keshavkant]

Hi ,

Please Try first to  increase the "RMQ_PowerCLI" and "RMQ_WorkerDelay"  inside  VMMARK2.CONFIG and then check s service not started or not.

     RMQ_WorkerDelay=60

     RMQ_PowerCLI_Delay=120.

[dadayayak]

I have fixed VMMARK2.CONFIG file but still got the same errors.

I have looked into VMmark2PSbe0.txt (also VMmark2PSbe1.txt, VMmark2PSbe2.txt VMmark2PSbe3.txt):

They all stop at:

   VMmark2PSbe 1.2 waiting for commands : 08/27/2015 11:49:18 : 0

Not sure which log to find further information.

Thanks

[lroderic]

The MailQualifier is incorrect in VMMARK2.CONFIG. It needs to read "vmmark.datrium.com" not "maildomain0.vmmark.datrium.com".

Also, it would be good to disable PTD for now to make troubleshooting easier.

Are you running the prime client split from vclient0? Typically these are combined, so in your environment, your prime client would be "vclient0" and not "primeclient".

Lisa

[dadayayak]

I have put them together and disabled PTD but still stuck at VMmark2PSbe.

What should I expect from VMmark2PSbe.ps1?

I try to run VMmark2PSbe.ps1 directly and I hit it only prints out:

    VMmark2PSbe 1.2 waiting for commands : 08/27/2015 17:22:20 : 0

I think something is missing but I don't where I can find the info.

Thanks

[RebeccaG]

I think you are saying that you put the prime client (aka the VMmark harness) and the client0 (which generates load for tile 0) on the same machine, correct? If the hostname of that machine is "primeclient", then in VMMARK2.config, set

CLIENTS="primeclient"

From the prime client, make sure you can ping both primeclient and primeclient.maildomain0.vmmark.datrium.com. Do you have a vclient0 anywhere in your environment?

2. Like Lisa mentioned, in VMMARK2.config, please change

MailServer/MailQualifier="maildomain0.vmmark.datrium.com"

to

MailServer/MailQualifier="vmmark.datrium.com"

3. In VMMARK2.config, please change

# ERRORIMMEDIATE=0

to

ERRORIMMEDIATE=1

There is an earlier error during the run that is being bypassed and we want to make sure the run stops after the first error is encountered so we can fix one thing at a time.

[dadayayak]

Thanks for all reply.

Unfortunately I still hitting the same errors

I have been now reconfig as following:

1. primeclient and client0 are on same physical machine.

2. in VMMARK2.CONFIG: CLIENTS="primeclient" (I have tried client0 also)

3. java is installed in c:\java on all windows machines/VMs

4. all staf are same version of 3.4.10 except for standby0

5. set ERRORIMMEDIATE=1

6. use vsphere powercli 5.8 with powershell v2.0

Thanks.

[jpschnee]

Hello,

Have you possibly modified any of the VMmark2 source code?  Specifically VMmark2PSfe.ps1 or VMmark2PSbe.ps1?  If not, please zip them up and attach them to the thread please. 

[dadayayak]

yes. I recently add several print out statement to see where the code stucks as following:

		# debug starts
		WriteOut "  4. VMmark2PSbe.ps1 in the loop" "debug"
		# debug ends

[dadayayak]

the codes are here. I have only include all ps1 files. It is too big to attach whole tool directory.

[dadayayak]

It seems to me it is waiting for messages from Rabbit server.

That is where it stucks.

What is expecting from RMQserver? Test Commands?

[jpschnee]

We'll need for you to restore the original source code before we can help.  The output that your scripts are generating are very different from what I'm expecting.  I encourage your to rename your existing VMmark2 directory to "VMmark2-MODIFIED" and reinstall both VMmark 2.5.0 and the VMmark2.5.2 Patch from original packages.  Afterwords make sure that none of the *ps1 scripts are being blocked and that powershell has been given the proper permissions.  Then give it another try and if it fails upload the results folder here.