MySQL Bugs: #92480: mysql-server: ails because mysql is still running after the stop

Bug #92480	mysql-server: ails because mysql is still running after the stop
Submitted:	18 Sep 2018 12:14	Modified:	20 Sep 2018 12:34
Reporter:	Amol Arote	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Server	Severity:	S1 (Critical)
Version:	5.5.59	OS:	CentOS
Assigned to:		CPU Architecture:	x86

Description:
mysql-server: service start/stop or restart sometimes fails because mysql is still running after the stop

How to repeat:
Error not occurred every time, as par my observation error occurred if services stopped for some time.

Not enough information was provided for us to be able to handle this bug. Please re-read the instructions at http://bugs.mysql.com/how-to-report.php

If you can provide more information, feel free to add it to this bug and change the status back to 'Open'.

Thank you for your interest in MySQL.

Dear Team,

we are using mysql 5.5.59 for our production server,which is recently migrated from myswl 5.0.
from couple of months everything is working fine and no such logs or issues found in any thing.
recently we was trying to made replication and backup of one mysql server and for that we stop mysqld service and
copy data file for replication..
after copying data when we tried to start mysqld for replication server it take long time and got failed

180915 19:05:47 InnoDB: The InnoDB memory heap is disabled
180915 19:05:47 InnoDB: Mutexes and rw_locks use GCC atomic builtins
180915 19:05:47 InnoDB: Compressed tables use zlib 1.2.3
180915 19:05:47 InnoDB: Using Linux native AIO
180915 19:05:47 InnoDB: Initializing buffer pool, size = 256.0G
180915 19:05:57 InnoDB: Completed initialization of buffer pool
180915 19:05:58 InnoDB: highest supported file format is Barracuda.

after checking process we found other mysql instance was still running on server.which seems wired to us.

we again restart service and this time it starts properly.
we done this 2- time and their is no such issue found on this server.
but same activity we done with other server and result is same..again mysql is failed first time.

for main database server ( whose replication wants to create) we want to perform same thing for rechecking.
this time on main DB service got failed for first time.

this can cause the database lost too if such things can happen regularly.
please let me know if their is any kind of bug in 5.5.59. as previously we were using 5.0 version.
we never face such indecent of service frailer so frequently.