This may be a silly question, but does the pid file actually exist?
Have you checked yourself?

I'm running into an issue like this myself, which seems to be
triggered by a slow shutdown of one thread (on port 8001, say).
Capistrano doesn't wait for the shutdown and tries to do a restart,
but when the new thread on 8001 starts it can't write the pid file
because the old one is still shutting down. Then the next time I do a
rake deploy, the pid file doesn't exist and I lose touch with the
thread.

At least, that's my best current theory.

On Feb 20, 9:02 am, "Brian LeRoux" <[EMAIL PROTECTED]> wrote:
> Ok ---thanks guys, I tried specifying a full path for the pid but still no go.
> This must be a permissions issue.. but the directory is open to the
> world to modify. This is odd.
>
> On 2/20/07, Luis Lavena <[EMAIL PROTECTED]> wrote:
>
>
>
> > On 2/20/07, Brian LeRoux <[EMAIL PROTECTED]> wrote:
>
> > > I'm getting the following error when I stop mongrel..... I know its
> > > running but I need the log files. It appears the log isn't being
> > > created / written to. I this message:
>
> > > !!! PID file log/mongrel.8000.pid does not exist.  Not running?
>
> > > This is my mongrel_cluster.yml
> > > ---
> > > cwd: /var/rails/soca/current
> > > port: "8000"
> > > environment: production
> > > address: 127.0.0.1
> > > pid_file: log/mongrel.pid
> > > servers: 2
>
> > > .....and I've the following permissions on the directory:
>
> > > drwxrwxrwx   2 bleroux root 4096 Feb 19 16:44 log
>
> > > Which is here:
>
> > > [EMAIL PROTECTED] current]# pwd
> > > /var/rails/soca/current
>
> > > Any ideas??
>
> > It is a known bug. You should specify full path log and pid files for
> > mongrel_cluster.
>
> > --
> > Luis Lavena
> > Multimedia systems
> > -
> > Leaders are made, they are not born. They are made by hard effort,
> > which is the price which all of us must pay to achieve any goal that
> > is worthwhile.
> > Vince Lombardi


--~--~---------~--~----~------------~-------~--~----~
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