my SUT is a 4-node cluster(using vSAN as primary storage), i used it to execute VMmark3 7-tile test(not turbo mode)
the STAX job monitor showed that the "VMmark Results Collection" failed; other stages are passed and good
the problem is, same errors has occurred for so many times:
1. on the STAX monitor there are somes errors showed up:
Error: Tile 0 Weathervane results number not correctly identified
Error: Tile 4 Weathervane results number not correctly identified
Error: Tile 5 Weathervane results number not correctly identified
Error: Tile 6 Weathervane results number not correctly identified
Could not Collect all Results for the following 4 Wklds: ['AuctionLB Tile0 failed results collection', 'AuctionLB Tile4 failed results collection', 'AuctionLB Tile6 failed results collection', 'AuctionLB Tile5 failed results collection']
Warning: VMmark may not have completed successfully. Check for results manually, see documentation for instructions.
to deal with this, i use tilescore.pl to generate scores but the parameters seemed not work, same errors showed up:
A. tried the command: perl ../../tools/tilescore.pl -t 7 -E
VMmark 3.0 TileScore : v1.0 05222017
Computing_results_for_test_with_tile_count: 7 ...
Error : WeathervaneAuction0.wrf does not exist, exiting
B. tried the command: perl ../../tools/tilescore.pl -t 7 -D
VMmark 3.0 TileScore : v1.0 05222017
Computing_results_for_test_with_tile_count: 7 ...
Error : WeathervaneElastic0.wrf does not exist, exiting
C. tried the command: perl ../../tools/tilescore.pl -t 7 -E -W
VMmark 3.0 TileScore : v1.0 05222017
Computing_results_for_test_with_tile_count: 7 ...
First Sample: 1523843640 Mon Apr 16 01:54:00 2018
Use of uninitialized value in concatenation (.) or string at ../../tools/tilescore.pl line 2622.
Info: 186 : : 7 : 4
Undefined times at 186
Error : could not resolve start-time. Results data missing from one or more *.wrf files or time on clients not synchronized
basically, the scores and graph.html could not be generated, i've read the user guide and hope did not miss any paragraph.
i've checked the journalctl_SYSTEMD_UNIT=startstaf.service file and...
there are only two errors:
ERROR ST84 : DeployVM0 : All pings failed at 10.101.6.240 : Try increasing ProvisionPingMaxTries in VMmark3.properties
ERROR MAIN : VMmark3 Service Thread Pool not shutdown cleanly : Exceed maximum timeframe : Creating Stop File
i didn't see "deploy remediation warning", "error verylow-disk-space" or "get guest info did not run correctly"...
any ideas?
i could only imagine that these problems were due to the client VMs' hosts have insufficient computing resources?
or due to second or third shared storage space too small?
or vmmark3-template at wrong storage?
thanks for reading my article, hope i can also solve others' problems.
related files are attached.