I just spent the last hour trying to figure out how to start/stop cruise control as needed. I am setting up cruise controll with phpundercontrol and I was able to get the web interface to load, but using kill all and ps aux and killing cruise control would actually stop cruisecontrol but it appeared as if it left dependencies running, particularly ‘jetty’. When I would restart cruise-control it would not start back up, it would spew out java errors.
Supposedly pressing cntrl+c is supposed to stop cruisecontrol. It turns out the default cruisecontrol.sh needs to be edited. After removing a ‘&’ from one of the EXEC calls towards the bottom of the file, pressing control + c gives me:
2009-11-08 02:38:36.862::INFO: Graceful shutdown SelectChannelConnector@0.0.0.0:8080
2009-11-08 02:38:36.863::INFO: Graceful shutdown org.mortbay.jetty.webapp.WebAppContext@6d3d7254{/dashboard,file:/opt/cruisecontrol/webapps/dashboard/}
2009-11-08 02:38:36.863::INFO: Graceful shutdown org.mortbay.jetty.webapp.WebAppContext@5d1d20d3{/cruisecontrol,file:/opt/cruisecontrol/webapps/cruisecontrol/}
2009-11-08 02:38:36.863::INFO: Graceful shutdown org.mortbay.jetty.webapp.WebAppContext@23562c67{/documentation,file:/opt/cruisecontrol/webapps/documentation/}
2009-11-08 02:38:36.864::INFO: Graceful shutdown org.mortbay.jetty.webapp.WebAppContext@6e7d3050{/cc-config,file:/opt/cruisecontrol/webapps/cc-config/}
2009-11-08 02:38:37.789:/dashboard:INFO: Destroying Spring FrameworkServlet 'spring-exceptions'
2009-11-08 02:38:37.790:/dashboard:INFO: Destroying Spring FrameworkServlet 'spring-tabs'
2009-11-08 02:38:37.790:/dashboard:INFO: Destroying Spring FrameworkServlet 'spring-ajax'
2009-11-08 02:38:37.791:/dashboard:INFO: Destroying Spring FrameworkServlet 'spring-pages'
2009-11-08 02:38:37.793:/dashboard:INFO: Shutting down Log4J
2009-11-08 02:38:37.823:/dashboard:INFO: Closing Spring root WebApplicationContext
2009-11-08 02:38:37.927::INFO: Shutdown hook complete
I can then run ./cruisecontrol.sh again to start it back up. This thwarted the need for me to set up init.d scripts, I found a few bloggers were doing it that way but their init.d scripts were literred with calls to dependencies I just couldn’t setup right on my distro. daemon_log_message, daemon_start_stop, which belong to the LSB linux standard base library “init-tools”. Which I installed but those commands were not found. Luckily I found the simple fix, and unlucky it took an hour plus.