FYI - a new "category" for this bug is recently in a few bug reports.
If sql_mode was set to NO_AUTO_CREATE_USER this won't work anymore.
Thereby triggering the usual "failed to upgrade, can't restart" condition.
In that case please check upstreams documentation on sql_mode, so far
all users
As this bug still unresolved (surprised to see its from 2016), I have to post
another night night headache bug #1899075.
I should agree with this bug author.
Release upgrade script should not block due any package upgrade error. Any fail
in a package upgrade should be just an warning, to be
Thanks will do have a look cheers Robbie
On Tue, 19 Nov 2019, 11:46 Robie Basak, <1612...@bugs.launchpad.net>
wrote:
> We're getting some additional duplicates of this bug against MySQL 8.0.
> It might be an idea to look through the recent dupes and try to identify
> a list of common failures
Robie even
On Tue, 19 Nov 2019, 17:34 Neale Francis, wrote:
> Thanks will do have a look cheers Robbie
>
> On Tue, 19 Nov 2019, 11:46 Robie Basak, <1612...@bugs.launchpad.net>
> wrote:
>
>> We're getting some additional duplicates of this bug against MySQL 8.0.
>> It might be an idea to look
We're getting some additional duplicates of this bug against MySQL 8.0.
It might be an idea to look through the recent dupes and try to identify
a list of common failures that we could automatically attempt to fix in
postinst.
--
You received this bug notification because you are a member of
** Description changed:
Separate from LP: #1571865 because this concerns options we don't try to
automatically fix.
When users upgrade from 5.5 (and especially if that was also an upgrade
from earlier versions) and have custom configs, 5.7 may refuse to start
because the config
** Description changed:
Separate from LP: #1571865 because this concerns options we don't try to
automatically fix.
When users upgrade from 5.5 (and especially if that was also an upgrade
from earlier versions) and have custom configs, 5.7 may refuse to start
because the config
This failure also occurs because "log_slow_queries" has become
"slow_query_log", but the installer does not handle this change
automagically. Like the OP's error, nothing specific to it is mentioned
in the installation failure message.
--
You received this bug notification because you are a
thread_concurrency was removed in 5.7. It only had an effect on older
Solaris systems, so simply removing it from the config should not cause
any change.
https://dev.mysql.com/doc/refman/5.7/en/server-system-
variables.html#sysvar_thread_concurrency
--
You received this bug notification because
2017-05-11T04:47:57.464320Z 0 [ERROR] unknown variable
'thread_concurrency=8'
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612517
Title:
Server fails to start after upgrade because of customized
** Changed in: mysql-5.7 (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1612517
Title:
Server fails to start after upgrade because of customized config
** Summary changed:
- Server fails to start after because of customized config and obsolete/renamed
directives
+ Server fails to start after upgrade because of customized config and
obsolete/renamed directives
--
You received this bug notification because you are a member of Ubuntu
Bugs,
12 matches
Mail list logo
