6 Replies Latest reply on Oct 23, 2017 10:41 PM by Sailaja Chintala

    TabJolt load test error

    Sailaja Chintala

      Hi,

       

      I have configured TabJolt and while running the load test, getting some errors as shown below:

       

      Our Tableau Server is configured on a different machine and this TabJolt is configured on a different server. It looks like it is not able to connect to the Tableau server as it is located on a different machine. But when i installed this TabJolt locally on my laptop it did work for me though the Tableau server is not existing on my laptop.

       

      D:\Tabjolt>go --t=testplans\InteractVizLoadTest.jmx --d=30 --c=1

      [2017-07-07 14:06:24,399] Perf harness is started with parameters: --rootPath=D:

      \Tabjolt --t=testplans\InteractVizLoadTest.jmx --d=30 --c=1

      [2017-07-07 14:06:24,540] Loading PerfTestConfig yaml file D:\Tabjolt\config\Per

      1. fTestConfig.yaml

      [2017-07-07 14:06:24,634] Loading ServerTestConfig yaml file D:\Tabjolt\config\S

      1. erverTestConfig.yaml

      -------------start collecting JMX counters--------------

      Output File:D:\Tabjolt/results/2017-07-07_14-06-24/jmxcounter.tsv

      -------------start collecting Zabbix counters--------------

      Output File:D:\Tabjolt/results/2017-07-07_14-06-24/zabbixcounter.tsv

      INFO  [2017-07-07 14:06:55,058][main] (PerfRunHelper.java:160) - Waiting for p

      rocesses "Windows Perf Counter Data Retriever" to start. 30 seconds have elapsed

      .

      Error   Unable to get instances for category Memory of host sedcatab0020. Skip c

      ollecting perf counters for the category. Exception Message: The network path wa

      s not found

      INFO  [2017-07-07 14:07:25,246][main] (PerfRunHelper.java:160) - Waiting for p

      rocesses "Windows Perf Counter Data Retriever" to start. 60 seconds have elapsed

      .

      Error   Unable to get instances for category Processor of host sedcatab0020. Ski

      p collecting perf counters for the category. Exception Message: The network path

      was not found

      INFO  [2017-07-07 14:07:55,418][main] (PerfRunHelper.java:160) - Waiting for p

      rocesses "Windows Perf Counter Data Retriever" to start. 90 seconds have elapsed

      .

      Error   Unable to get instances for category LogicalDisk of host sedcatab0020. S

      kip collecting perf counters for the category. Exception Message: The network pa

      th was not found

      INFO  [2017-07-07 14:08:25,715][main] (PerfRunHelper.java:160) - Waiting for p

      rocesses "Windows Perf Counter Data Retriever" to start. 120 seconds have elapse

      1. d.

      Error   Unable to get instances for category Network Interface of host sedcatab0

      1. Skip collecting perf counters for the category. Exception Message: The netw

      ork path was not found

      INFO  [2017-07-07 14:08:55,871][main] (PerfRunHelper.java:160) - Waiting for p

      rocesses "Windows Perf Counter Data Retriever" to start. 150 seconds have elapse

      1. d.

      Error   Unable to get instances for category Process of host sedcatab0020. Skip

      collecting perf counters for the category. Exception Message: The network path w

      as not found

      -------------start windows performance counters collection-------------

      Output File:d:\tabjolt/results/2017-07-07_14-06-24/wincounter.tsv

      INFO  [2017-07-07 14:09:14,981][main] (PerfRunHelper.java:347) - -------------

      start Jmeter load test run-------------

      INFO  [2017-07-07 14:09:14,981][main] (PerfRunHelper.java:348) - Output file:

      D:\Tabjolt/results/2017-07-07_14-06-24/result-sedcatab0050-0.jtl

      INFO  [2017-07-07 14:09:14,981][main] (PerfRunHelper.java:349) - Command: [D:\

      Tabjolt/bin/jmeter.bat, , , , , , -n, -t=D:\Tabjolt\testplans\InteractVizLoadTes

      1. t.jmx, -j=D:\Tabjolt/logs/jmeter_2017-07-07_14-06-24.log, -JthreadCount=1, -Jdur

      ation=30, -JloginWeight=1.0, -JconfigFolderPath=D:\Tabjolt/config/, -Jlogpath=D:

      \Tabjolt/results/2017-07-07_14-06-24/result-sedcatab0050-0.jtl, , ]

      ERROR [2017-07-07 14:09:15,103][main] (Main.java:286)   - Failed to process perf

      counters and run result.

      • org.postgresql.util.PSQLException: ERROR: relation "test_runs" does not exist

        Position: 13

              at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryEx

      1. ecutorImpl.java:2284)

              at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutor

      1. Impl.java:2003)

              at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.ja

      va:200)

              at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:424)

              at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:321

      )

              at org.postgresql.jdbc.PgStatement.executeUpdate(PgStatement.java:297)

              at org.postgresql.jdbc.PgStatement.executeUpdate(PgStatement.java:1347)

              at com.tableausoftware.test.tools.ResultProcessor.PostgresDBHelper.execu

      teScalar(PostgresDBHelper.java:314)

              at com.tableausoftware.test.tools.ResultProcessor.PostgresDBHelper.inser

      t(PostgresDBHelper.java:309)

              at com.tableausoftware.test.tools.ResultProcessor.PostgresDBHelper.inser

      tRun(PostgresDBHelper.java:128)

              at com.tableausoftware.test.tools.ResultProcessor.ResultProcessor.startP

      rocessing(ResultProcessor.java:114)

              at com.tableausoftware.test.tools.perfRunHarness.Main.startPerfResultsSa

      ver(Main.java:281)

              at com.tableausoftware.test.tools.perfRunHarness.Main.runOneTest(Main.ja

      va:238)

              at com.tableausoftware.test.tools.perfRunHarness.Main.main(Main.java:140

      )

      INFO  [2017-07-07 14:09:15,118][Thread-1] (PerfRunMonitor.java:37)   - Starting

      Perfrun monitor thread

      Created the tree successfully using D:\Tabjolt\testplans\InteractVizLoadTest.jmx

       

      Starting the test @ Fri Jul 07 14:09:15 CEST 2017 (1499429355634)

      Waiting for possible shutdown message on port 4445

      #0      Threads: 1/1    Samples: 1      Latency: 0      Resp.Time: 21813

      Errors: 1

      Tidying up ...    @ Fri Jul 07 14:10:00 CEST 2017 (1499429400275)

      ... end of run

      INFO  [2017-07-07 14:10:15,119][main] (PerfRunHelper.java:192) - Jmeter proces

      s has exited. Waiting for the other processes to exit.

      INFO  [2017-07-07 14:10:15,119][main] (PerfRunHelper.java:211) - All processes

      have exited.

      INFO  [2017-07-07 14:10:15,119][main] (PerfRunMonitor.java:57) - Perfrun is co

      mpleted - ending monitor thread

      Exception in thread "main" java.lang.NullPointerException

              at com.tableausoftware.test.tools.ResultProcessor.ResultProcessor.signal

      RunCompleted(ResultProcessor.java:177)

              at com.tableausoftware.test.tools.perfRunHarness.Main.runOneTest(Main.ja

      va:254)

              at com.tableausoftware.test.tools.perfRunHarness.Main.main(Main.java:140

      )

       

      Please help me solve this issue at the earliest.

       

       

       

      Thanks,

      Sailaja

        • 1. Re: TabJolt load test error
          Jeff Strauss

          Hi Sailaja.  Many of the errors refer to "the network path was not found".  Does the location of tabjolt and tableau-server reside within the same network?  If not, this could be a root cause of your issue.  To test out, you should be able to open a command window and do a "ping sedcatab0020" which I am assuming is one of your hosts.  Another thought is that if your tabjolt install is in a different domain that your Tableau Server, then you may need to add the FQDN domain to the host such as sedcatab0020.xxxxxxxx.xxxxxxxxx

           

          Error   Unable to get instances for category Processor of host sedcatab0020. Ski

          p collecting perf counters for the category. Exception Message: The network path

          was not found

          • 2. Re: TabJolt load test error
            Sailaja Chintala

            Thanks Jeff for your reply. I have tried pinging my Tableau Server, sedcatab0020 and is resulted in a timed out session. All the servers are located in the same domain.

             

            • 3. Re: TabJolt load test error
              Sailaja Chintala

              Hi Jeff,

               

              Another quick question, i have tried installing TabJolt on my local machine which is in a different domain (APAC) to that of my Tableau server (EMEA) and is working fine without any issues. I have tried pinging my Tableau server from my laptop and it gives the same error as timed out. So im not sure if this issue is really with the network. Could you please suggest.

               

               

              Thanks,

              Sailaja

              • 4. Re: TabJolt load test error
                Jeff Strauss

                hmmm, I'm not sure what is going on then.  Generally speaking, the network path not found issue needs to be resolved first.  One cause of this could be not being able to ping, but then how it works from your laptop is not currently clear.  Are you sometimes running wireless, and sometimes connected?

                • 5. Re: TabJolt load test error
                  Sailaja Chintala

                  Hi Jeff,

                   

                  We have opened the firewall with the port 48123 and i'm able to run the load tests. But to view the results in the workbook provided by Tabjolt, i'm unable to connect to the IP address.

                   

                  We have some issues while configuring TabJolt on our Monitoring server. To explain this, please find the servers list and its usage.

                   

                  Tableau Application servers:

                  Sedcatab0020 – Tableau DEV server

                  Sedcatab0010 – Tableau INT server

                  Sedcatab0000 – Tableau PROD server

                   

                  Monitoring Servers:

                  Sedcatab0050 – for Tableau DEV server – Monitoring tool is running (code developed in Python to get the heartbeat of the servers) which has Postgres as a DB. Tabjolt is also installed with a different port number, 48123.

                  Sedcatab0040 – for Tableau INT server

                  Sedcatab0030 – for Tableau PROD server

                   

                  Proxy servers:

                  Sedcitab0000 – Proxy (IIS) for Tableau DEV server

                  Sedcitab0010 – Proxy (IIS) for Tableau INT server

                  Sedcitab0020 – Proxy (IIS) for Tableau PROD server

                   

                  When we ran load tests on DEV Monitoring server, we had couple of error messages and found that the issue could be due to a network. So we had opened up a firewall for this port, 48123 and now able to run the load tests without any issues.

                   

                  However, to see the load tests results through the workbook provided as part of TabJolt, DEV monitoring server has no Tableau Desktop installed. I’m trying to save the workbook in our file share and open the same on our DEV Tableau server through Tableau desktop and unable to connect to the Postgres by providing the host IP address of DEV Monitoring server.

                   

                   

                  I have tried to install Tableau Desktop on the monitoring server and it gives me the below error while installing.

                   

                   

                  Could you please suggest us on how to view our load test results with the above issues.

                  • 6. Re: TabJolt load test error
                    Sailaja Chintala

                    Hi Jeff,

                     

                    After opening the firewall on the port that TabJolt postgres is using, we were able to run the load tests. However, all the load tests are resulting in a 100% error rate and when looked into the error messages captured in the TabJolt workbook, it shows 'timed out'.

                     

                    D:\Tabjolt>go --t=testplans\InteractVizLoadTest.jmx --d=120 --c=5

                    [2017-10-18 11:43:20,458] Perf harness is started with parameters: --rootPath=D:

                    \Tabjolt --t=testplans\InteractVizLoadTest.jmx --d=120 --c=5

                    [2017-10-18 11:43:20,614] Loading PerfTestConfig yaml file D:\Tabjolt\config\Per

                    1. fTestConfig.yaml

                    [2017-10-18 11:43:20,708] Loading ServerTestConfig yaml file D:\Tabjolt\config\S

                    1. erverTestConfig.yaml

                    -------------start collecting JMX counters--------------

                    Output File:D:\Tabjolt/results/2017-10-18_11-43-20/jmxcounter.tsv

                    -------------start collecting Zabbix counters--------------

                    Output File:D:\Tabjolt/results/2017-10-18_11-43-20/zabbixcounter.tsv

                    INFO  [2017-10-18 11:43:51,118][main] (PerfRunHelper.java:160) - Waiting for p

                    rocesses "Windows Perf Counter Data Retriever" to start. 30 seconds have elapsed

                    .

                    Error   Unable to get instances for category Memory of host sedcatab0020. Skip c

                    ollecting perf counters for the category. Exception Message: The network path wa

                    s not found

                    INFO  [2017-10-18 11:44:21,337][main] (PerfRunHelper.java:160) - Waiting for p

                    rocesses "Windows Perf Counter Data Retriever" to start. 60 seconds have elapsed

                    .

                    Error   Unable to get instances for category Processor of host sedcatab0020. Ski

                    p collecting perf counters for the category. Exception Message: The network path

                    was not found

                    INFO  [2017-10-18 11:44:51,524][main] (PerfRunHelper.java:160) - Waiting for p

                    rocesses "Windows Perf Counter Data Retriever" to start. 90 seconds have elapsed

                    .

                    Error   Unable to get instances for category LogicalDisk of host sedcatab0020. S

                    kip collecting perf counters for the category. Exception Message: The network pa

                    th was not found

                    INFO  [2017-10-18 11:45:21,727][main] (PerfRunHelper.java:160) - Waiting for p

                    rocesses "Windows Perf Counter Data Retriever" to start. 120 seconds have elapse

                    1. d.

                    Error   Unable to get instances for category Network Interface of host sedcatab0

                    1. Skip collecting perf counters for the category. Exception Message: The netw

                    ork path was not found

                    INFO  [2017-10-18 11:45:51,915][main] (PerfRunHelper.java:160) - Waiting for p

                    rocesses "Windows Perf Counter Data Retriever" to start. 150 seconds have elapse

                    1. d.

                    Error   Unable to get instances for category Process of host sedcatab0020. Skip

                    collecting perf counters for the category. Exception Message: The network path w

                    as not found

                    -------------start windows performance counters collection-------------

                    Output File:d:\tabjolt/results/2017-10-18_11-43-20/wincounter.tsv

                    INFO  [2017-10-18 11:46:10,024][main] (PerfRunHelper.java:347) - -------------

                    start Jmeter load test run-------------

                    INFO  [2017-10-18 11:46:10,024][main] (PerfRunHelper.java:348) - Output file:

                    D:\Tabjolt/results/2017-10-18_11-43-20/result-sedcatab0050-0.jtl

                    INFO  [2017-10-18 11:46:10,024][main] (PerfRunHelper.java:349) - Command: [D:\

                    Tabjolt/bin/jmeter.bat, , , , , , -n, -t=D:\Tabjolt\testplans\InteractVizLoadTes

                    1. t.jmx, -j=D:\Tabjolt/logs/jmeter_2017-10-18_11-43-20.log, -JthreadCount=5, -Jdur

                    ation=120, -JloginWeight=1.0, -JconfigFolderPath=D:\Tabjolt/config/, -Jlogpath=D

                    :\Tabjolt/results/2017-10-18_11-43-20/result-sedcatab0050-0.jtl, , ]

                    INFO  [2017-10-18 11:46:10,164][main] (ResultProcessor.java:129) - -----------

                    --start processing perf counters and run result-------------

                    INFO  [2017-10-18 11:46:10,164][main] (ResultProcessor.java:130) - Perf run re

                    sult is saving to result repository. Please use this RUN ID 13 to view your resu

                    lt in Tableau

                    INFO  [2017-10-18 11:46:10,196][Thread-7] (PerfRunMonitor.java:37)   - Starting

                    Perfrun monitor thread

                    Created the tree successfully using D:\Tabjolt\testplans\InteractVizLoadTest.jmx

                     

                    Starting the test @ Wed Oct 18 11:46:10 CEST 2017 (1508319970664)

                    Waiting for possible shutdown message on port 4445

                    #0      Threads: 5/5    Samples: 1      Latency: 0      Resp.Time: 21763

                    Errors: 1

                    #21     Threads: 5/5    Samples: 4      Latency: 0      Resp.Time: 21785

                    Errors: 4

                    #42     Threads: 5/5    Samples: 5      Latency: 0      Resp.Time: 21309

                    Errors: 5

                    #63     Threads: 5/5    Samples: 5      Latency: 0      Resp.Time: 21253

                    Errors: 5

                    #85     Threads: 5/5    Samples: 5      Latency: 0      Resp.Time: 21244

                    Errors: 5

                    #106    Threads: 5/5    Samples: 5      Latency: 0      Resp.Time: 21244

                    Errors: 5

                    Tidying up ...    @ Wed Oct 18 11:48:20 CEST 2017 (1508320100352)

                    ... end of run

                    INFO  [2017-10-18 11:48:30,196][main] (PerfRunHelper.java:192) - Jmeter proces

                    s has exited. Waiting for the other processes to exit.

                    INFO  [2017-10-18 11:48:30,196][main] (PerfRunHelper.java:211) - All processes

                    have exited.

                    INFO  [2017-10-18 11:48:30,196][main] (PerfRunMonitor.java:57) - Perfrun is co

                    mpleted - ending monitor thread

                    INFO  [2017-10-18 11:48:30,883][Thread-1] (JmeterResultDBSender.java:81)   - Fin

                    ish processeing all Jmeter perf result samples.

                    INFO  [2017-10-18 11:48:31,399][Thread-3] (PerfCounterDBSender.java:72)   - Fini

                    shed processing all perf counter records

                    INFO  [2017-10-18 11:48:31,415][main] (ResultProcessor.java:186) - -----------

                    ------------------------------------------

                    INFO  [2017-10-18 11:48:31,415][main] (ResultProcessor.java:187) - Perf run re

                    sult have been stored. Please use this RUN ID 13 to view your result in Tableau