Comment 2 for bug 1396757
Revision history for this message
| Jay Janssen (jay-janssen) wrote Re: [Bug 1396757] rhel7 / systemd -- killing mysqld causes lingering systemd processes | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Ah, thanks for the clarification. systemctl stop mysql is a reasonable workaround and we had to do that before systemd, it’s just much less obvious that it is what is needed.
Is it a bug that systemctl start mysql hangs when this timeout is in play? Isn’t an error message better, or is that not systemd’s way?
> On Nov 27, 2014, at 6:13 AM, Raghavendra D Prabhu <email address hidden> wrote:
>
> The 'garbage' is due to the fact that mysqld is SIGkilled but its PID
> file still remains, so the script waits for it upto timeout (900s) and
> then exits. This is same behavior as 'service mysql stop'. So,
> removing the stale PID file should also do.
>
> In any case, I have modified it to check for this and mysql-systemd
> will exit early.
>
> On a long term, this can be fixed by replacing mysqld_safe and calling
> mysqld directly in unit file. That should avoid any need for these
> pre/post scripts.
Jay Janssen, Managing Consultant, Percona
http://