Bug 1676605 referred to this from comment 18:
> I found some other issues too when I tried reinstalling from scratch -
/etc/mysql/my.cnf has the line "!includedir /etc/mysql/conf.d/", but
/etc/mysql/conf.d no longer exists if you have purged mysql before
reinstalling, so the server won't start up
ñ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults were
customised
To manage notifications about this bug go to:
https://bugs.l
@Robie Basak
The main problem is that all the packages that rely on an active mysql-server
to upgrade themselves will stop and ask what to do, thus you anyway need to
babysit them :)
At this point, having the upgrade of Mysql-Server stopping if it was on
and could not restart will only stop the
On Tue, Oct 11, 2016 at 09:37:56AM -, Christian Deligant wrote:
> What happened is that mysql-server did not restart, probably throwing a
> complain but without stopping (and upgrading from 14.04 to 16.04 means
> 2900 MB of stuff to download, running on an SSD you really don't even
> notice wha
I understand your concern.
My installation had a separate cnf file in the conf.d directory with a
couple of personal settings affecting the mysqld, among them the old
slow-query variables.
This was done in order to have the my.cnf upgrade smoothly among time.
What happened is that mysql-server d
Christian:
There are too many things that could go wrong for users if the server itself
ignores something in the config file and uses what it considers a safe default.
For the packaging we are working on working around the issue of the
server not starting in cases where users have disabled the au
Why couldn't mysql-server just throw a warning on an unknown variable and start
with a default?
Especially during a release update, mysql is critical when many packages rely
on a DB-based content to upgrade themselves (Mediawiki, otrs, etc)
--
You received this bug notification because you are
So, if I understand correctly, after the upgrade, I'll still have a
my.cnf file *exactly* as I left it, but the config file mysql will be
using will be a my.cnf.migrated file, which will be a best-guess at
auto-migrating my custom config. Is this correct?
After double-checking my.cnf.migrated and
@Rocko
Sounds like you have an issue unrelated to this bug. See
http://www.ubuntu.com/support/community for community support options,
or if you think there is a different bug in Ubuntu, then please file
that with full details.
@Mohamed
In short, yes. If you don't have a customised configuration
Hi, so just to clarify, for those of us using do-release-upgrade from
14.04 to 16.04.1, we don't need to worry about manually renaming "key-
buffer-size" and "myisam-recover-options", and all that will
automatically be taken care of for us?
--
You received this bug notification because you are a
I found that when it tried to install mysql-5.7 -
5.7.13-0ubuntu0.16.04.2, dpkg just hung forever at postinst (in this
case, forever means overnight). The only way around this was to kill -9
the two mysqld processes that ran (I think one was already running, and
then another ran when I killed the f
This bug was fixed in the package mysql-5.7 - 5.7.13-0ubuntu0.16.04.2
---
mysql-5.7 (5.7.13-0ubuntu0.16.04.2) xenial-security; urgency=medium
* SECURITY UPDATE: Update to 5.7.13 to fix security issues (LP: #1604796)
-
http://www.oracle.com/technetwork/security-advisory/cpujul20
I've spent some time testing this fix in Xenial. It was broken for two
reasons:
1) I failed to update the version string check in mysql-
server-5.7.postinst in preparing the SRU, so the migration code never
ran. This isn't a regression, just a failure to fix the problem as
intended.
2) On an upgr
Comment #14 Solved after remove and reinstall (Update not work).
Sorry #14 unnecessary comment.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgra
This:
insserv: warning: current start runlevel(s) (empty) of script `mysql' overrides
LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (0 1 2 3 4 5 6) of script `mysql'
overrides LSB defaults (0 1 6).
Solved:
sudo update-rc.d -f mysql remove && sudo update-rc.d mysql default
#12 You're still using the "old" package (5.7.12-0ubuntu1.1) that fails
but I'm talking about the one in proposed (see #10) (5.7.12-0ubuntu1.2).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
T
furin@furin-K43SD:~$ sudo apt-get install -f
[sudo] password for furin:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
linux-headers-4.4.0-22 linux-headers-4.4.0-22-generic
Latest package in SUR doesn't solves the problem for me. Moreover, log
in /var/log/mysql.log is empty. Can you tell me how can I provide debug
info?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/157186
Hello Joel, or anyone else affected,
Accepted mysql-5.7 into xenial-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/mysql-5.7/5.7.12-0ubuntu1.2 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
http
Uploaded to Xenial. SRU team: you may find it easier to review if you
verify my uploaded delta is the same as
https://git.launchpad.net/~racb/ubuntu/+source/mysql-5.7/log/?h=mysql-5.7/ubuntu/xenial
and then use that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Thanks Mitch. I've updated the workaround accordingly.
** Description changed:
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped
with options "key-buffer" and "myisam-recover". In 5.7, these option
names have been removed and replaced with "key-buffer-size" and "myisam-
** Description changed:
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped
with options "key-buffer" and "myisam-recover". In 5.7, these option
names have been removed and replaced with "key-buffer-size" and "myisam-
recover-options" instead. If a user customised /etc/my
** Description changed:
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped
with options "key-buffer" and "myisam-recover". In 5.7, these option
names have been removed and replaced with "key-buffer-size" and "myisam-
recover-options" instead. If a user customised /etc/my
** Changed in: mysql-5.7 (Ubuntu Xenial)
Milestone: None => ubuntu-16.04.1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults we
This bug was fixed in the package mysql-5.7 - 5.7.13-0ubuntu3
---
mysql-5.7 (5.7.13-0ubuntu3) yakkety; urgency=medium
* Automatically replace removed config options from 5.5 and old 5.6
installations (LP: #1571865). Cherry-picked from Debian VCS ef3f92b.
Thanks to Lars Tangv
** Changed in: mysql-5.7 (Ubuntu Xenial)
Status: Triaged => In Progress
** Changed in: mysql-5.7 (Ubuntu Xenial)
Assignee: Lars Tangvald (lars-tangvald) => Robie Basak (racb)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: mysql-5.7 (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults wer
I had spent a few hours on this with no resolution. Even with the mysql
service running as root, it failed to get permissions to write to a data
directory other than /var/lib/mysql (or whatever the default is if that's
wrong). Even with apparmor configured to allow the new data directory, and
eve
Re: [Workaround Option 3/3]
I tried this method, placing my local customizations in
/etc/mysql/mysql.conf.d/local.cnf but mysqld did not pick those up. I
had to name my file zzlocal.cnf. I'm guessing it reads those file in
alpha order, with the later files overriding the earlier.
--
You received
** Changed in: mysql-5.7 (Ubuntu)
Milestone: None => ubuntu-16.05
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults were
cust
** Changed in: mysql-5.7 (Ubuntu)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
** Changed in: mysql-5.7 (Ubuntu Xenial)
Assignee: (unassigned) => Lars Tangvald (lars-tangvald)
** Changed in: mysql-5.7 (Ubuntu)
Status: Triaged => In Progress
--
You received this bug n
In my case there was no customization. All 3 of my effected 16.04
servers were fresh installs of 16.04 during the development phase of
16.04. This was all two or three weeks ago. I finally sorted out the
mess, by re-installing mysql.
--
You received this bug notification because you are a member
** Also affects: mysql-5.7 (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: mysql-5.7 (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: mysql-5.7 (Ubuntu Xenial)
Status: New => Triaged
--
You received this bug notification because you are a member
** Changed in: mysql-5.7 (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults were
c
This was wrongly marked as fixed by me. Please rollback that change.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults were
custo
** Changed in: mysql-5.7 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571865
Title:
mysql fails to start after upgrade if previous defaults were
c
** Tags added: dist-upgrade
** Also affects: ubuntu-release-notes
Importance: Undecided
Status: New
** Changed in: ubuntu-release-notes
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
http
** Description changed:
In 14.04 (both in 5.5 and 5.6), the default /etc/mysql/my.cnf shipped
with options "key-buffer" and "myisam-recover". In 5.7, these option
names have been removed and replaced with "key-buffer-size" and "myisam-
recover-options" instead. If a user customised /etc/my
38 matches
Mail list logo
