[Tsung] Bug when using a relative path for a custom log file

[Diego Louzán]

Hello, I don't really know if this is a bug or it is well known (but not 
documented).

I've been trying the last few hours to configure a very simple scenario 
in which I wanted to perform a clustered stress test from 2 machines in 
my network against another test box.

I got the usual timeout errors of Tsung not being able to start the 
client processes on the other nodes from the controller, so at first I 
thought that the error was about DNS or SSH, but all of that worked fine 
  manually.

My configuration file (tsung.xml) was:

[...]
     <clients>
         <client host="gould" cpu="2">
             <ip value="10.121.55.133"></ip>
         </client>
         <client host="joshua">
             <ip value="10.121.55.34"></ip>
         </client>
     </clients>
[...]

gould is localhost and joshua is another machine from my network in 
which tsung is correctly configured too.

I launched tsung with the following command:

# tsung -f tsung.xml -l tsung.log start

and got the following error:

[...]
=INFO REPORT==== 11-Feb-2008::12:35:09 ===
     ts_config_server:(6:<0.44.0>) starting newbeam on host joshua from 
gould with Args " -rsh ssh  -detached -setcookie  tsung -shared -boot 
/usr/lib/erlang/lib/tsung-1.2.1/priv/tsung -boot_var TSUNGPATH 
/usr/lib/erlang -pa /usr/lib/erlang/lib/tsung-1.2.1/ebin 
-pa/usr/lib/erlang/lib/tsung_controller-1.2.1/ebin -tsung debug_level 6 
-tsung dump none -tsung log_file ts_encoded._4720080211_4511_5835"

=INFO REPORT==== 11-Feb-2008::12:35:41 ===
     ts_config_server:(0:<0.44.0>) Can't start newbeam on host joshua 
(reason: timeout) ! Aborting!
[...]

If this same configuration is launched without a custom log file 
(without "-l tsung.log"), everything works fine. Seems that the last 
parameter is an encoded path (_47 = /?) to the log file used, but when a 
relative path is passed to "-l", tsung does not generate a valid path in 
that parameter.

The following command works fine using custom log files:

# tsung -f tsung.xml -l $PWD/tsung.log start

I don't know if this is a problem with the shell script or tsung itself, 
but it should be solved (or at least documented on the man pages). It's 
quite hard to trace cause the error given by erlang (a timeout) points 
to some kind of network problem.

Here's my environment for reference:

Ubuntu Linux Gutsy Gibbon
Tsung 1.2.1
Erlang r11b

Regards and thanks in advance.
Diego.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: diego_louzan.vcf
Type: text/x-vcard
Size: 506 bytes
Desc: not available
Url : http://lists.process-one.net/pipermail/tsung-users/attachments/20080211/be368701/diego_louzan.bin