Uploaded image for project: 'Tsung development'
  1. Tsung development
  2. TSUN-310

Tsung writes one log entry then gracefully stops

    Details

    • Type: Bug
    • Status: Not Yet Scheduled
    • Priority: Blocker
    • Resolution: Unresolved
    • Affects Version/s: 1.5.1
    • Fix Version/s: None
    • Component/s: Core
    • Labels:
      None
    • Environment:
      Centos Release 6.5 (Final), Erlang R14B04, Tsung 1.5.1

      Description

      After using tsung for sometime I've noticed that there comes a time when tsung will cease to work either using only localhost or distributed. This usually seems to occur when I introduce a for loop in my xml test. Uninstalling and reinstalling doesn't seem to help. Removing 1.5.1 and using 1.5.2a from github.com also doesn't resolve the problem.

      I noticed the problem when I tried to run /usr/local/lib/tsung/bin/tsung_stats.pl on a test I had had which included a for loop. The tsung.dump has had all 200's, but the tsung.log only had written 1 interval. I got the error:
      Illegal division by zero at /usr/local/lib/tsung/bin/tsung_stats.pl line 486.

      Using any test (with or without) a for loop from then on failed.

      1. theGoogleTest.xml
        0.9 kB
        Andrew Gerhold
      2. tsung_controller@trex.log
        38 kB
        Andrew Gerhold

        Expenses

          Activity

          Hide
          coolbeans7 Andrew Gerhold added a comment -

          Log file using the debug flag

          Show
          coolbeans7 Andrew Gerhold added a comment - Log file using the debug flag
          Hide
          coolbeans7 Andrew Gerhold added a comment -

          The test which was ran with the debug flag

          Show
          coolbeans7 Andrew Gerhold added a comment - The test which was ran with the debug flag
          Hide
          coolbeans7 Andrew Gerhold added a comment -

          First attempt to try and fix this shows uninstalling is not a workaround.

          1. Uninstall tsung using make uninstall
          Stdout: rm -rf /usr/lib/erlang/lib/tsung-1.5.2a /usr/bin/tsung
          2. cd /usr/lib/erlang/lib
          3. ls
          Stdout: tsung-1.5.0 tsung_controller-1.5.0 tsung_controller-1.5.2a tsung_recorder-1.5.1a
          tsung-1.5.1a tsung_controller-1.5.1a tsung_recorder-1.5.0 tsung_recorder-1.5.2a
          4. rm -rf *
          (removed everything here just to be sure I didn't miss anything)
          5. Back at ~ and I remove tsung-git
          6. git clone https://github.com/processone/tsung.git
          7. cd tsung
          8. ./configure
          9. make
          10. sudo make install
          11. cd ~
          12. tsung -f theGoogleTest.xml start
          13. same result

          Show
          coolbeans7 Andrew Gerhold added a comment - First attempt to try and fix this shows uninstalling is not a workaround. 1. Uninstall tsung using make uninstall Stdout: rm -rf /usr/lib/erlang/lib/tsung-1.5.2a /usr/bin/tsung 2. cd /usr/lib/erlang/lib 3. ls Stdout: tsung-1.5.0 tsung_controller-1.5.0 tsung_controller-1.5.2a tsung_recorder-1.5.1a tsung-1.5.1a tsung_controller-1.5.1a tsung_recorder-1.5.0 tsung_recorder-1.5.2a 4. rm -rf * (removed everything here just to be sure I didn't miss anything) 5. Back at ~ and I remove tsung-git 6. git clone https://github.com/processone/tsung.git 7. cd tsung 8. ./configure 9. make 10. sudo make install 11. cd ~ 12. tsung -f theGoogleTest.xml start 13. same result
          Hide
          tisba Sebastian Cohnen added a comment -

          Could you please also add the tsung.log file? As discussed on the mailing list, I can reproduce this error, when the tsung.log only contains one snapshot.

          So we might face two problems here:

          1) Why is there only one snapshot in your tsung.log?
          2) Why does tsung_stats fail to get the interval right if there is only one snapshot? We should maybe default here to 10sec

          Show
          tisba Sebastian Cohnen added a comment - Could you please also add the tsung.log file? As discussed on the mailing list, I can reproduce this error, when the tsung.log only contains one snapshot. So we might face two problems here: 1) Why is there only one snapshot in your tsung.log? 2) Why does tsung_stats fail to get the interval right if there is only one snapshot? We should maybe default here to 10sec

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Start Date:

                Development