Distributed Jmeter config

[bpc...@gmail.com]

When I execute a local jmeter test from Taurus it's successful, however, when I execute a distributed test such as bzt jmeter.yml -v -o execution.distributed=10.32.45.100

the following is displayed:

15:23:44 INFO: Taurus CLI Tool v1.4.3

15:23:44 INFO: Starting with configs: ['jmeter.yml\xc2\xa0-v']

15:23:44 INFO: Configuring...

15:23:44 INFO: No personal config: /root/.bzt-rc

15:23:44 ERROR: IOError: [Errno 2] No such file or directory: 'jmeter.yml\xc2\xa0-v'

15:23:44 WARNING: Please wait for graceful shutdown...

15:23:44 INFO: Post-processing...

15:23:44 INFO: Artifacts dir: None

15:23:44 WARNING: Done performing with code: 1

15:23:44 WARNING: Artifacts dir has not been set, will not copy bzt.log

The script (below) is located on both the Taurus and Jmeter servers, however, on Taurus jmeter was auto-installed and on jmeter server jmeter was manually installed to /home/bcarson/apache-jmeter-2.13/bin/jmeter .

Where on the distributed server is Taurus looking to find 'jmeter.yml\xc2\xa0-v'?   

Script

---

modules:

  jmeter:

    path: /home/bcarson/apache-jmeter-2.13/bin/jmeter

execution:

  concurrency: 50

  ramp-up: 1m

  hold-for: 1m

  scenario:

    requests:

      - http://blazedemo.com

      - http://blazedemo.com/vacation.html

[Andrey Pokhilko]

Hi,

You seems have copied and pasted something into your command line, so it put some unexpected bytes after the config file name. Please try re-typing it by hand from the scratch, it should help.

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/4b82769d-0baa-4069-8b14-438fb5cd7020%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[bpc...@gmail.com]

Andrey,

That was weird - good find, thanks!

Next issue, when I look at jmeter.log it shows

2016/04/19 08:06:56 INFO  - jmeter.engine.DistributedRunner: Configuring remote engine: 1

2016/04/19 08:06:56 ERROR - jmeter.engine.DistributedRunner: Failed to create engine at 1 java.rmi.ConnectIOException: Exception creating connection to: 1; nested exception is:

        java.net.SocketException: Invalid argument or cannot assign requested address

        at sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:631)

        at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:216)

        at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:202)

        at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:341)

        at sun.rmi.registry.RegistryImpl_Stub.lookup(Unknown Source)

        at java.rmi.Naming.lookup(Naming.java:101)

        at org.apache.jmeter.engine.ClientJMeterEngine.getEngine(ClientJMeterEngine.java:54)

        at org.apache.jmeter.engine.ClientJMeterEngine.<init>(ClientJMeterEngine.java:67)

        at org.apache.jmeter.engine.DistributedRunner.createEngine(DistributedRunner.java:237)

        at org.apache.jmeter.engine.DistributedRunner.getClientEngine(DistributedRunner.java:213)

        at org.apache.jmeter.engine.DistributedRunner.init(DistributedRunner.java:91)

        at org.apache.jmeter.JMeter.runNonGui(JMeter.java:814)

        at org.apache.jmeter.JMeter.startNonGui(JMeter.java:737)

        at org.apache.jmeter.JMeter.start(JMeter.java:395)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)

        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)Enter code here...

How do I troubleshoot this RMI connection issue? What port is it trying to use? I thought I saw 4445 in a log somewhere but if I execute netstat -alnp | grep 4445 on the Jmeter server nothing gets returned?

[bpc...@gmail.com]

I've updated jmeter.properties in my Taurus server to be:

remote_hosts=10.32.45.100

server_port=1099

I've updated jmeter.properties in my Jmeter server to be:

remote_hosts=127.0.0.1

server_port=1099

After doing this I'm testing by telneting from Taurus to Jmeter and I get connection refused so maybe I need to disable IPTABLES or something, but do the above settings seem correct for Jmeter connections?

[Andrey Pokhilko]

If you will run JMeter without Taurus, will it work in distributed mode?

Andrey Pohilko Chief Scientist P: +7 (909) 631-21-69

--
You received this message because you are subscribed to the Google Groups "codename-taurus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codename-taur...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/codename-taurus/2d18a637-0364-4bed-91b0-6564ae33b604%40googlegroups.com.

[bpc...@gmail.com]

This is definitely a firewall issue not a Taurus issue. I'm going to rebuild my open-stack instance and allow port 1099 access. Hoping this will do the trick. Thanks, Bruce.