" Fixed as of the upcoming 5.7.27, 8.0.17 release, and here's the
changelog entry "
So, judging by:
mysql-server | 5.7.31-0ubuntu0.18.04.1 | bionic-updates | all
and
mysql-server | 8.0.20-0ubuntu0.19.10.1 | eoan-updates | all
and
mysql-server | 8.0.21-0ubuntu0.20.04.3 |
** Also affects: mariadb-10.3 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10 minutes to stop without message
** Also affects: mysql-server via
http://bugs.mysql.com/bug.php?id=93708
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server
https://bugs.mysql.com/bug.php?id=93708
** Bug watch added: MySQL Bug System #93708
http://bugs.mysql.com/bug.php?id=93708
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql
Yes, it will delay the start of MySQL server but the consequence of
going backward in time after MySQL is started are important enough to
me.
Regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm just going by
https://github.com/systemd/systemd/issues/5097#issuecomment-276787961
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10 minutes to stop without
I just made the test to be sure: using Wants= does not prevent MySQL to
start event if the system never reaches “time-sync.target”.
I added an ntpdate.service:
# /etc/systemd/system/ntpdate.service
[Unit]
Description=Force synchronisation of time
ConditionPathExists=/etc/default/ntpdate
> * fixing mysql.service to use After=time-sync.target and Wants=time-
sync.target
As far as I understand this is unsuitable to be done by default since
not all systems will necessarily ever reach "time synced", for example
if they're intentionally being used offline.
But this does seem like a
I think the problem can be solved with:
* recent systemd fixes https://github.com/systemd/systemd/issues/5097 (with a
workaround for older versions)
* fixing mysql.service to use After=time-sync.target and Wants=time-sync.target
Regards.
** Bug watch added: github.com/systemd/systemd/issues
Hi,
Same happening on ubuntu server 18.04. Fresh install , just apache and mysql
without ntp. Machine is a VM in esxi 6.5. During restart “A stop job is running
to for Mysql Community Server” and 10 min of waiting.
I was trying tzdata reconfigure and ntp service, but it's not permanent.
Any
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
Confirmed, MySQL stops sometimes 10 minutes, there is no setting to
change this ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10 minutes to stop without message
I don't think there will be a fix to this problem in Ubuntu until it is
fixed upstream. I suggest you ask there.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10
Any fix to this problem yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10 minutes to stop without message after time drift
To manage notifications about this
I solved my above time jump problem by installing the VirtualBox guest
additions as described here: https://www.virtualbox.org/manual/ch04.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
** Attachment added: "error-20170210.log"
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164/+attachment/4816680/+files/error-20170210.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also have this problem with Ubuntu 16.04.2 LTS:
| $ lsb_release --all
| No LSB modules are available.
| Distributor ID: Ubuntu
| Description:Ubuntu 16.04.2 LTS
| Release:16.04
| Codename: xenial
|
| $ dmidecode -s system-product-name
| VirtualBox
After a reboot the activation
** Changed in: mysql-5.7 (Ubuntu)
Assignee: (unassigned) => Norvald H. Ryeng (nryeng)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10 minutes to stop without
I go this problem, however, adding After=ntp.service wouldn't fix it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
Mysql server take 10 minutes to stop without message after time
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: mysql-5.7 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1600164
Title:
I'm not sure it's reasonable to adjust service startups. Following that
logic, every package would have to start after ntp.service, and there
should be a more general solution to that problem.
Can MySQL be adjusted to be a little more robust to the time changing
when it is idle? I understand that
I _think_ adding After=ntp.service would be safe (does not imply
Requires), but need to learn more about the ordering and dependency
system in systemd first.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
22 matches
Mail list logo
