Hi fellows,
I have an issue that's happened quit a few times and I'm wondering
what might be a better configuration to avoid this issue.
The problem is if one of the mongrels in a cluster starts up and has
no pid file (I know this sounds odd, but it has happened quite a few
times, I don't know why). So all of the mongrels in the cluster start
up fine, but 1 ends up w/o a pid file. god comes along, finds no pid
so tries to start the mongrel instance, it fails because the port is
used and so no pid is written out, this happens over and over as god
discovers the missing pid each time. The end result is that nothing is
ever down, but I get emailed over and over by god saying it's trying
to start one of the mongrels. Here is the relevant extract of my
config:
w.start = "mongrel_rails start -c #{RAILS_ROOT} -p #{port} \
-P #{RAILS_ROOT}/tmp/pids/mongrel.#{port}.pid -e production -d"
# Conditions to start a mongrel
w.start_if do |start|
# If it's not running, start it
start.condition(:process_running) do |c|
c.running = false
c.notify = {:contacts => ['developers'], :priority =>
2, :category => 'god starting mongrel'}
end
end
What's a better way to configure mongrel start to avoid this problem?
Thanks!
Sean
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"god.rb" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/god-rb?hl=en
-~----------~----~----~----~------~----~------~--~---
