I am running jmeter-server on my slaves:
/jmeter/apache-jmeter-2.13/bin$ sudo ./jmeter-server Created remote object: UnicastServerRef [liveRef: [endpoint:[54.70.213.113:39049](local),objID:[-5ec80bb2:14db9f630f7:-7fff, -5495296853936812260]]] -----Original Message----- From: mahesh bhasme [mailto:[email protected]] Sent: Wednesday, June 03, 2015 6:03 PM To: JMeter Users List Subject: Re: Distributed test Is jmeter-server started ? check below link for connection timeout error http://www.guru99.com/jmeter-distributed-testing.html Regards, MB On Wed, Jun 3, 2015 at 8:10 PM, Erez Naim <[email protected]> wrote: > The thing is I want to control it from my windows server....to see it > on GUI... > Other AWS that function as slaves are Linux based servers... > > > > -----Original Message----- > From: Sergio Boso [mailto:[email protected]] > Sent: Wednesday, June 03, 2015 5:21 PM > To: JMeter Users List > Subject: Re: Distributed test > > Hi, > > as described here: > > http://jmeter.apache.org/usermanual/jmeter_distributed_testing_step_by > _step.pdf > > you must have all computer running on the same VLAN to execute a > distributed testing. > I think you have two options: > - move the master to AWS, on the same VPC > - setup a VPN so that all server are connected on the same network > > IMHO, the first one is much ore simple. > Regards > > Sergio > > 2015-06-03 16:00 GMT+02:00 Erez Naim <[email protected]>: > > > No firewalls are active on my slaves: > > > > deploy@ip-10-34-6-21:~$ sudo ufw status > > Status: inactive > > > > -----Original Message----- > > From: Bo Bodnar [mailto:[email protected]] > > Sent: Wednesday, June 03, 2015 4:56 PM > > To: JMeter Users List > > Subject: Re: Distributed test > > > > I've run across this situation - the quick solution was to turn off > > the firewalls on the slaves. > > > > > > > > > > On 6/3/15, 5:56 AM, "Erez Naim" <[email protected]> wrote: > > > > >I have successfully connect from my windows server to AWS using > > >telnet command with specific port , what am I missing? > > > > > > > > > > > >From: Konstantinos Dimkas [mailto:[email protected]] > > >Sent: Wednesday, June 03, 2015 11:41 AM > > >To: JMeter Users List > > >Subject: Re: Distributed test > > > > > > > > > > > >Hi Erez, > > > > > > > > > > > >Is there any firewall between the master and the slaves? > > > > > > > > > > > >On Jun 3, 2015, at 10:42 AM, Erez Naim <[email protected] > > ><mailto:[email protected]> > wrote: > > > > > > > > > > > >Hello all, > > > > > > > > > > > >I am trying to run a remote test when I am trying to run it from my > > >local computer (windows OS - client) and to run slave servers on > > >AWS (UBUNTU linux os - server), > > > > > >I have updated the jmeter.properties file with remote-hosts > > >parameter to point (on client side) to the relevant public DNS addresses. > > > > > > > > > > > >On the servers I have updated in the jmeter.properties > > >server.rmi.localport=50000 > > > > > >When I am trying to run the test from client side I am getting the > > >following error: > > > > > >Connection refused to host 54.xx.xx.xx nested exception is > > >java.net.ConnectException: Connection timed out: connect > > > > > >What can I do in order to solve it? > > > > > >Thanks for any help it is quite urgent as I have to run the tests !! > > > > > > > > > > > > > > > > > > > > >Erez Naim | QA Lead | > > > > > > > > >EL AL 2 Street | Herzliya > > >mobile (+972) 50 9 555 686 | fax (408) 689.1366 | skype erez.neura > > > > > > > > > > > > > > > <http://www.theneura.com/> website | <http://www.startupbitz.com/> > > >blog | <https://twitter.com/intent/user?screen_name=theneura> > twitter > > >| <http://goo.gl/maps/ZRkg5> map > > > > > > > > > > > >Konstantinos Dimkas > > > > > > > > > > > > > > > > > > > > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > -------------------------------------------------------------------- > > - To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Thanks, MAhesh --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
