- Originally the JON Server and 4 JON Agents were properly configured and working under in our environment.
- To test our build, we took VM images of the 4 nodes and modified the hostnames from dev-node.host.com to test-node.host.com
- When the tester re-configured the Jon Agents using the new hostnames (using the --cleanconfig option), it appears that the old hostnames are still residing somewhere because the JON agent log files show the JON Agent trying to access the JON Server at the old "dev" hostname. Hence, we are unable to get the JON Agent to communicate with the JON Server (even though they are on the same node!).
We really want to avoid having to do a complete reinstallation of the JON Server and JON Agents each time there is a change in hostname.
Could the old name be referenced in the database somewhere?
- JBoss Operations Network 2.3 Server
- JBoss Operations Network 2.3 Agent
- Redhat Enterprise Linux 5.3
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.