Reconfiguring Agent

[mgalante_hyperi]

We had to change the IP of our HQ server running Windows 2003. How do I reconfigure all my agent without uninstalling, rebooting and reinstalling the agent?

[john_hyperic]

run 'hq-agent.sh -setup' and be sure to specify that you want to regenerate the tokens.

[mgalante_hyperi]

It's prompts to find a program to open the file with. All my agents are running on a Windows 2003 server or Windows 2000.

[BradFelmey]

Then instead run hq-agent.exe from the directory you installed Hyperic into. It's *.exe for the Windows systems, and *.sh for the Unix ones.

[deeboh]

Hey John and Brad, thanks for the insight. re-running setup forced auto-discover to find my missing components jboss and tomcat...

http://communities.vmware.com/message/1915809#1915809

don't know how to mark your posts helpful but they were.

Deeboh

[gnovak]

I am also having the same problem although my situation is a bit different. HQ server used to be on Box A. Well, I removed it from Box A, Box A is now dead, installed it on Box B and gave it the same IP address that it had on Box A. The IP didn't change, just the machine.

However, no agents are showing up in the autodiscovery for HQ server running on it's new box. I tried stopping and restarting the agent on a windows box but that didn't seem to work. Running "hq-agent.exe -setup" on the windows box where the agent is running didn't do anything or ask me if I wanted to regenerate tokens.

HQ server is running on an Ubuntu machine. I have a mix of agents, some of are running linux, some are running Windows. None have showed up since HQ was moved.

Is there some type of command that can be run on the server to contact all agents running on machines on your network and have them repopulate the dashboard again? How can I get all of these machines to show up in hyperic again without reinstalling the agent on every machine?

[BradFelmey]

Well, the brute force approach usually works well for me, but no points for elegance. :)

On the client systems, in the directory where you installed the agent, first shut down the agent, and then completely remove the "data" directory. Restart the agent, and it will prompt you again to set up anew.

[gnovak]

Well it's a good thing I didn't have this running on every machine in production.

For now I'll remove the agent from the machines and reinstall it. However, in the event this would happen in the future when a lot more machines have agents configured on them, it would be a lot easier to maybe have the server broadcast something like "hey, agents, over here!" and they would rediscover the server. Having to uninstall and reinstall it on every machine is very time consuming.

[BradFelmey]

"I feel your pain" (TM Bill Clinton)

I moved our server after we had close to 100 systems on it. It did take a while. :-/

[BradFelmey]

You don't have to reinstall. In fact, if the agent is already running, you can just ./hq-agent.sh -setup and it'll prompt you to reenter the server name. I usually do the rm -rf on the data directory just to get a clean start.

Like I said, no points for elegance.

I don't know if the HQ shell will allow you to do this en masse or not.

[gnovak]

p.s. Thanks for your help. I'll add these instructions to my documentation!