[Tsung] timeout error with bad_return_value
Vinod Panicker
vinod.p at gmail.com
Fri Feb 23 06:00:22 CET 2007
Seems like this was caused due to a bad install of tsung on the guilty
machine. Re-installing tsung made this problem go away.
Regards,
Vinod.
On 2/8/07, Vinod Panicker <vinod.p at gmail.com> wrote:
> Hi,
>
> Here's the error log -
>
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_config_server:(5:<0.45.0>) Config server started, logdir is
> "/home/vinod/.tsung/log/20070208-08:59"
>
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_mon:(5:<0.44.0>) starting monitor, global
>
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_mon:(5:<0.46.0>) Init, log dir is
> "/home/vinod/.tsung/log/20070208-08:59"
>
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_mon:(5:<0.46.0>) starting monitor
>
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_os_mon:(5:<0.44.0>) starting os_mon
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_os_mon:(5:<0.51.0>) os_mon started
> =INFO REPORT==== 8-Feb-2007::03:59:41 ===
> ts_config:(5:<0.45.0>) Reading config file:
> /home/vinod/.tsung/tsung.xml
>
> =INFO REPORT==== 8-Feb-2007::03:59:42 ===
> ts_user_server:(5:<0.50.0>) Reset offline and online lists
>
> =INFO REPORT==== 8-Feb-2007::03:59:42 ===
> ts_config:(5:<0.45.0>) Session name for id 1 is "jabber-example1"
>
> =INFO REPORT==== 8-Feb-2007::03:59:42 ===
> ts_config:(5:<0.45.0>) Session type: persistent=true
>
> =INFO REPORT==== 8-Feb-2007::04:00:14 ===
> ts_config_server:(0:<0.45.0>) Can't start newbeam on host mimsdev
> (reason: timeout) ! Aborting!
>
> =ERROR REPORT==== 8-Feb-2007::04:00:14 ===
> ** Generic server ts_config_server terminating
> ** Last message in was {'$gen_cast',{newbeam,mimsdev,[]}}
> ** When Server state == {state,{config,
> undefined,
> 4,
> none,
> text,
> undefined,
> [{client,"mimsdev",0.500000,7000,[]},
> {client,"mimsdev",0.500000,7000,[]},
> {client,"hummer",0.500000,7000,[]},
> {client,"hummer",0.500000,7000,[]},
> {client,"mims5",1.00000,7000,[]},
> {client,"mims4",1.00000,7000,[]},
> {client,"mims3",1.00000,7000,[]},
> {client,"mims2",1.00000,7000,[]},
> {client,"mims1",1.00000,7000,[]}],
> [{server,"192.168.1.17",5222,gen_tcp}],
> [{"banshee",erlang}],
> [{arrivalphase,
> 1,
> 10000,
> undefined,
> undefined,
> 4.00000e-3,
> infinity}],
> undefined,
> false,
> [],
> undefined,
> [{session,
> 1,
> 100,
> ts_jabber,
> true,
> negociate,
> undefined}],
> 17,
> false,
> 60,
> 663,
> 662,
> undefined,
> negociate},
> "/home/vinod/.tsung/log/20070208-08:59",
> undefined,
> mims1,
> 0,
> 0,
> undefined,
> 7.00000}
> ** Reason for termination ==
> ** {bad_return_value,{stop,normal}}
>
> =INFO REPORT==== 8-Feb-2007::04:00:14 ===
> ts_mon:(0:<0.46.0>) Aborting by request !
>
>
> And yes, the erlang versions are the same - 5.5.1
>
> Regards,
> Vinod.
>
> On 2/8/07, Nicolas Niclausse <nicolas at niclux.org> wrote:
> > Vinod Panicker ecrivait le 06.02.2007 07:20:
> > > Hi,
> > >
> > > I'm running a distributed load test, and the test host is not able to
> > > connect to a particular node with the timeout error. Reason is given
> > > as bad_return_value.
> >
> > Can you show us the full error report ?
> >
> > > Although, I'm able to run a slave on the remote host and set a cookie,
> > > as is described in the faq section of the manual.
> > >
> > > The tsung host machine is ubuntu-edgy 32 bit. The remote host is
> > > ubuntu-edgy 64 bit.
> > >
> > > The tsung host is able to connect to other 64 bit ubuntu machines
> > > without any problem. I'm running a test distributed across 6+ nodes.
> > > So its weird that tsung is giving an error for one particular node.
> >
> >
> > weird indeed ...
> >
> > the same version of erlang is used on all nodes ?
> >
> >
> > --
> > Nicolas
> > _______________________________________________
> > Tsung-users mailing list
> > Tsung-users at lists.process-one.net
> > https://lists.process-one.net/mailman/listinfo/tsung-users
> >
>
More information about the Tsung-users
mailing list