[Tsung] Using tsung in "cluster"

[Pascal Cohen]

Nicolas Niclausse wrote:
> Hello,
>
> Pascal Cohen ecrivait le 19.10.2006 09:53:
>   
>> Hello
>> I don't know if the "cluster" word is the right one. Probably
>> distributed would be more suitable.
>> Anyway, when I try to start tsung on several clients, the program stops
>> quickly. When I have a look in the controller log I find the message
>> like it is starting a new beam on a remote machine but it displays a log
>> with timeout and it failed to start the beam. - I add a log at the end
>> of this post. If I try to connect with ssh on the remote machine
>> everything is OK. I have added the ssh keys to avoid asking for the
>> password.
>>
>> If I try from another machine it works. In fact it has been working
>> until a new kernel was installed. I tried to reinstall but it doesn't
>> work anymore.
>> I made tests with a rpm version but it didn't work either.
>>     
>
> ? the kernel should have no impact on ssh authentication. What OS are you
> using ?
>
>   
That is what I expected too. But in fact we use Xen virtual machines. So 
the first time I installed (and compiled) tsung, there was a specific 
Linux kernel that enables Xen virtual machines. Everything behave well 
and we changed the Linux kernel (a standard Centos 4.1) a few weeks ago 
to use a "standard" kernel. I was not able anymore to start beams on 
remote machines, I got a "timeout" message. I tried to make a clean up 
and recompile, reinstall without any success, I tried to use a rpm 
version, I had the same problem.
I would also really be surprised if that was related to a kernel version 
anyway if I restart with the kernel used for Xen, it works fine.

It is like tsung is not able to connect to other machines. I checked 
with ssh keys manually and everything is OK.
>> Currently I can start distributed tests starting the controller on the
>> first machine and delegating process to other machines.
>>     
>
> What do you mean by delegating ?
>
>   
Bad choice of word: it is as said just before starting beams on remote 
machines and I get timeout!