Product Support > SPECvirt_sc2013
Fail to run benchmark with runspecvirt.sh
Tang:
Hi,
I have done clock sync and run benchmark with ./runspecvirt.sh. Then I check primectrl.out but it just not updated after a few hours.
It seems that no errors is printed to the logs. It may encounter some errors, how can I deal with it ?
Thanks a lot.
set Control.config:
NUM_WORKLOADS=1
OS: CentOS6.5
java version:
app servers:
java version "1.8.0_112"
other servers and client:
java version "1.7.0_45"
glassfish: glassfish-4.0
glassfish log: attached below
apache: apache-tomcat-6.0.44
primectrl.out :
2018-03-16 17:05:55:213 Fri Mar 16 17:05:55 CST 2018
2018-03-16 17:05:55:214 specvirt: maxPreRunTime = 1201
2018-03-16 17:05:55:214 specvirt: runTime = 7200
2018-03-16 17:05:55:214 specvirt: runTime = 600
2018-03-16 17:05:55:217 Validator: [WARNING] NUM_WORKLOADS value is: 1; should be 4
2018-03-16 17:05:55:218 Validator: [WARNING] Non-compliant configuration.
2018-03-16 17:05:55:218 [WARNING] This will be a non-compliant benchmark result!
2018-03-16 17:05:55:256 RMI server started: client1:9990
2018-03-16 17:05:55:261 [INFO] This is a perf-only benchmark run. Skipping active idle polling interval.
2018-03-16 17:05:55:261 PrimeControl: preparing client drivers.
2018-03-16 17:05:55:261 PrimeControl: PRIME_HOST 0 = client1:1098
2018-03-16 17:05:55:262 PrimeControl: Master 1: client1:1098
2018-03-16 17:05:55:264 PrimeControl: adding host client1:1098
2018-03-16 17:05:55:283 First client for 0: 192.1.1.7:1091
2018-03-16 17:05:55:289 PrimeControl: starting clients...
2018-03-16 17:05:55:289 PrimeControl: clients.length = 1
2018-03-16 17:05:55:289 PrimeControl: clients[0].length = 1
2018-03-16 17:05:55:289 PrimeControl: starting clients[0][0]: 192.1.1.7:1091
2018-03-16 17:05:55:305 PrimeControl: started client: 192.1.1.7:1091
2018-03-16 17:05:55:305 PrimeControl: PTDs not used for this benchmark run!
2018-03-16 17:05:55:306 PrimeControl: starting 1 masters.
2018-03-16 17:05:55:309 PrimeControl: master[0][0] sleeping 20 sec.
2018-03-16 17:06:15:327 PrimeControl: waiting on 1 prime client(s).
2018-03-16 17:06:15:516 Sending config to client1:1098
.
2018-03-16 17:06:16:339 setting hostsReady = true
2018-03-16 17:08:31:274 PrimeControl: Workload and prime controller builds: 79
2018-03-16 17:08:31:274 PrimeControl: awaiting runtime started signal from prime clients
2018-03-16 17:08:31:274 PrimeControl: all workloads started.
prime-client1_1098.log:
2018-03-16 17:06:15:428 Looking up SPECvirt controller: client1
2018-03-16 17:06:15:516 masterID: 0, tile: 0, workload: 0
2018-03-16 17:06:15:516 hostname: client1
Hostname of prime client: specclient1
2018-03-16 17:06:15:536 Fri Mar 16 17:05:55 CST 2018
2018-03-16 17:06:15:562 RMI server started: client1:9900
2018-03-16 17:06:15:562 Total clients: 1
2018-03-16 17:06:15:562 Adding host client1:1091
2018-03-16 17:06:15:571 Setting up clients...
2018-03-16 17:06:16:337 calling getHostVM() on jappclient...
2018-03-16 17:08:31:275 Starting drivers and waiting for Steady State...
client-192.1.1.7_1091.log:
2018-03-16 17:05:55:465 Creating jappclient using RMI Registry port 1091
2018-03-16 17:05:55:500 specclient1:1091 ready...
Driver Host: specclient1 Tile Number:0
2018-03-16 17:06:15:597 matchOut() messages set ...
2018-03-16 17:06:15:598 Starting rmiregistry; bindWait = 45000
2018-03-16 17:07:00:598 Starting Controller; bindWait = 45000
2018-03-16 17:07:00:603 waiting for: Binding controller to /
rec'd notifyInterrupt(101) call
Binding controller to //specclient1:2098/ControllerLauncher: done in waitMatch(0)
2018-03-16 17:07:46:168 Starting Agents
---------------//specclient1:2098/Controller
Calling switchLog as master
url[0] is : http://specemulator:8080/Emulator/EmulatorServlet?cmd=switchlog
url[1] is : http://specdelivery:8000/Supplier/DeliveryServlet?cmd=switchlog
calling driver.waitMatch(0)...
2018-03-16 17:08:31:277 waiting for: waiting2ramp
RunID for this run is : 17
Output directory for this run is : /opt/SPECjAppServer2004/output/17
loadFactor=5
changeRate=30
burstyCurve from run.properties=37,72,61,87,132,77,0,49,137,93,187,103,174,138,200,173,153,107,225,44,36,44,48,68,138,125,116,88,38,50
scaleFactor=1.0
Curve avg txRate = 100.0
maxTxRate=225
tileNumber=0
Will run in bursty mode after rampup/warmup phases. Starting at burstPoint:0
WarmUp style = 0 (0=linear only, 1=burstycurve, 2=zigzag)
Phase one of warm up (start of transaction activity) will increase IR from 0 to 100 linearly, over 900 seconds.
Steady-State IR transition stepRate(ms)=40000
Burst Curve StartPoint Tile Multiplier=7
smoothFactor=1
Using default timeSkewTolerance value: 3
Mar 16, 2018 5:08:32 PM com.sun.enterprise.v3.server.CommonClassLoaderServiceImpl findDerbyClient
INFO: Cannot find javadb client jar file, derby jdbc driver will not be available by default.
Mar 16, 2018 5:08:32 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: list ==> specdelivery:3700
Mar 16, 2018 5:08:32 PM org.glassfish.enterprise.iiop.impl.GlassFishORBManager getCorbalocURL
INFO: corbaloc url ==> iiop:1.2@specdelivery:3700
Tang:
I also checked glassfish server log and searched 'error', and did't find any 'error' printed.
ChrisFloyd:
Tang,
I see in one location where it appears to be connecting to client with hostname client1, but refers to hostname primeclient1 elsewhere, and appears to be configured by numeric IP in the Control.config file. Can you please provide the Control.config file used for this test, and a brief summary of your client topology and hostnames/IPs? Thanks,
Tang:
Hi，ChrisFloyd
The below script is /etc/hosts in client1. In other six vm servers, this file is the same except the red part, for example, in infraserver the red part is modified to 'infraserver1'.
All vm servers and client are connected with virtual eth0 with 192.1.1.x. Infraserver, webserver, appserver, dbserver and client are connected with virtual eth1 with 192.2.1.x.
There is not virtual eth1 in mailserver or batchserver. All servers and client are now running on one physical machine.
Control.config is attatched below.
/etc/hosts:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 specclient1
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.1.1.1 infraserver1 infraserver1-ext infraserver
192.1.1.2 webserver1 webserver1-ext webserver
192.1.1.3 mailserver1 mailserver1-ext mailserver
192.1.1.4 appserver1 appserver1-ext specdelivery specemulator appserver
192.1.1.5 dbserver1 dbserver1-ext specdb dbserver
192.1.1.6 batchserver1 batchserver1-ext batchserver
192.2.1.1 infraserver1-int besim infraserver-int
192.2.1.2 webserver1-int webserver-int
192.2.1.3 mailserver1-int mailserver-int
192.2.1.4 appserver1-int appserver-int
192.2.1.5 dbserver1-int dbserver-int
192.2.1.6 batchserver1-int batchserver-int
192.1.1.7 specclient1 client1 specdriver specclient
192.1.2.7 specclient2 client2
192.1.3.7 specclient3 client3
192.1.4.7 specclient4 client4
192.1.5.7 specclient5 client5
192.1.6.7 specclient6 client6
192.1.7.7 specclient7 client7
192.1.8.7 specclient8 client8
192.1.9.7 specclient9 client9
Thanks.
Tang:
I've changed client hostname to client1 and set hostname with command "hostname client1", and modified /etc/sysconfig/network to set HOSTNAME=client1.
The problem is still the same.
/etc/hosts:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 client1
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
192.1.1.1 infraserver1 infraserver1-ext infraserver
192.1.1.2 webserver1 webserver1-ext webserver
192.1.1.3 mailserver1 mailserver1-ext mailserver
192.1.1.4 appserver1 appserver1-ext specdelivery specemulator appserver
192.1.1.5 dbserver1 dbserver1-ext specdb dbserver
192.1.1.6 batchserver1 batchserver1-ext batchserver
192.2.1.1 infraserver1-int besim infraserver-int
192.2.1.2 webserver1-int webserver-int
192.2.1.3 mailserver1-int mailserver-int
192.2.1.4 appserver1-int appserver-int
192.2.1.5 dbserver1-int dbserver-int
192.2.1.6 batchserver1-int batchserver-int
192.1.1.7 specclient1 client1 specdriver specclient
192.1.2.7 specclient2 client2
192.1.3.7 specclient3 client3
192.1.4.7 specclient4 client4
192.1.5.7 specclient5 client5
192.1.6.7 specclient6 client6
192.1.7.7 specclient7 client7
192.1.8.7 specclient8 client8
192.1.9.7 specclient9 client9
Navigation
[0] Message Index
[#] Next page
Go to full version