Simple Weathervane crashes in DB

[mathieugont]

Dear community

Could someone help me to figure out what is going wrong?

I just setup Weathervane in the VMmark virtual machine. The installation seems ok, but when I run weathervane manually with the defaults weathervane.config, it stops with the following error:

[root@vmmark3 weathervane]# ./weathervane.pl

Tue Jan 21 05:49:43 2020: Weathervane Version VMmark3.1

Tue Jan 21 05:49:43 2020: Command-line parameters:

Tue Jan 21 05:49:43 2020: Run Configuration has 1 workloads.

Tue Jan 21 05:49:43 2020: Workload 1 has 1 workload-driver nodes

Tue Jan 21 05:49:43 2020: Workload 1 has 1 application instances.

Tue Jan 21 05:49:43 2020: Workload 1, Application Instance 1 configuration:

Tue Jan 21 05:49:43 2020:       1 ConfigurationManagers

Tue Jan 21 05:49:43 2020:       0 ElasticityServices

Tue Jan 21 05:49:43 2020:       1 CoordinationServers

Tue Jan 21 05:49:43 2020:       0 LbServers

Tue Jan 21 05:49:43 2020:       1 WebServers

Tue Jan 21 05:49:43 2020:       1 DbServers

Tue Jan 21 05:49:43 2020:       1 NosqlServers

Tue Jan 21 05:49:43 2020:       0 FileServers

Tue Jan 21 05:49:43 2020:       1 MsgServers

Tue Jan 21 05:49:43 2020:       1 AppServers

Tue Jan 21 05:49:43 2020:       maxDuration = 7200

Tue Jan 21 05:49:43 2020: Running Weathervane with Single-Run RunManager using Full-Run RunProcedure.

Tue Jan 21 05:49:43 2020: Single-Run RunManager starting run.

Tue Jan 21 05:49:44 2020: Stopping running services and cleaning up old log and stats files.

Tue Jan 21 05:49:59 2020: Preparing data for use in current run.

Tue Jan 21 05:49:59 2020: Configuring and starting data services for appInstance 1 of workload 1.

Tue Jan 21 05:51:00 2020: Backup is not available at the proper scale for 300 users for appInstance 1 of workload 1. Loading data.

Tue Jan 21 05:51:49 2020: Workload 1, appInstance 1: Loading data for a maximum of 300 users

Tue Jan 21 05:52:03 PST 2020: Loading data -- Initial estimate of total load time is 0 hours, 0 min, 13 sec. Workload 1, appInstance 1.

Tue Jan 21 05:52:10 PST 2020: Loading is 13.1% complete.  Current estimate of remaining load time is 0 hours, 0 min, 12 sec. Workload 1, appInstance 1.

Tue Jan 21 05:53:14 2020: Data is still not loaded at proper scale.  Check the logs of the data services for errors.

Looking at the logs, it seems the issue comes from /root/weathervane/output/0/setupLogs/isDataLoaded-AuctionDriver1.log:

ssh -o 'StrictHostKeyChecking no' root@AuctionDriver1  java -client -cp /root/weathervane/dist/dbLoader.jar:/root/weathervane/dist/dbLoaderLibs/*:/root/weathervane/dist/dbLoaderLibs -Dspring.profiles.active="postgresql,ehcache,imagesInMon05:31:39.493 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check 05:31:39.971 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check

05:31:40.208 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check 05:31:40.301 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check

05:31:40.359 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check 05:31:40.412 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check

05:31:40.465 [main] WARN  o.s.d.m.c.convert.CustomConversions - Registering converter from class java.lang.Number to class java.lang.Number as writing converter although it doesn't convert to a Mongo supported type! You might wanna check Exception in thread "main" java.lang.RuntimeException: Cannot find benchmarkInfo in database.  Make sure that data is preloaded.

        at com.vmware.weathervane.auction.dbloader.DBPrep.main(DBPrep.java:187)

256

Thanks for your help.

[fredab2]

Looking through the community posts it looks like you have been having issues with getting Weathervane running for some months now since original deployment.

Were you ever successful in executing Weathervane through the VMmark3 harness since you have deployed?

I would suggest using the harness to test individual workloads vs going into the scripts and doing it manually. 

You can edit the lines below in your  VMmark3.properties to not run any infrastructure operations and only Weathervane.

InfrastructureList =

WorkloadList : AuctionLB,AuctionWebA,AuctionWebB,AuctionAppA,AuctionAppB,AuctionDB,AuctionMSQ,AuctionNoSQL

Let me know how this goes.

Regards,

Fred