2 Mongrel_rails and monit are not the best of friends. It's difficult to get them to work together. For example, this is the error I got in my monit logs when switching to a new mongrel_rails command that cleans up stale pids: <code> 'mongrel_1' process is not running 'mongrel_2' trying to restart 'mongrel_3' start: /usr/local/bin/mongrel_rails 'mongrel_4' failed to start </code> To fix it I added the following start_command to the monit configuration: <code> /usr/bin/env PATH=/usr/local/bin/:$PATH mongrel_rails cluster::start -C /var/www.... --clean --only 8000 </code> The problem is that monit overrides the PATH environment variable, so it won't find mongrel_rails unless you tell it where to find it. Monit also contains a bug which doesn't tell you why it can't start mongrel_rails, but that's another story... Note that I'm using the --clean switch which will startup the mongrels even if a stale pid exists. In fact I got so tired of the whole mess I wrote a plugin that "generates a working monit configuration for mongrel_rails":http://github.com/christianhellsten/monit_conf/ from one or more mongrel_cluster.yml configuration files. 0 2008-11-17T01:57:25+02:00 275 131 <p>Mongrel_rails and monit are not the best of friends. It&#8217;s difficult to get them to work together.</p> <p>For example, this is the error I got in my monit logs when switching to a new mongrel_rails command that cleans up stale pids:</p> <p><pre class="active4d"><span class="line-numbers"> 1 </span> <span class="String"><span class="String">'</span>mongrel_1<span class="String">'</span></span> process is not running <span class="line-numbers"> 2 </span> <span class="String"><span class="String">'</span>mongrel_2<span class="String">'</span></span> trying to restart <span class="line-numbers"> 3 </span> <span class="String"><span class="String">'</span>mongrel_3<span class="String">'</span></span> start: /usr/local/bin/mongrel_rails <span class="line-numbers"> 4 </span> <span class="String"><span class="String">'</span>mongrel_4<span class="String">'</span></span> failed to start </pre></p> <p>To fix it I added the following start_command to the monit configuration:</p> <p><pre class="active4d"><span class="line-numbers"> 1 </span> /usr/bin/env PATH=/usr/local/bin/:<span class="Variable"><span class="Variable">$</span>PATH</span> mongrel_rails cluster::start -C /var/www.... --clean --only 8000 </pre></p> <p>The problem is that monit overrides the <span class="caps">PATH</span> environment variable, so it won&#8217;t find mongrel_rails unless you tell it where to find it.<br /> Monit also contains a bug which doesn&#8217;t tell you why it can&#8217;t start mongrel_rails, but that&#8217;s another story&#8230;</p> <p>Note that I&#8217;m using the &#8212;clean switch which will startup the mongrels even if a stale pid exists.</p> <p>In fact I got so tired of the whole mess I wrote a plugin that <a href="http://github.com/christianhellsten/monit_conf/">generates a working monit configuration for mongrel_rails</a> from one or more mongrel_cluster.yml configuration files.</p> 2008-11-17T01:57:58+02:00