Red Hat Bugzilla – Bug 1022573
agent needs to be told what the server's endpoint is when rhqctl installs it
Last modified: 2014-04-23 08:31:47 EDT
The server no longer listens to 0.0.0.0 by default when you install it. You have to pick an IP address that the server will bind to (jboss.bind.address).
When you install the agent, we don't set explicitly the server address - we rely on the agent to use its default. This is one of two things - its either the IP from a DNS lookup of "rhqserver" alias, and if that is not found, it uses Java to look up the local hostname of the agent.
Usually, this is OK, unless you pick a server bind address that is different from what Java will pick up as the default hostname. If they are different, then the agent will fail to connect to the server.
Here is how I replicate this.
Build master - do not build a dev container, but just a production build (go in modules/enterprise/server/appserver and "mvn clean install").
From that build, run "rhqctl install --start" and when it prompts you, give it a jboss.bind.address of 127.0.0.1.
The agent will not be able to connect. That's because it will attempt to talk to the server on your hostname's non-loopback address (usually). On my box, it tries 192.168.x.x IP. But the server is not listening on that IP, its listening on 127.0.0.1 as I told it to.
The agent will therefore never be able to connect.
This is bad. Unless you are lucky and have a single network adapter with a single IP or Java happens to pick the IP that you pick, the agent won't be able to connect. The workaround is to set "rhqserver" alias in /etc/hosts so the agent can pick up the IP you want it to.
git commit to master: 92f4f9c
I think this should be extended to the agent port as well - in case that the user has set a different http port in the rhq-server.properties before running rhqctl install.
(In reply to Heiko W. Rupp from comment #2)
> I think this should be extended to the agent port as well - in case that the
> user has set a different http port in the rhq-server.properties before
> running rhqctl install.
The fix that I committed does this, too.
Bulk closing of 4.10 issues.
If an issue is not solved for you, please open a new BZ (or clone the existing one) with a version designator of 4.10.