Evan Weaver on 22 Jan 2008 06:53:34 -0800 |
You can do whatever you want in a monit environment via 'env'. For example, one of my monit start commands looks like: start program = "/usr/bin/sudo -u app /usr/bin/env LD_LIBRARY_PATH=/opt/aspell/lib:/opt/freeimage/lib:/opt/mysql5/devel-default/lib/mysql PATH=/opt/ruby/default/bin:/opt/sphinx/default/bin:/opt/mysql5/client-default-5.0/bin:/opt/mysql5/devel-default/bin:/opt/aspell/bin:/bin:/usr/bin INLINEDIR=/opt/rails/chow/production/current/tmp/inline mongrel_rails cluster::start -C /opt/rails/chow/production/current/config/mongrel_cluster.production.yml --clean --only 10220" Evan On Jan 22, 2008 9:47 AM, Andrew Libby <alibby@tangeis.com> wrote: > > > Randy Schmidt wrote: > >> You probably want to be using mongrel::cluster with the --clean flag. > >> Mongrel_rails won't restart daemons that were hard killed by Monit and > >> didn't remove their PID file. > >> > > > > I started by using /usr/local/bin/mongrel_rails cluster:: but that > > calls mongrel_rails (without an absolute path) which monit can't find. > > Monit has a very slim PATH setup and you can't add to it. I guess I > > could add a symlink from a place in the Monit PATH but I have a hard > > time believing that will fix the problem since my start and stop > > programs work fine from the command line. > > > > > Could you make sure mongrel_rails is in the path before making your > call? The symlink would > also work, me thinks. > > > > > Andy > > _______________________________________________ > To unsubscribe or change your settings, visit: > http://lists.phillyonrails.org/mailman/listinfo/talk > -- Evan Weaver Cloudburst, LLC _______________________________________________ To unsubscribe or change your settings, visit: http://lists.phillyonrails.org/mailman/listinfo/talk
|
|