Mongrel won't start

after doing some server updates I can no longer start mongrel or at
least get it working. I get 404’s whenever I now try to access a
dynamic page.

This is what I get when I run cap deploy:restart

** [out :: li21-118.members.linode.com] !!! PID file
/var/rails/communitycms/current/tmp/pids/mongrel.8002.pid already
exists. Mongrel could be running already. Check your
/var/rails/communitycms/current/log/mongrel.8002.log for errors.
** [out :: li21-118.members.linode.com]
** [out :: li21-118.members.linode.com] **
** [out :: li21-118.members.linode.com] !!! Exiting with error. You
must stop mongrel and clear the .pid before I’ll attempt a start.
** [out :: li21-118.members.linode.com]

I get the same thing if I rub cap deploy:stop first.

There is no useful information in the mongrel.xxx.log files.

Any help would be greatly appreciated.

When reading the error messages it sounded like it said that it WAS
already running, but in the end it was the just the pid files that
remained. Deleting them from the RAILS/tmp/pids folder fixed things

On Sun, 2008-01-27 at 16:49 +0100, Chris O. wrote:

When reading the error messages it sounded like it said that it WAS
already running, but in the end it was the just the pid files that
remained. Deleting them from the RAILS/tmp/pids folder fixed things

Another option is to use mongrel_cluster_ctl with the --clean option;
that’ll delete stale pids for you. I usually ensure that my mongrel
init scripts include this option so’s to make sure that they’ll come up
if the server crashes.

Yours,

Tom

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs