| Bug #60141 | Server wiht named pipes enabled won't stop reliably | ||
|---|---|---|---|
| Submitted: | 16 Feb 2011 13:13 | Modified: | 2 Mar 2011 17:34 |
| Reporter: | Peter Laursen (Basic Quality Contributor) | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Server | Severity: | S2 (Serious) |
| Version: | 5.1.55, 5.5.9 | OS: | Windows (7/64) |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | qc | ||
[16 Feb 2011 13:14]
Peter Laursen
"net stop" takes forever
Attachment: forever.jpg (image/jpeg, text), 41.02 KiB.
[16 Feb 2011 13:52]
MySQL Verification Team
Thank you for the bug report. Could you please see if related to: http://bugs.mysql.com/bug.php?id=31621 Thanks in advance.
[16 Feb 2011 14:51]
Peter Laursen
It looks similar to me. But if it is the same or not ('internally') is difficult for me to tell. Service does stop *sometimes* - but after several minutes. But at several occasions it did not even after 15 minutes. There is no particular load on the system.
But the old report was/should have been fixed in 5.1.41/5.5.0 it seems? So either
1) the fix was not complete
2) there is a regression
3) or it is not same
.. I don't know I should be able to provide a definite reply to the question.
[16 Feb 2011 16:01]
MySQL Verification Team
What you need to check to verify if are the same is the server shutdown hangs when exist idle connection (some client application connected and inactive). Thanks in advance.
[16 Feb 2011 16:13]
Peter Laursen
It is not that simple. It seems that I will have to use the server instance for a while. * starting service * connecting * executing SHOW DATABASES * wait a few minutes * stopping service .. does not reproduce the issue. It was consistently reproducible for me when I posted this with both 5.1 and 5.5 (they had been running since the morning - around 6 hours) but with little activity.
[18 Feb 2011 10:22]
Peter Laursen
I cannot reproduce this now. I think have tried around 20 times over the last days.
[2 Mar 2011 17:34]
MySQL Verification Team
I couldn't repeat too. Please re-open this bug report if you find a way to be easily repeatable. Thanks in advance.
Description: a service started with named pipes take an eternity to stop. Sometimes it seems it never stops. Have to kill the process after 10-15 minutes. How to repeat: 1) In configuration: [mysqld] enable-named-pipe port=3307 -- or any port no. .. 2) net start {servicename} -- starts fine after few seconds 3) net stop {servicename} -- lasts forever Suggested fix: stop the service! :-)