(1:51:49 PM) ccrouch: mazz: so we can't give the agents a new JAVA_OPTS without going to each box right? (1:52:42 PM) mazz: right - no way to currently be able to modify the rhq-agent-env.sh/bat file (1:52:56 PM) ccrouch: is that in the bucket with agent autoupgrades? (1:53:00 PM) mazz: though that would be cool - however, we have no way of restarting the agent using rhq-agent.bat/sh anyway (1:53:16 PM) ccrouch: don't we inventory those scripts? (1:53:19 PM) mazz: no (1:53:45 PM) mazz: this is the difficult thing with the agents (1:54:05 PM) mazz: how do you restart it? the agent process wants to ask to run rhq-agent.sh but it IS already running (1:54:20 PM) mazz: so you have to kill the agent, then run the script... chicken and egg. (1:54:50 PM) ccrouch: well jbas get around this by using exit codes in the run scripts (1:55:18 PM) ccrouch: so if we exit with 10 (i think) the script will see that and try and restart (1:55:23 PM) mazz: yeah... in one of my update jiras, I mention exit scripts somewhere I think (1:56:19 PM) ccrouch: so basically the large environment use case is "i dont want to touch each ofl the boxes. period." (1:56:44 PM) ccrouch: so if we can do upgrades thats great, but we've got to be able to tweak stuff too (1:56:50 PM) ccrouch: like JAVA_OPTS (1:57:19 PM) ccrouch: or any of the other stuff we specify at startup thats not in the agent resource config
Making this critical because not being able to restart the agent remotely, or change its start up options means there is a good likelihood admins will still need to visit the boxes the agents are installed on
today we can "restart" the agent core - we just can't restart the agent process. Restarting the entire agent process is what this JIRA is all about.
One additional thing that maybe related to restarting the whole agent is to be able to remotely turn on debug logging on the agent. Right now this is done by setting the RHQ_AGENT_DEBUG=true env. var. It would be nice to be able to do this the main JON Server across a set of agents at once.
RHQ-1198 provides the ability for the agent to turn on and off comm tracing and switch log4j config. right now, only can do this from console (prompt command) but is trivial to add this to the AgentManagementMBean and expose the functionality as rhq-agent plugin operations.
RHQ-22 is implemented (rev 2224) so you can now remotely turn on/off debugging from operations tab of the agent.
RHQ-1197 lets you import the configuration for these config files so you can change their values from the UI.
svn rev 2448 and a few before introduce agent plugin operations to the RHQ Agent Java Service Wrapper service resource that lets you shutdown and restart the agent VM on windows. you can reconfigure the VM settings through the config tab. therefore, full remote control of the agent exists on windows. still have to do this for unix platforms.
svn rev 2457 added the unix script support. this should close this issue out. still need alot of testing on this.
This bug was previously known as http://jira.rhq-project.org/browse/RHQ-1108 This bug is related to RHQ-1189 This bug is related to RHQ-1197 This bug relates to RHQ-1041 This bug relates to RHQ-1194 This bug is incorporated by RHQ-1198