nGrinder 3.2.1 - Agent is not connecting to controller

[balajilinks]

I downloaded and deployed nGrinder 3.2.1 with tomcat package.  I started running the 3.2.1 Agent.  

Got the following error messge in Agent.

2013-06-24 12:25:49,687 INFO  org.ngrinder.NGrinderStarter  :  - Passing mode agent
2013-06-24 12:25:49,688 INFO  org.ngrinder.NGrinderStarter  :  - nGrinder version 3.2.1
2013-06-24 12:25:49,916 INFO  org.ngrinder.NGrinderStarter  :  ***************************************************
2013-06-24 12:25:49,917 INFO  org.ngrinder.NGrinderStarter  :   Start nGrinder Agent ...
2013-06-24 12:25:49,984 INFO  org.ngrinder.NGrinderStarter  :  with console: 127.0.0.1:16001
2013-06-24 12:25:49,984 INFO  org.ngrinder.NGrinderStarter  :  JVM server mode is disabled. If you turn on ngrinder.servermode in agent.conf. It will provide the better agent performance.
2013-06-24 12:25:50,082 INFO  agent controller daemon  :  The agent controller daemon is started.
2013-06-24 12:25:51,257 ERROR agent controller  :  Error while connecting to controller /127.0.0.1:16001
2013-06-24 12:25:54,261 ERROR agent controller  :  Error while connecting to controller /127.0.0.1:16001
2013-06-24 12:25:57,264 ERROR agent controller  :  Error while connecting to controller /127.0.0.1:16001
2013-06-24 12:26:00,356 ERROR agent controller  :  Error while connecting to controller /127.0.0.1:16001
2013-06-24 12:26:03,363 ERROR agent controller  :  Error while connecting to controller /127.0.0.1:16001
2013-06-24 12:26:05,364 INFO  agent controller daemon  :  The agent controller daemon is started.


I stopped 3.2.1 controller and I started 3.2 controller. This time my agent is connected to controller.
OS :-  Win 7
Agent and controller running in same machine.

[junoyoon]

Due to fix [NGRINDER-612] - Make controller's ip configurable,
controller now use the public ip (not 127.0.0.1) to bind the listening socket..

OMG.
I missed to fix this in agent side... agent is still connecting 127.0.0.1..

Please set up the controller ip(public one) in the agent.conf file please.

[balajilinks]

Thanks Juno.. This worked.. Now the agent is connected with controller.

IP address keep changing and the machine name wont change that often. I thought, rather specifying the IP address, if I able to specify the Machine Name that reduce lots of my maintenance effort.

So, I configured agent.conf with the machine name and I started the agent.

================================================================================
2013-06-25 09:46:25,681 INFO  org.ngrinder.NGrinderStarter  :  - Passing mode agent
2013-06-25 09:46:25,682 INFO  org.ngrinder.NGrinderStarter  :  - nGrinder version 3.2.1
2013-06-25 09:46:25,820 INFO  org.ngrinder.NGrinderStarter  :  ***************************************************
2013-06-25 09:46:25,820 INFO  org.ngrinder.NGrinderStarter  :   Start nGrinder Agent ...
2013-06-25 09:46:25,823 ERROR org.ngrinder.NGrinderStarter  :  Hey!! Z0024-E8F9-BD89 does not seems like IP. Try to resolve the ip with Z0024-E8F9-BD89.
2013-06-25 09:46:25,823 INFO  org.ngrinder.NGrinderStarter  :  Console IP is resolved as 10.205.7.181.
2013-06-25 09:46:25,828 INFO  org.ngrinder.NGrinderStarter  :  with console: 10.205.7.181:16001
2013-06-25 09:46:25,899 INFO  agent controller daemon  :  The agent controller daemon is started.
2013-06-25 09:46:26,975 ERROR agent controller  :  Error while connecting to controller /10.205.7.181:16001
2013-06-25 09:46:30,634 INFO  agent controller  :  connected to agent controller server at /10.205.7.181:16001
2013-06-25 09:46:30,637 INFO  agent controller  :  waiting for agent controller server signal
 
================================================================================

nGrinder Agent resolved the machine name and connected to the controller. Very pleased with this feature.. You guys are thinking well ahead of the problem.. :)

Thanks

[AMRITHA]

2014-02-28 04:27:30,457 INFO  agent config: NGRINDER_AGENT_HOME : /home/ec2-user/.ngrinder_agent
2014-02-28 04:27:30,733 INFO  starter: ***************************************************
2014-02-28 04:27:30,744 INFO  starter:    Start nGrinder Agent ...
2014-02-28 04:27:30,744 INFO  starter: ***************************************************
2014-02-28 04:27:30,745 INFO  starter: JVM server mode is disabled.
2014-02-28 04:27:30,763 INFO  starter: connecting to controller 54.254.164.130:16001
2014-02-28 04:27:30,833 INFO  agent controller daemon: The agent controller daemon is started.
2014-02-28 04:27:31,511 INFO  agent controller: Connected to agent controller server at /54.254.164.130:16001
2014-02-28 04:27:31,511 INFO  agent controller: Waiting for agent controller server signal


but but still no response from agent controller

[junoyoon]

agent controller: Waiting for agent controller server signal

means... that the agent is already connected to controller and wait the test start message from the controller.

It's totally valid state.

[AMRITHA]

2014-06-13 09:37:37,773 INFO  agent controller daemon: The agent controller daemon is started.
2014-06-13 09:37:37,774 ERROR agent controller: Error while connecting to controller /192.168.0.236:16001
2014-06-13 09:37:39,775 ERROR agent controller: Error while connecting to controller /192.168.0.236:16001
2014-06-13 09:37:41,776 ERROR agent controller: Error while connecting to controller /192.168.0.236:16001
2014-06-13 09:37:43,777 ERROR agent controller: Error while connecting to controller /192.168.0.236:16001
2014-06-13 09:37:45,779 ERROR agent controller: Error while connecting to controller /192.168.0.236:16001
2014-06-13 09:37:47,779 INFO  agent controller daemon: The agent controller daemon is started.