SPECvirt ® Datacenter 2021 Technical Support

svdc-director

  1. You can submit a measurement manually:

./submit.sh -c ../config/cloudpump.xml -w ../config/workloads/specvirt/workload.xml -d ../config/workloads/specvirt/deployment.xml -r ../config/workloads/specvirt/run.xml

  1. If you receive an error message:

Failed to connect to master svdc-director:19998 java.rmi.ConnectException: Connection refused to host: svdc-director; nested exception is: java.net.ConnectException: Connection refused (Connection refused)

Run $CP_BIN/resetprimes.sh.

3. vSphere 7.0.3 and later only supports ECDSA with SSH. To add ECDSA support between svdc-director and the vSphere hosts, on svdc-director issue the following:

ssh-keygen -t ecdsa -f /root/.ssh/id_ecdsa -N ''
for Host in `grep Host /etc/hosts | awk '{print $1}'`
do
    cat ~/.ssh/id_ecdsa.pub | ssh $Host 'cat >> /etc/ssh/keys-root/authorized_keys'
    ssh $Host 'chmod +t /etc/ssh/keys-root/authorized_keys'
    ssh $Host '/etc/init.d/SSH restart'
done

  1. The reporter requires requires a space after each blank line with an “= ” in Control.config. A missing space after each blank line with an “= ” results in the following error:

                      SPECvirt® Datacenter 2021 Reporter 1.0
 Copyright (c) 2010-2022 Standard Performance Evaluation Corporation
 --------------------------------------------------------------

 > Raw Result File - specvirt-datacenter-2022-07-07_14-31-43.raw

 > Generating Reports in HTML Format

 > Verifying Raw Result File..

 > Renaming Raw Result File: specvirt-datacenter-2022-07-07_14-31-43.raw.backup

 > Loading Raw Result File..

 > Recreating Raw Result File: specvirt-datacenter-2022-07-07_14-31-43.raw

Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 1
      at org.spec.virt.reporter.Results.loadLinkedHashmapConfig(Results.java:340)
      at org.spec.virt.reporter.Results.rewriteResFile(Results.java:171)
      at org.spec.virt.reporter.Reporter.main(Reporter.java:166)

The Control.config distributed with the kit is correct, so recheck your changes to Control.config.

Clients

For problems deploying clients, check the following.

  1. Ensure that the svdc-template’s and svdc-director’s virtual NIC has assigned the correct MAC address. Check the svdc-template’s eth0 vNIC settings to ensure that the MAC prefix (the first three octets) assigned to the vNIC matches the value for MACAddressPrefix that you set in Control.config for the testbed network. The default for svdc-template is 42:44:49:00:00:00. The default for svdc-director is 42:44:49:00:00:02.

  2. Ensure that the svdc-director’s virtual NIC has assigned the correct IP address. Check that the svdc-director’s IP address uses the value of IPAddressPrefix and 0.2. The default IP address for the svdc-director is 172.23.0.2.

  3. Use ping to make sure that the svdc-director can contact the management server.

Submissions

If you encounter problems during the collection of the support tarball archive at the end of a measurement, you can rerun ${virtVendor}/collectSupport.sh manually. The support archive is valid as long as you haven’t made changes to the testbed.

For submissions on vSphere, make sure to add the sutHost alias for each vSphere server to /etc/hosts as described in Section 3.2.5.4 of the SPECvirt Datacenter 2021 User Guide. Issue the following commands to capture non-default ESXi settings:

cd $CP_RESULTS/<results-directory>
. /export/home/cp/bin/getVars.sh
for i in $(seq 1 $numHosts);
do
   echo "Non-default settings on sutHost${i}" > sutHost${i}-esx-conf-non-defaults.txt
   echo "===================================" >> sutHost${i}-esx-conf-non-defaults.txt
   ssh sutHost${i} "esxcli system settings advanced list -d" >> sutHost${i}-esx-conf-non-defaults.txt
done

Please include all the esx-conf-non-defaults.txt files in the submission.

HammerDB

  1. HammerDB creation during prepSUT.sh takes a long time and appears to hang. CPU utilization on the svdc-director is idle, and the console output reads:

... ALL VIRTUAL USERS COMPLETE hammerdb>DB load successful. Creating DB backup. **Note, this takes several minutes (or more). Please be patient...

This pause occurs as the harness backs up the HammerDB database on the svdc-director and could take several hours.

  1. To monitor active HammerDB transactions during a measurement:

  1. Get the “jobid” from http://svdc-txxx-happ:8080/jobs

  2. Enter the “jobid” at http://svdc-txxx-happ:8080/jobs?jobid=[jobid] and refresh browser to see updates

  1. If HammerDB reports no transactions, check if:

  • svdc-t*-hdb doesn’t have /opt/hammerdb_mysql_backup/hammerDB-backup.tgz with size = 13281381806

  • svdc-t*-happ /opt/HammerDB/*tcl.orig doesn’t contain svdc-t*-hdb and instead contains TARGETHOST

prepSUT.sh failed. Rerun $CP_COMMON/prepSUT.sh, tail -f $CP_COMMON/prepSUT.log for output.

BigBench

To access the BigBench web console and monitor transaction job history:

http://svdc-txxx-bbnn:19888/jobhistory/app - shows history of 38 jobs completed during initial load as well as all past jobs

http://svdc-txxx-bbnn:8088/cluster/apps - monitor active BigBench jobs

http://svdc-txxx-bbnn:8088/cluster/nodes - monitor BigBench data node status

To check the status of BigBench services:

ssh svdc-txxx-bbnn "/opt/createApacheCluster/checkHadoopStatus.sh"

Copyright 2021 Standard Performance Evaluation Corporation (SPEC). All rights reserved.