Hi!

I think the best is to just ignore those compaints.. I don't know 
either..

But this will solve your stale PIDs problem:

http://textsnippets.com/posts/show/931

I used this patch from the guy in the comments:

---------------------------------
Index: bin/mongrel_rails
===================================================================
--- bin/mongrel_rails   (revision 536)
+++ bin/mongrel_rails   (working copy)
@@ -83,9 +83,17 @@
       config = Mongrel::Rails::RailsConfigurator.new(settings) do
         if defaults[:daemon]
           if File.exist? defaults[:pid_file]
-            log "!!! PID file #{defaults[:pid_file]} already exists. 
Mongrel c$
-            log "!!! Exiting with error.  You must stop mongrel and 
clear the .$
-            exit 1
+            # mongrels that crash can leave stale PID files behind, and 
these
+            # should not stop mongrel from being restarted by 
monitors...
+            pid = File.new(defaults[:pid_file]).readline
+            running = Process.kill(0, pid.to_i) rescue nil
+            if running
+              log "!!! PID file #{defaults[:pid_file]} already exists 
and the p$
+              exit 1
+            else
+              log "!!! PID file #{defaults[:pid_file]} exists, but is 
stale, an$
+              File.delete(defaults[:pid_file])
+            end
           end

           daemonize
---------------------------------

Apply it in mongrel directory (probably 
/usr/lib/ruby/gems/1.8/gems/mongrel-x.x.x/) by:
patch -p0 < /path/to/mongrel_stale_pid_file.patch



I'm now going back troubleshooting my mongrel_cluster autostart 
problem!? If anyone has ideas:

I can say "/etc/init.d/mongrel_cluster start" and it starts just fine, 
but when I restart the system, it doesn't start...

I did issue:
"sudo update-rc.d mongrel_cluster defaults" and got:
 Adding system startup for /etc/init.d/mongrel_cluster ...
   /etc/rc0.d/K20mongrel_cluster -> ../init.d/mongrel_cluster
   /etc/rc1.d/K20mongrel_cluster -> ../init.d/mongrel_cluster
   /etc/rc6.d/K20mongrel_cluster -> ../init.d/mongrel_cluster
   /etc/rc2.d/S20mongrel_cluster -> ../init.d/mongrel_cluster
   /etc/rc3.d/S20mongrel_cluster -> ../init.d/mongrel_cluster
   /etc/rc4.d/S20mongrel_cluster -> ../init.d/mongrel_cluster
   /etc/rc5.d/S20mongrel_cluster -> ../init.d/mongrel_cluster


Strange, very strange!!
nginx is starting fine.. I tried to remove / add nginx links with 
update-rc.d and it still worked.. but cluster just won't start.. What 
could possibly be causing this?

David
-- 
Posted via http://www.ruby-forum.com/.

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Deploying Rails" group.
To post to this group, send email to rubyonrails-deployment@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/rubyonrails-deployment?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to