Re: daemontools and mysqld

Actually, no.  localhost.pid contains the last pid in
the group of mysqld processes (it is a mysqld pid).

The problem is that daemontools sends the SIGTERM to
the first pid in the group of mysqld processes and the
pid it is expecting is the very last mysqld pid.

Now the question is:  How do I get daemontools to send
the SIGTERM to the last mysqld pid instead of the
first?


Gary


--- Paul Jarc <[email protected]> wrote:

> "Gary C. New" <[email protected]> wrote:
> > svstat /service/mysqld
> > /service/mysqld: up (pid 4849) 60 seconds
> >
> > cat /home/mysql/data/localhost.pid
> > 4858
> >
> > ps aux|grep mysql
> > root      4848  0.0  0.1  1392  308 ?        S  
> 19:00   0:00 supervise mysqld
> > mysql     4849  0.2  8.0 57476 20684 ?       S  
> 19:00   0:00 /usr/local/mysql/
> 
> So localhost.pid contains the pid of supervise, not
> mysqld?  That's
> pretty odd.  Manually killing supervise results in
> supervise being
> restarted by svscan, and the new supervise doesn't
> know about the
> previous "svc -d".  It starts a new instance of
> mysqld without any
> attempt to kill the old one.  But all your pids are
> grouped close
> together, so they seem to be all from the same
> instance.  I can't say
> how the old one finally exited.  Try "svc -d
> /service/mysqld" again,
> and if it still stays up, run a system call trace on
> mysqld (process
> 4849 in this case) to see what it's doing.
> 
> 
> paul
>