This may be a bit of a strange case, but i'm using version 0.82 and if
i don't have a running thin process and try to do a restart, the
process currently hangs.
If I execute these commands, the terminal output 'Can't stop
process...' is the last thing I see, ie I never get the cursor back.
[dereky@thin]$ sudo thin stop -d -C /etc/thin/back_end.conf
Sending QUIT signal to process 2046 ...
[dereky@thin]$ sudo thin restart -d -C /etc/thin/back_end.conf
Can't stop process, no PID found in tmp/pids/thin.pid
I can see that this still running by in another window on the same
box..
ps -ef | grep thin
root 2060 1971 99 16:05 pts/0 00:02:43 ruby /usr/bin/thin
restart -d -C /etc/thin/back_end.conf
Has anyone else seen this? My fear is that if someone issues a
capistrano stop then a restart, or we do a restart on an idle server,
it won't start up cleanly which is what I really want.
> This may be a bit of a strange case, but i'm using version 0.82 and if
> i don't have a running thin process and try to do a restart, the
> process currently hangs.
> If I execute these commands, the terminal output 'Can't stop
> process...' is the last thing I see, ie I never get the cursor back.
> [dereky@thin]$ sudo thin stop -d -C /etc/thin/back_end.conf
> Sending QUIT signal to process 2046 ...
> [dereky@thin]$ sudo thin restart -d -C /etc/thin/back_end.conf
> Can't stop process, no PID found in tmp/pids/thin.pid
> I can see that this still running by in another window on the same
> box..
> ps -ef | grep thin
> root 2060 1971 99 16:05 pts/0 00:02:43 ruby /usr/bin/thin
> restart -d -C /etc/thin/back_end.conf
> Has anyone else seen this? My fear is that if someone issues a
> capistrano stop then a restart, or we do a restart on an idle server,
> it won't start up cleanly which is what I really want.
> On May 14, 4:20 pm, dereky <derek...@gmail.com> wrote:
> > This may be a bit of a strange case, but i'm using version 0.82 and if
> > i don't have a running thin process and try to do a restart, the
> > process currently hangs.
> > If I execute these commands, the terminal output 'Can't stop
> > process...' is the last thing I see, ie I never get the cursor back.
> > [dereky@thin]$ sudo thin stop -d -C /etc/thin/back_end.conf
> > Sending QUIT signal to process 2046 ...
> > [dereky@thin]$ sudo thin restart -d -C /etc/thin/back_end.conf
> > Can't stop process, no PID found in tmp/pids/thin.pid
> > I can see that this still running by in another window on the same
> > box..
> > ps -ef | grep thin
> > root 2060 1971 99 16:05 pts/0 00:02:43 ruby /usr/bin/thin
> > restart -d -C /etc/thin/back_end.conf
> > Has anyone else seen this? My fear is that if someone issues a
> > capistrano stop then a restart, or we do a restart on an idle server,
> > it won't start up cleanly which is what I really want.
> As a workaround you can force thin to cluster mode by specify -s1
> option or "servers: 1" in your config file.
> On May 14, 4:43 pm, dereky <derek...@gmail.com> wrote:
> > sorry meant version 0.80..
> > On May 14, 4:20 pm, dereky <derek...@gmail.com> wrote:
> > > This may be a bit of a strange case, but i'm using version 0.82 and if
> > > i don't have a running thin process and try to do a restart, the
> > > process currently hangs.
> > > If I execute these commands, the terminal output 'Can't stop
> > > process...' is the last thing I see, ie I never get the cursor back.
> > > [dereky@thin]$ sudo thin stop -d -C /etc/thin/back_end.conf
> > > Sending QUIT signal to process 2046 ...
> > > [dereky@thin]$ sudo thin restart -d -C /etc/thin/back_end.conf
> > > Can't stop process, no PID found in tmp/pids/thin.pid
> > > I can see that this still running by in another window on the same
> > > box..
> > > ps -ef | grep thin
> > > root 2060 1971 99 16:05 pts/0 00:02:43 ruby /usr/bin/thin
> > > restart -d -C /etc/thin/back_end.conf
> > > Has anyone else seen this? My fear is that if someone issues a
> > > capistrano stop then a restart, or we do a restart on an idle server,
> > > it won't start up cleanly which is what I really want.
