VMmark

 View Only
  • 1.  Can't get VMmark4 to run a quick_start test for 1 tile.

    Posted Sep 20, 2024 12:04 PM

    Hi,

    I must be missing something obvious, but I can't seem to get VMmark4 to deploy and run a single 1 tile test using quick_start mode. It deploys the VMs OK, but then just stops without running any actual test.

    The first error I see in the vmmark4service-output log is:

    [ERROR]:   Auction : completed True : errors 0 : tileTrue : std_out 'VMmark4 Weathervane Provisioning Completed with Errors : Thu Sep 19 01:06:22 AM BST 2024' : std_err ''

    The tile0 log in the deploy folder for Weathervane Version 2.1.0 (VMmark4) states: "Couldn't bring to running all data services for appInstance 1 of workload 1."

    But I have no clue what that means. The documentation and online help for v4 seems very light compared to v3.

    Has anyone else hit a similar issue? Am I missing something obvious in the setup?

    The reason I went with v4 this time was that it claimed to automate and speed up the config and deployment process. Now  regretting not going with v3 again this time round.

    Thanks, John



    ------------------------------
    John M
    ------------------------------


  • 2.  RE: Can't get VMmark4 to run a quick_start test for 1 tile.

    Broadcom Employee
    Posted Sep 24, 2024 12:03 PM

    Can you check your previous provision logs for a file called postprovision-auction-nnn.nnn.nnn.nnn.out and post it here? This contains some of the logs for setup of the auction workload which is the component that is failing.




  • 3.  RE: Can't get VMmark4 to run a quick_start test for 1 tile.

    Broadcom Employee
    Posted Sep 24, 2024 06:01 PM

    The way the auction provisioning works is that the client VM connects to the vcenter using the primeclient as a NAT gateway.  Usually this type of failure means that the client VM cannot connect to the vcenter.  As a first step can you verify that you can ping your primeclient from you client0 VM? 

    There is another log file which is missing from the logs you posted.  This is due to the fact that you are re-provisioning.  Can you look into your older provisioning logs to find the log filed named "postprovision-auction-XXX.XXX.XXX.XXX.out" and post it here?