This may be due to how the cloud provide r does proxying internally. If you are
setting up a listening socket for some reason, just bind to '*'.
That said, this slave is about to be replaced.
-Chris
On Feb 9, 2018, 12:12, at 12:12, Felix Schumacher
wrote:
Hi,
Am 09.02.2018 um 03:00 schrieb Chris Lambertus:
> I’ve been using it all day, we haven’t had any (other) reports of problems.
> Our monitoring usually notices poor performance these days, and people are
> pretty vocal about letting us know when something’s wrong when Jira’s
> involved. :-)
Hi all,
we (JMeter) have currently a problem running our nightly builds. The
tests fail, when we try to bind to the address of the hostname of the
build server. The server is bb-1604-test.apache.org and resolves to
207.244.88.135. It seems, that that address is not bound to the network