thread does not exist in autopilot mode on RedHat

[ma44in]

I try to execute HammerDb in Autopilot Mode to build a Db2 test schema as follows.

I've created following "Autopilot"-File.

build_db2_schema.tcl File:

global complete
proc wait_to_complete {} {
  global complete
  set complete [vucomplete]
  if {!$complete} { after 5000 wait_to_complete } else { exit }
}

puts "SETTING CONFIGURATION"
dbset db db2
dbset bm TPC-C
diset tpcc db2_num_vu 4
diset tpcc db2_count_ware 4
diset tpcc db2_dbase test1
diset tpcc db2_user test1
diset tpcc db2_pass test1
diset tpcc db2_def_tab DATA01
print dict
buildschema
wait_to_complete

Then I start hammercli and in crashes with the "Error from thread"-Message.

$ export LD_LIBRARY_PATH="/opt/IBM/clidriver/lib"
$ ./hammerdbcli auto build_db2_schema.tcl
HammerDB CLI v4.4
Copyright (C) 2003-2022 Steve Shaw
Type "help" for a list of commands
The xml is well-formed, applying configuration
SETTING CONFIGURATION
Database set to Db2
Benchmark set to TPC-C for Db2
Changed tpcc:db2_num_vu from 1 to 4 for Db2
Changed tpcc:db2_count_ware from 1 to 4 for Db2
Changed tpcc:db2_dbase from tpcc to test1 for Db2
Changed tpcc:db2_user from db2inst1 to test1 for Db2
Changed tpcc:db2_pass from ibmdb2 to test1 for Db2
Changed tpcc:db2_def_tab from USERSPACE1 to DATA01 for Db2
Dictionary Settings for Db2
connection {
 db2_def_user  = db2inst1
 db2_def_pass  = ibmdb2
 db2_def_dbase = db2
}
tpcc       {
 db2_count_ware       = 4
 db2_num_vu           = 4
 db2_user             = test1
 db2_pass             = test1
 db2_dbase            = test1
 db2_def_tab          = DATA01
 db2_tab_list         = C "" D "" H "" I "" W "" S "" NO "" OR "" OL ""
 db2_partition        = false
 db2_total_iterations = 10000000
 db2_raiseerror       = false
 db2_keyandthink      = false
 db2_driver           = test
 db2_rampup           = 2
 db2_duration         = 5
 db2_monreport        = 0
 db2_allwarehouse     = false
 db2_timeprofile      = false
 db2_async_scale      = false
 db2_async_client     = 10
 db2_async_verbose    = false
 db2_async_delay      = 1000
 db2_connect_pool     = false
}
Script cleared
Building 4 Warehouses with 5 Virtual Users, 4 active + 1 Monitor VU(dict value db2_num_vu is set to 4)
Ready to create a 4 Warehouse Db2 TPROC-C schema
under user TEST1 in existing database TEST1?
Enter yes or no: replied yes
Vuser 1 created - WAIT IDLE
Vuser 2 created - WAIT IDLE
Vuser 3 created - WAIT IDLE
Vuser 4 created - WAIT IDLE
Vuser 5 created - WAIT IDLE
Vuser 1:RUNNING
Vuser 1:Monitor Thread
Vuser 1:Connecting to database test1
Vuser 2:RUNNING
Vuser 2:Worker Thread
Vuser 2:Waiting for Monitor Thread...
Vuser 3:RUNNING
Vuser 3:Worker Thread
Vuser 1:Connection established
Vuser 3:Waiting for Monitor Thread...
Vuser 1:CREATING TPCC TABLES
Vuser 4:RUNNING
Vuser 4:Worker Thread
Vuser 4:Waiting for Monitor Thread...
Vuser 5:RUNNING
Vuser 5:Worker Thread
Vuser 5:Waiting for Monitor Thread...
Error from thread tid0x7fc3d2d02700
thread "tid0x7fc3d4f65740" does not exist
    while executing
"thread::send -async tid0x7fc3d4f65740 {::myerrorproc tid0x7fc3d2d02700 db2sql1.0}"
    ("eval" body line 1)
    invoked from within
"eval [subst {thread::send -async $MASTER {::myerrorproc [list $ID $result]}}]"
    (procedure "runVuser" line 5)
    invoked from within
"runVuser tid0x7fc3d4f65740 tid0x7fc3d2d02700 1 500 {#!/usr/local/bin/tclsh8.6
#LOAD LIBRARIES AND MODULES
set library db2tcl
if [catch {package requir..."

If I'm executing the hammerdbcli in interactive mode and executing the commands manually everything works as expected.

Do you have any ideas what could be the reason for the different behaviors between autopilot and interactive mode?

Thanks a lot :)

[sm-shaw]

Hi,
The wait to complete command is now built in as "waittocomplete" so you don't have to code your routine to do this, there are some examples in this blog post here https://www.hammerdb.com/blog/uncategorized/hammerdb-cli-101/ - otherwise overall the script you are running looks OK. So it looks like the main thread "fell off" the bottom of the script and exited (after the first 5 seconds) which is why the thread doesn't exist message was reported. So try using the built-in waittocomplete first - this keeps the main thread busy while the Virtual User threads are running.

[ma44in]

The "waittocomplete" command did the trick. Many thanks for your help! 👍