Re: Console Service remote worker issues

You are confusing the two ports the console uses. You've configured 8000
as the console port - this is the port for communication between
agents/workers and the console that has been part of The Grinder for a
decade now. The default value is 6372.

You really wanted to configure the console service HTTP port. As Marc
said, the normal way to do this is in the console options. You can also
set the HTTP port from the command line, I've just updated the docs with
instructions:
http://grinder.sourceforge.net/g3/console-service.html#address-command-line

- Phil

On 24/09/13 20:29, [email protected] wrote:
> Marc,
>
> Excellent. Worked like a charm. Thank you.
>
> I feel we should have this documented more clearly in the Console API
> service section on the Grinder site. Because Console options can be
> confused with passing Java options on the commandline like how I was
> doing it.
>
> Overall console API works great. As an enhancement being able to
> control individual agents will be something nice to have.
>
> Anil
>
> ------------------------------------------------------------------------
> *From: *"Marc Holden" <[email protected]>
> *To: *"grinder-use" <[email protected]>
> *Sent: *Sunday, September 22, 2013 5:18:06 AM
> *Subject: *Re: [Grinder-use] Console Service remote worker issues
>
> Hi Anil,
>
> IIRC, you should remove the grinder.consoleHost and
> grinder.consolePort properties from the console start-up.  If you need
> to change the port http listens on,
> see http://grinder.sourceforge.net/g3/console-service.html#configuration.
>  Essentially, you need to change the port in the console options and
> click 'Save as default'.  Then restart the console.  Doing this will
> generate .grinder_console (or something simliar) properties file in
> you $HOME directory that is read by the console process at startup time.
>
> Hopefully this helps.
>
> -Marc 
>
>
> On Sat, Sep 21, 2013 at 6:23 PM, <[email protected]
> <mailto:[email protected]>> wrote:
>
>     I am trying to use the console REST API service from multiple
>     remote machines. Here are the issues I face. If anyone has worked
>     this out please advice.
>
>     Steps I carried out:
>
>     Start Console on one machine
>     1. java -classpath engine/grinder/lib/grinder.jar
>     -Dgrinder.console.consoleHost=10.2.1.24
>     -Dgrinder.console.consolePort=8000 net.grinder.Console -headless
>     It starts saying - Started SelectChannelConnector@:6373
>
>     Start agent on remote machine
>
>     2. java -classpath engine/grinder/lib/grinder.jar
>     -Dgrinder.consoleHost=10.2.1.24 -Dgrinder.consolePort=8000
>     net.grinder.Grinder
>     connected to console at /10.2.1.24:8000 <http://10.2.1.24:8000>
>     2013-09-21 15:10:20,651 INFO  agent: waiting for console signal
>
>     3. Start worker on remote machine
>
>     curl -H "Content-Type: application/json" -X POST
>     http://10.2.1.24:8000/agents/start-workers -d '{"grinder.duration"
>     : "600000","grinder.processes" : "1", "grinder.threads" : "5",
>     "grinder.runs" : "0",  "grinder.script" : "testrun.py" }'
>
>     Message: curl: (56) Recv failure: Connection reset by peer
>
>     Exception on Console:
>     2013-09-21 15:10:21,167 INFO  console: Agent testmachine1 [Connected]
>     2013-09-21 15:13:45,828 ERROR console: Could not read address details
>     net.grinder.communication.CommunicationException: Could not read
>     address details
>
>     Caused by: java.io.StreamCorruptedException: invalid stream
>     header: 504F5354
>
>     This works only from the local machine with Console, Agent and
>     Worker on the same machine.
>
>     Please let me know if anyone has been able to get console, agent
>     and worker from remote machines. Need it urgently.
>
>     Thank you.
>     Anil
>

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134791&iu=/4140/ostg.clktrk

_______________________________________________
grinder-use mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/grinder-use