You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jmeter.apache.org by Michael McDonnell <bz...@gmail.com> on 2008/05/11 01:05:25 UTC
Jmeter: Distributed Testing Issues
I'm utilizing 4 machines for Jmeter test, one master 3 slaves.
The Master Machine is Windows XP SP2
The Slaves are Ubuntu 8.04
(I don't believe this SHOULD matter, but bear with me)
The tests are not working on the remote computers only, and I'm not entirely
sure why...
1) In order to be assured that port 1099 was open on all the machines, I
scanned them all using NMap.
2) To double check they were all on the same subnet, I put them all on a
switch with the master. (Their addresses are all 10.237.0.x)
3) To make sure they were all on the same version of jmeter and that the
same test and necessary data files were all accessible, I piled my csv and
jmx files into the bin folder and ftp'ed them so they were all synchronous.
(eventually, I'll just utilize subversion to sync them up, but for now...)
4) To make sure that the jmeter-server bin wasn't failing, I was checking
the logs using a tail (tail -f jmeter-server.log in the linux world) No
exceptions were found.
5) I was also watching the jmeter log very closely on the master computer.
I keep getting the same error:
jmeter.samplers.RemoteListenerWrapper: testStarted(host)
java.rmi.ConnectException: Connection refused to host: 127.0.1.1;
In my jmeter.log file for each remote computer I try to connect to.
5a) To double check that I wasn't screwing things up by pointing my
jmeter.properties file at the wrong place, I changed the local slave (
127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on
the local machine.
Any help anyone could offer would be fantastically appreciated!
Thanks!
Michael
Re: Jmeter: Distributed Testing Issues
Posted by Michael McDonnell <bz...@gmail.com>.
The change of setting the eth0 IP to point to the HOSTNAME (and not the loop
back) worked perfectly! Thanks for all your help!
On Sat, May 10, 2008 at 6:44 PM, sebb <se...@gmail.com> wrote:
> On 11/05/2008, Michael McDonnell <bz...@gmail.com> wrote:
> > So I should have an entry in my /etc/hosts files that says <MyComputer's
> > Host Name> <MyComputersIP> ?? instead of <HOSTNAME> 127.0.0.1 ?
> >
>
> yes
>
> > (and to play it safe I'll comment out anything that points to 127.0.0.1
> )
>
> no, you should probably keep at least:
>
> localhost 127.0.0.1
>
> There may be some other loopback entries that are required.
>
> > Unfortunately, this will have to wait til monday afternoon. Thanks for
> the
> > super fast response though!
> >
> > Michael
> >
> >
> > On Sat, May 10, 2008 at 6:26 PM, sebb <se...@gmail.com> wrote:
> >
> > > On 11/05/2008, Michael McDonnell <bz...@gmail.com> wrote:
> > > > I'm utilizing 4 machines for Jmeter test, one master 3 slaves.
> > > > The Master Machine is Windows XP SP2
> > > > The Slaves are Ubuntu 8.04
> > > > (I don't believe this SHOULD matter, but bear with me)
> > > > The tests are not working on the remote computers only, and I'm
> not
> > > entirely
> > > > sure why...
> > > > 1) In order to be assured that port 1099 was open on all the
> machines, I
> > > > scanned them all using NMap.
> > > > 2) To double check they were all on the same subnet, I put them
> all on a
> > > > switch with the master. (Their addresses are all 10.237.0.x)
> > > > 3) To make sure they were all on the same version of jmeter and
> that the
> > > > same test and necessary data files were all accessible, I piled my
> csv
> > > and
> > > > jmx files into the bin folder and ftp'ed them so they were all
> > > synchronous.
> > > > (eventually, I'll just utilize subversion to sync them up, but for
> > > now...)
> > > > 4) To make sure that the jmeter-server bin wasn't failing, I was
> > > checking
> > > > the logs using a tail (tail -f jmeter-server.log in the linux
> world) No
> > > > exceptions were found.
> > > > 5) I was also watching the jmeter log very closely on the master
> > > computer.
> > > > I keep getting the same error:
> > > > jmeter.samplers.RemoteListenerWrapper: testStarted(host)
> > > > java.rmi.ConnectException: Connection refused to host: 127.0.1.1;
> > > > In my jmeter.log file for each remote computer I try to connect
> to.
> > >
> > > This usually means that the host database is not set up correctly.
> > > Check that the Ubuntu systems know their own IP addresses, and that
> > > they are not set to the loopback address.
> > >
> > > > 5a) To double check that I wasn't screwing things up by pointing
> my
> > > > jmeter.properties file at the wrong place, I changed the local
> slave (
> > > > 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked
> fine
> > > on
> > > > the local machine.
> > > >
> > > > Any help anyone could offer would be fantastically appreciated!
> > > >
> > > > Thanks!
> > > >
> > > >
> > > > Michael
> > > >
> > >
> >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: Jmeter: Distributed Testing Issues
Posted by sebb <se...@gmail.com>.
On 11/05/2008, Michael McDonnell <bz...@gmail.com> wrote:
> So I should have an entry in my /etc/hosts files that says <MyComputer's
> Host Name> <MyComputersIP> ?? instead of <HOSTNAME> 127.0.0.1 ?
>
yes
> (and to play it safe I'll comment out anything that points to 127.0.0.1)
no, you should probably keep at least:
localhost 127.0.0.1
There may be some other loopback entries that are required.
> Unfortunately, this will have to wait til monday afternoon. Thanks for the
> super fast response though!
>
> Michael
>
>
> On Sat, May 10, 2008 at 6:26 PM, sebb <se...@gmail.com> wrote:
>
> > On 11/05/2008, Michael McDonnell <bz...@gmail.com> wrote:
> > > I'm utilizing 4 machines for Jmeter test, one master 3 slaves.
> > > The Master Machine is Windows XP SP2
> > > The Slaves are Ubuntu 8.04
> > > (I don't believe this SHOULD matter, but bear with me)
> > > The tests are not working on the remote computers only, and I'm not
> > entirely
> > > sure why...
> > > 1) In order to be assured that port 1099 was open on all the machines, I
> > > scanned them all using NMap.
> > > 2) To double check they were all on the same subnet, I put them all on a
> > > switch with the master. (Their addresses are all 10.237.0.x)
> > > 3) To make sure they were all on the same version of jmeter and that the
> > > same test and necessary data files were all accessible, I piled my csv
> > and
> > > jmx files into the bin folder and ftp'ed them so they were all
> > synchronous.
> > > (eventually, I'll just utilize subversion to sync them up, but for
> > now...)
> > > 4) To make sure that the jmeter-server bin wasn't failing, I was
> > checking
> > > the logs using a tail (tail -f jmeter-server.log in the linux world) No
> > > exceptions were found.
> > > 5) I was also watching the jmeter log very closely on the master
> > computer.
> > > I keep getting the same error:
> > > jmeter.samplers.RemoteListenerWrapper: testStarted(host)
> > > java.rmi.ConnectException: Connection refused to host: 127.0.1.1;
> > > In my jmeter.log file for each remote computer I try to connect to.
> >
> > This usually means that the host database is not set up correctly.
> > Check that the Ubuntu systems know their own IP addresses, and that
> > they are not set to the loopback address.
> >
> > > 5a) To double check that I wasn't screwing things up by pointing my
> > > jmeter.properties file at the wrong place, I changed the local slave (
> > > 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine
> > on
> > > the local machine.
> > >
> > > Any help anyone could offer would be fantastically appreciated!
> > >
> > > Thanks!
> > >
> > >
> > > Michael
> > >
> >
>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
> >
> >
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
Re: Jmeter: Distributed Testing Issues
Posted by Michael McDonnell <bz...@gmail.com>.
So I should have an entry in my /etc/hosts files that says <MyComputer's
Host Name> <MyComputersIP> ?? instead of <HOSTNAME> 127.0.0.1 ?
(and to play it safe I'll comment out anything that points to 127.0.0.1)
Unfortunately, this will have to wait til monday afternoon. Thanks for the
super fast response though!
Michael
On Sat, May 10, 2008 at 6:26 PM, sebb <se...@gmail.com> wrote:
> On 11/05/2008, Michael McDonnell <bz...@gmail.com> wrote:
> > I'm utilizing 4 machines for Jmeter test, one master 3 slaves.
> > The Master Machine is Windows XP SP2
> > The Slaves are Ubuntu 8.04
> > (I don't believe this SHOULD matter, but bear with me)
> > The tests are not working on the remote computers only, and I'm not
> entirely
> > sure why...
> > 1) In order to be assured that port 1099 was open on all the machines, I
> > scanned them all using NMap.
> > 2) To double check they were all on the same subnet, I put them all on a
> > switch with the master. (Their addresses are all 10.237.0.x)
> > 3) To make sure they were all on the same version of jmeter and that the
> > same test and necessary data files were all accessible, I piled my csv
> and
> > jmx files into the bin folder and ftp'ed them so they were all
> synchronous.
> > (eventually, I'll just utilize subversion to sync them up, but for
> now...)
> > 4) To make sure that the jmeter-server bin wasn't failing, I was
> checking
> > the logs using a tail (tail -f jmeter-server.log in the linux world) No
> > exceptions were found.
> > 5) I was also watching the jmeter log very closely on the master
> computer.
> > I keep getting the same error:
> > jmeter.samplers.RemoteListenerWrapper: testStarted(host)
> > java.rmi.ConnectException: Connection refused to host: 127.0.1.1;
> > In my jmeter.log file for each remote computer I try to connect to.
>
> This usually means that the host database is not set up correctly.
> Check that the Ubuntu systems know their own IP addresses, and that
> they are not set to the loopback address.
>
> > 5a) To double check that I wasn't screwing things up by pointing my
> > jmeter.properties file at the wrong place, I changed the local slave (
> > 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine
> on
> > the local machine.
> >
> > Any help anyone could offer would be fantastically appreciated!
> >
> > Thanks!
> >
> >
> > Michael
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jmeter-user-help@jakarta.apache.org
>
>
Re: Jmeter: Distributed Testing Issues
Posted by sebb <se...@gmail.com>.
On 11/05/2008, Michael McDonnell <bz...@gmail.com> wrote:
> I'm utilizing 4 machines for Jmeter test, one master 3 slaves.
> The Master Machine is Windows XP SP2
> The Slaves are Ubuntu 8.04
> (I don't believe this SHOULD matter, but bear with me)
> The tests are not working on the remote computers only, and I'm not entirely
> sure why...
> 1) In order to be assured that port 1099 was open on all the machines, I
> scanned them all using NMap.
> 2) To double check they were all on the same subnet, I put them all on a
> switch with the master. (Their addresses are all 10.237.0.x)
> 3) To make sure they were all on the same version of jmeter and that the
> same test and necessary data files were all accessible, I piled my csv and
> jmx files into the bin folder and ftp'ed them so they were all synchronous.
> (eventually, I'll just utilize subversion to sync them up, but for now...)
> 4) To make sure that the jmeter-server bin wasn't failing, I was checking
> the logs using a tail (tail -f jmeter-server.log in the linux world) No
> exceptions were found.
> 5) I was also watching the jmeter log very closely on the master computer.
> I keep getting the same error:
> jmeter.samplers.RemoteListenerWrapper: testStarted(host)
> java.rmi.ConnectException: Connection refused to host: 127.0.1.1;
> In my jmeter.log file for each remote computer I try to connect to.
This usually means that the host database is not set up correctly.
Check that the Ubuntu systems know their own IP addresses, and that
they are not set to the loopback address.
> 5a) To double check that I wasn't screwing things up by pointing my
> jmeter.properties file at the wrong place, I changed the local slave (
> 127.0.0.1) to the non-loopback ip (10.237.0.x) and it still worked fine on
> the local machine.
>
> Any help anyone could offer would be fantastically appreciated!
>
> Thanks!
>
>
> Michael
>
---------------------------------------------------------------------
To unsubscribe, e-mail: jmeter-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jmeter-user-help@jakarta.apache.org