We need more info in order to help. What is the main problem, how to make the process run correctly or how to get it offline? If it is a process, what did you use for existence monitor? Is it a script or something else?
You are missing the stop operation (at least for tomcat). In that case when you shutdown the process, nothing gets executed and Autostart keeps waiting for the existence monitor to exit with an errorcode (which will never happen). Depending on the existence monitor used you can either manually do whatever it takes to make it exist with an errorcode or edit the appropriate existence monitor in $FT_DIR/StateMon/E_*.* and just enter exit (1); in the first line. All this assuming that you are using a script for the existence monitor at all.
Or alternatively, open the ftcli command line interface for autostart and force the status of the process to offline:
ftcli> ForceProcState [Proc_ID] offline
I think the command is correct as I am talking from the top of my head, but this should get you going. Once executed the process should go to offline state.
If the interactive process is brought online in the same session in which the first interactive AutoStart process was configured, then the process will not start until the user logs off and logs in back to the node, even though the console would show the process status to be online.
tribicic
157 Posts
1206
0
Posted November 8th, 2010 05:00
We need more info in order to help. What is the main problem, how to make the process run correctly or how to get it offline? If it is a process, what did you use for existence monitor? Is it a script or something else?