Re: Unable to get monitoring working in latest ngrinder

Posted by junoyoon on
URL: http://ngrinder.373.s1.nabble.com/Unable-to-get-monitoring-working-in-latest-ngrinder-tp1462p1478.html

I think I found the root cause. nGrinder monitor only works properly when IP6 and IP4 are both supported. If IP6 is not supported in the target system. It tries to bind the default IP (IP bound to hostname)

Could you check your server has IP6 address(not including IP6 for loopback and tenneling interfaces)?

2014-04-09 22:44 GMT+09:00 Juno Yoon <[hidden email]>:

Oh. Thanks. However your case(hostname => 127.0.0.1) was what we thought that it's fixed.

Actually nGrinder JMX-Over-RMI implementation is supposed to be bound to all available IPs.

I'll follow up this issue and fix it soon.

2014-04-09 5:09 GMT+09:00 John Warner [via ngrinder] <[hidden email]>:

Hi,

Thanks for the suggestion. While setting things up to try that, I found a problem with the configuration on our box. Essentially the hostname was being pointed to 127.0.1.1 instead of its external IP address.

That was preventing the connection being established correctly and caused all of our problems. All is well now.

Thanks for all of your help and sorry to have wasted your time.

--
John Warner

---

If you reply to this email, your message will be added to the discussion below:

http://ngrinder.642.n7.nabble.com/Unable-to-get-monitoring-working-in-latest-ngrinder-tp1462p1471.html

To start a new topic under ngrinder-user-en, email [hidden email]
To unsubscribe from ngrinder-user-en, click here.
NAML