Re: Broken Pipe Exception - failed reporting to console

* Lei <[email protected]> [20140823 16:20]:
> I am trying to run grinder agent in Amazon EC2 instance and run console in
> my local network. All instances including console are within one VPN
> network. I am pretty positive about the network between EC2 instance and
> local machine runs grinder console.
> 
> While the agent got started, it connected to console instantly. Agent
> showed up in console correctly.
> 
> However once the agent start testing, it failed reporting to console with
> below Broken Pipe exception.
> 
> I am aware similar Exception had been reported by another user a few months
> ago. Given the network is pretty stable, and this problem happened
> consistently from my observation. This problem might not because of
> unstable internet connection.
> 
> Any advice for debugging this issue will be appreciated.

My bet is that you are trying to create processes and/or threads
too fast and overloading your agent. I suggest trying to diagnose wether
it is a maximum agent load issue or a rate issue (i.e.: wether you can
create the intended load over a longer timeframe).

qvb
--
pica

------------------------------------------------------------------------------
Slashdot TV.  
Video for Nerds.  Stuff that matters.
http://tv.slashdot.org/