4 Replies Latest reply on May 2, 2019 11:56 AM by dmorse

    VMmark ERROR and config help

    jefcisco Lurker
    jefcisco Apr 29, 2019 7:25 AM

      Hi,

       

      Looking for some help or guidance as to why I continue to see this error. My DeployVM field has these type of entries --> AuctionAppA0: 10.x.x.x then the 18 other ones. I'm assuming the issue is with my VMmark3.properties config file, but not sure at this point.

       

      ERROR:

       

      2019-04-29T07:16:00.689 [pool-3-thread-20] ERROR COMM : Error Ip not found for AuctionAppA0 : Ip null : Try increasing ProvisionPingIpSeconds in VMmark3.properties : Continuing

      2019-04-29T07:16:00.692 [pool-3-thread-20] ERROR COMM : IP not found : AuctionAppA0

      2019-04-29T07:16:00.692 [pool-3-thread-20] ERROR ST220 : Terminating Early Due to Provision Thread Errors (1)

      2019-04-29T07:16:00.701 [pool-3-thread-20] ERROR MAIN : Exception Caught: Terminating Early Due to Provision ThreadErrorsErrorsFound: 1 : exitSetting true

       

      Any help is much appreciated

      • 420 Views
      • Tags:
        • 1. Re: VMmark ERROR and config help
          jefcisco Lurker
          jefcisco Apr 29, 2019 7:42 AM (in response to jefcisco)

          I've increased ProvisionPingIpSeconds from 600 to 1200 and still the same error.

           

          Here is the message sent to me via email:

           

          VMmark3Service_v1.0.17 Finished

           

          Summary::

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

            Terminating Early Due to Provision ThreadErrors :: Error Detail (if applicable): ErrorsFound: 1 Error Output:: Found 1 Errors IP not found : AuctionAppA0TimeElapsed: 1245 (secs)

          • 2. Re: VMmark ERROR and config help
            dmorse Enthusiast
            VMware Employees
            dmorse Apr 29, 2019 11:42 AM (in response to jefcisco)

            Hi jefcisco

             

            I'd like to see your VMmark3.properties and the contents of the provisioning-output directory.
            Here are the commands to run on your PrimeClient VM to grab both:

             

            cd /root/VMmark3/

            zip -r provision_jefcisco.zip VMmark3.properties provisioning-output/

             

            Please reply to this message and attach the corresponding .zip file.

             

            Thanks,

            David

            • 3. Re: VMmark ERROR and config help
              dmorse Enthusiast
              VMware Employees
              dmorse Apr 30, 2019 7:52 AM (in response to dmorse)

              jefcisco Thanks for sending the requested .zip (also attached in this reply).

               

              Your PrimeClient has an IP of 10.199.135.11 with a subnet mask of 255.255.255.0.  The VMmark3 benchmark harness created Client0, as shown from the log file below, powered it on, but could not ping it:

              2019-04-29T14:15:38.010 [pool-3-thread-17] INFO  COMM : Client0 Attempting to Ping at 10.199.135.31

              2019-04-29T14:18:50.299 [pool-3-thread-17] WARN  COMM : Client0 : All pings failed at 10.199.135.31 : Remediating

              2019-04-29T14:18:50.302 [pool-3-thread-17] INFO  vCSc : RemediateVM: Client0

              2019-04-29T14:18:50.327 [pool-3-thread-17] INFO  vCSc : DVS Disabled: NetworkLabel VM Network

              2019-04-29T14:18:52.353 [pool-3-thread-17] INFO  vCSc : Updated Client0 to use NetworkLabel VM Network and verified connected state

              2019-04-29T14:18:52.356 [pool-3-thread-17] INFO  COMM : RemediatedPing Client0 : Scanning for IP

              2019-04-29T14:18:52.369 [pool-3-thread-17] INFO  COMM : RemediatedPing Client0 Attempting to Ping at 10.199.135.31

              2019-04-29T14:19:16.413 [pool-3-thread-17] ERROR COMM : RemediatedPing Client0 : All pings failed at 10.199.135.31

              This means you will need to do some troubleshooting from your PrimeClient and/or vCenter to figure out why your PrimeClient can't ping Client0.  Some possibilities/things to check:

              • Is 'VM Network' is the right NetworkLabel? If not, uncomment and change the line in your VMmark3.properties file that reads "ProvisioningNetworkLabel = VM Network"
              • Are you using a standard vSwitch (default)?  If not (a distributed vSwitch), uncomment and change the line in your VMmark3.properties file that reads "ProvisioningNetworkType = standard" to "dvswitch".
              • Double check your other network settings for accuracy, namely:
                // String ProvisioningIPstaticStart : First IP address to use. Valid ranges are 1-245
                ProvisioningIPstaticStart = 10.199.135.31
                // String ProvisioningGateway : Gateway to use for static VM provisioning : Default 192.168.1.253
                ProvisioningGateway = 10.199.135.1
                // String ProvisioningSubnetMask : Subnet mask to use for static VM provisioning : Default 255.255.252.0
                ProvisioningSubnetMask = 255.255.255.0

              Long story short, in order for provisioning to succeed, you'll need to be able to ping client0 from your PrimeClient VM, and you can't right now.

               

              Here is what you're likely seeing ("bad" case):

              [root@primeclient ~]# ping 10.199.135.31

              PING 10.199.135.31 (10.199.135.31) 56(84) bytes of data.

              From 10.199.135.11 icmp_seq=10 Destination Host Unreachable

              From 10.199.135.11 icmp_seq=11 Destination Host Unreachable

               

              Here is what you need to see ("good" case):

              [root@primeclient ~]# ping 10.199.135.31

              PING 10.199.135.31 (10.199.135.31) 56(84) bytes of data.

              64 bytes from 10.199.135.31: icmp_seq=1 ttl=64 time=0.142 ms

              64 bytes from 10.199.135.31: icmp_seq=2 ttl=64 time=0.162 ms

              64 bytes from 10.199.135.31: icmp_seq=3 ttl=64 time=0.188 ms

              ^C

              --- 10.199.135.31 ping statistics ---

              3 packets transmitted, 3 received, 0% packet loss, time 1999ms

              rtt min/avg/max/mdev = 0.142/0.164/0.188/0.018 ms

               

              Please let me know how it goes.

               

              Thanks,

              David

              • 4. Re: VMmark ERROR and config help
                dmorse Enthusiast
                VMware Employees
                dmorse May 2, 2019 11:56 AM (in response to dmorse)

                Just to update / close out this thread: I heard back from jefcisco privately, and confirmed he was able to successfully deploy 1 tile (tile0):

                 

                Hi David,

                 

                Thanks for following up. Sorry been extremely busy with multiple projects.

                 

                The issue was a two pronged problem

                 

                1. Incorrect Network Label in the VMMark3.properties file
                2. The ESXi server client server had an incorrect Network adapter config

                 

                So I corrected both things and the “java -jar” command succeeded finally. Also just checked the DS3DB0 database creation and saw this which is a good sign.

                 

                [root@DS3DB0 ~]# tail -f /ds3/VMmark3-DS3installoutput.txt

                Warning: Using a password on the command line interface can be insecure.

                Loading Membership data

                Warning: Using a password on the command line interface can be insecure.

                Loading Reviews data

                Warning: Using a password on the command line interface can be insecure.

                Loading Reviews Helpfulness Ratings Data

                Warning: Using a password on the command line interface can be insecure.

                Removing data files

                Thu May  2 08:30:20 PDT 2019

                VMmark3 DS3DB Setup Completed : Rebooting

                 

                James