Hi Karl, my question was related in specify case when the server where Apache Manifold is running dies for hardware or OS problems. In this case a would undestand the best scenario to recover the situation and create an automatic procedure.
To check this behavior I wrote a Red Hat Cluster agent to move a Manifold Agent on a 2 nodes cluster with the *-agent.sh scripts and I fixed the nohup.out file into a specific directory. The nohup.out file will be monitored by Nagios to identify the logging "Agent already in use" and the cluster fails the startup of agent when unclean situation happend before. Marcello On 11/06/2013 05:09 PM, Marcello Lorenzi wrote:
Hi All, I'm trying to install and testing the Manifold agent on a clustered environment based on CentOS 6, and I noticed a strange behavior of agent when the JVM PID were killed manually without using the stop-agents.sh scripts. In fact after the kill if I try to start the agent I noticed this messages "Agent already in use" and I couldn't start the agent. The only solution is to run locks-clean.sh script to mitigate the issue, but to run this script I have to stop the agent and the webconsole. Is it a correct procedure to cleanup the environment ? Thanks, Marcello
