Got the same issue, found a possible explanation: my cloud provider store time in local timezone (earlier than UTC); at startup MySQL boot first, then NTP, which updates the time to UTC; therefore, MySQL literally "started in the future" (sounds interesting).
I can hotfix this by setting the timezone to UTC:
dpkg-reconfigure tzdata
After that MySQL can be stopped immediately. Even after I switch timezone back to local time, it can still stop or restart without problems. After rebooting the server (a KVM), I have to do this again unless the NTP timezone issue is fixed.
BTW, @darek334:
> MySQL stops sometimes 10 minutes
10 minutes is the timeout period defined in system/multi-user.target.wants/mysql.service (TimeoutSec=600).
Got the same issue, found a possible explanation: my cloud provider store time in local timezone (earlier than UTC); at startup MySQL boot first, then NTP, which updates the time to UTC; therefore, MySQL literally "started in the future" (sounds interesting).
I can hotfix this by setting the timezone to UTC:
dpkg-reconfigure tzdata
After that MySQL can be stopped immediately. Even after I switch timezone back to local time, it can still stop or restart without problems. After rebooting the server (a KVM), I have to do this again unless the NTP timezone issue is fixed.
BTW, @darek334:
> MySQL stops sometimes 10 minutes
10 minutes is the timeout period defined in system/ multi-user. target. wants/mysql. service (TimeoutSec=600).