i can work on a script to do so, in short you can use
1. passwd to change the root password in the command line
2. run "/var/opt/apache-tomcat-8.5.4/bin/digest.sh -a md5 -h org.apache.catalina.realm.MessageDigestCredentialHandler NEW_PASSWORD" to get a hash.
3. put this hash into /var/opt/apache-tomcat-8.5.4/conf/tomcat-users.xml to replace the value of password.
4. reboot HCIBench.
Nov 30, 2021
Nov 15, 2021
2021-11-15 08:39:24 +0000: Validating Vdbench binary and the workload profiles...
2021-11-15 08:39:33 +0000: Validating VC IP and Credential...
2021-11-15 08:39:34 +0000: VC IP and Credential Validated
2021-11-15 08:39:34 +0000: Validating Datacenter Prod-VM...
2021-11-15 08:39:34 +0000: Datacenter Prod-VM Validated
2021-11-15 08:39:34 +0000: Validating Cluster Prod-VM-Cloud-03...
2021-11-15 08:39:34 +0000: Cluster Prod-VM-Cloud-03 Validated
2021-11-15 08:39:34 +0000: Cluster Prod-VM-Cloud-03 has DRS mode: fullyAutomated
2021-11-15 08:39:34 +0000: Validating If Any Hosts in Cluster Prod-VM-Cloud-03 for deployment is in Maintainance Mode...
2021-11-15 08:39:35 +0000: All the Hosts in Cluster Prod-VM-Cloud-03 are not in Maitainance Mode
2021-11-15 08:39:35 +0000: Validating Host 192.168.1.10 IP Address...
2021-11-15 08:39:39 +0000: Host 192.168.1.10 Address Validated
2021-11-15 08:39:39 +0000: Validating If Host 192.168.1.10 Is In Cluster Prod-VM-Cloud-03...
2021-11-15 08:39:39 +0000: ------------------------------------------------------------------------------
2021-11-15 08:39:39 +0000: Host 192.168.1.10 Is NOT In Cluster Prod-VM-Cloud-03!
2021-11-15 08:39:39 +0000: ------------------------------------------------------------------------------
govc: ServerFaultCode:
Error processing attribute "type" with value ""
while parsing MoRef for ManagedObject of type vmodl.ManagedObject
at line 2, column 312
while parsing property "obj" of static type ManagedObject
while parsing serialized DataObject of type vmodl.query.PropertyCollector.ObjectSpec
at line 2, column 301
while parsing property "objectSet" of static type ArrayOfObjectSpec
while parsing serialized DataObject of type vmodl.query.PropertyCollector.FilterSpec
at line 2, column 219
while parsing call information for method CreateFilter
at line 2, column 66
while parsing SOAP body
at line 2, column 60
while parsing SOAP envelope
at line 2, column 0
while parsing HTTP request for method createFilter
on object of type vmodl.query.PropertyCollector
at line 1, column 0
govc: ServerFaultCode:
Error processing attribute "type" with value ""
while parsing MoRef for ManagedObject of type vmodl.ManagedObject
at line 2, column 312
while parsing property "obj" of static type ManagedObject
while parsing serialized DataObject of type vmodl.query.PropertyCollector.ObjectSpec
at line 2, column 301
while parsing property "objectSet" of static type ArrayOfObjectSpec
while parsing serialized DataObject of type vmodl.query.PropertyCollector.FilterSpec
at line 2, column 219
while parsing call information for method CreateFilter
at line 2, column 66
while parsing SOAP body
at line 2, column 60
while parsing SOAP envelope
at line 2, column 0
while parsing HTTP request for method createFilter
on object of type vmodl.query.PropertyCollector
at line 1, column 0
govc: ServerFaultCode:
Error processing attribute "type" with value ""
while parsing MoRef for ManagedObject of type vmodl.ManagedObject
at line 2, column 312
while parsing property "obj" of static type ManagedObject
while parsing serialized DataObject of type vmodl.query.PropertyCollector.ObjectSpec
at line 2, column 301
while parsing property "objectSet" of static type ArrayOfObjectSpec
while parsing serialized DataObject of type vmodl.query.PropertyCollector.FilterSpec
at line 2, column 219
while parsing call information for method CreateFilter
at line 2, column 66
while parsing SOAP body
at line 2, column 60
while parsing SOAP envelope
at line 2, column 0
while parsing HTTP request for method createFilter
on object of type vmodl.query.PropertyCollector
at line 1, column 0
govc: ServerFaultCode:
Error processing attribute "type" with value ""
while parsing MoRef for ManagedObject of type vmodl.ManagedObject
at line 2, column 312
while parsing property "obj" of static type ManagedObject
while parsing serialized DataObject of type vmodl.query.PropertyCollector.ObjectSpec
at line 2, column 301
while parsing property "objectSet" of static type ArrayOfObjectSpec
while parsing serialized DataObject of type vmodl.query.PropertyCollector.FilterSpec
at line 2, column 219
while parsing call information for method CreateFilter
at line 2, column 66
while parsing SOAP body
at line 2, column 60
while parsing SOAP envelope
at line 2, column 0
while parsing HTTP request for method createFilter
on object of type vmodl.query.PropertyCollector
at line 1, column 0
govc: ServerFaultCode:
Error processing attribute "type" with value ""
while parsing MoRef for ManagedObject of type vmodl.ManagedObject
at line 2, column 312
while parsing property "obj" of static type ManagedObject
while parsing serialized DataObject of type vmodl.query.PropertyCollector.ObjectSpec
at line 2, column 301
while parsing property "objectSet" of static type ArrayOfObjectSpec
while parsing serialized DataObject of type vmodl.query.PropertyCollector.FilterSpec
at line 2, column 219
while parsing call information for method CreateFilter
at line 2, column 66
while parsing SOAP body
at line 2, column 60
while parsing SOAP envelope
at line 2, column 0
while parsing HTTP request for method createFilter
on object of type vmodl.query.PropertyCollector
at line 1, column 0
Nov 16, 2021
Both HCIBench 2.5.3 and 2.6.1 must turn this option off for the verification configuration to succeed.
Nov 16, 2021
Verify that the configuration is successful by turning off the following options.
"Specify Hosts to Deploy"
Thank you !
Nov 30, 2021
Jason,
did you put any hosts and the credential while you checked "specify hosts to deploy"?
Nov 15, 2021
HCIBench 2.6.1,Failed to verify config.
But In the same configuration, HCIBench 2.4.0 can be verified.
why is that,please ?
Nov 13, 2021
hello,
in recent 2-3 versions (surely 2.53 and latest 2.61) i see in the Grafana dashboards datastore names like "datastore-2507-02" instead of a real datastore name like "vmware_datastore" as it is configured in the vCenter/ESXi hosts.
So in order to know which datastore it is (since i'm benchmarking usually 2-3 against each other) i have to keep records which datastore was which name in Grafana
can you please advise if this is a norm ?
Thank you
Kind regards,
-vlad
Nov 15, 2021
Vlad,
the grafana just pull whatever is passed from the vSAN health service, besides the change of HCIBench version, did you upgrade the vc or vsan to the newer version at the same time?
Nov 15, 2021
yes, we keep vc, vsan and esxi always up-to date (so right now we are on 7.03ub and so on...). we test both vsan, san and nas devices - they all get the wierd names like "datastore-2507-8" etc instead of the names that are visible in vcenter.
datastore names show up in vcenter correctly, for what its worth.
Nov 15, 2021
cuz for grafana or telegraf was not changed, so i believe thats due to the change of the vsan perf service.
Load more
How do you change the password?