mysql stop/restart fails + breaking mysql + reboots
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mariadb-10.0 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
mysql-5.6 (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
[Status]
Cannot reproduce - see comment 20. Without steps that someone else can follow to reproduce the problem from a fresh system, we don't expect to make any progress on this issue.
[Original Description]
This is a huge problem.
After several iterations of - service mysql {start|
The problem becomes - service mysql stop - hangs forever, upon attempting...
exec systemctl stop mysql.service
What's required then is one of these...
mysqladmin -uroot -p shutdown
pkill mysqld
Neither of these is acceptable.
The biggest problem is this breakage also breaks reboots.
The reboot sequence depends on services doing what's expected, so when systemctl stop mysql.service hangs, reboot hangs too.
Because of the lunacy of the entire systemctl subsystem, sshd is correctly killed off while msqld hangs.
At this point, there's no way to ssh into system + a power recycle must be done to complete a reboot sequence.
/bin/systemctl is an executable with no apparent way to debug it's logic.
Please update this bug with details about how to debug /bin/systemctl + I'll post output.
Changed in mariadb-10.0 (Ubuntu): | |
status: | Incomplete → Won't Fix |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem.
We have instructions on debugging some types of problems at http:// wiki.ubuntu. com/DebuggingPr ocedures
At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Instead of "several iterations" please can you describe exactly how to reproduce the problem on a fresh Ubuntu machine?
You've also not said anything about Ubuntu release or version numbers, and you've filed this bug against mysql-dfsg-5.1. MySQL 5.1 never shipped in a release that also shipped systemd. Please reassign to the correct package (maybe mysql-5.6) and then execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1468804
When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https:/ /wiki.ubuntu. com/ReportingBu gs.
Once you've fixed this bug reporting issues, please change the bug status back to New.
Thanks!