Ubuntu 16.04 : can t apt due to mysql-server-5.7 issue
I'm trying to install / update packages and everytime the process fails because of a mysql-server error :
sudo apt install graylog-server
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
graylog-server is already the newest version (2.0.3-1).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 10 non mis à jour.
2 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Paramétrage de mysql-server-5.7 (5.7.12-0ubuntu1.1) ...
Checking if update is needed.
Checking server version.
Running queries to upgrade MySQL server.
mysql_upgrade: (non fatal) [ERROR] 1545: Failed to open mysql.event
Checking system database.
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.engine_cost OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.gtid_executed OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.server_cost OK
mysql.servers OK
mysql.slave_master_info OK
mysql.slave_relay_log_info OK
mysql.slave_worker_info OK
mysql.slow_log OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
The sys schema is already up to date (version 1.5.0).
Found 0 sys functions, but expected 21. Re-installing the sys schema.
Upgrading the sys schema.
mysql_upgrade: [ERROR] 1136: Column count doesn't match value count at row 1
mysql_upgrade failed with exit status 5
dpkg: erreur de traitement du paquet mysql-server-5.7 (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent.
dpkg: des problèmes de dépendances empêchent la configuration de mysql-server :
mysql-server dépend de mysql-server-5.7 ; cependant :
Le paquet mysql-server-5.7 n'est pas encore configuré.
dpkg: erreur de traitement du paquet mysql-server (--configure) :
problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
mysql-server-5.7
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
I did purge and reinstall mysql-server, I even set password to null without expiration for debian-sys-maint ( it's on a dev computer so no sensitive data ) but the issue still remains.
I don't know how to solve it and it's very annoyince since now I can't even update my system because this process is involved every time.
Thanks for you help !
apt 16.04 mysql
add a comment |
I'm trying to install / update packages and everytime the process fails because of a mysql-server error :
sudo apt install graylog-server
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
graylog-server is already the newest version (2.0.3-1).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 10 non mis à jour.
2 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Paramétrage de mysql-server-5.7 (5.7.12-0ubuntu1.1) ...
Checking if update is needed.
Checking server version.
Running queries to upgrade MySQL server.
mysql_upgrade: (non fatal) [ERROR] 1545: Failed to open mysql.event
Checking system database.
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.engine_cost OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.gtid_executed OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.server_cost OK
mysql.servers OK
mysql.slave_master_info OK
mysql.slave_relay_log_info OK
mysql.slave_worker_info OK
mysql.slow_log OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
The sys schema is already up to date (version 1.5.0).
Found 0 sys functions, but expected 21. Re-installing the sys schema.
Upgrading the sys schema.
mysql_upgrade: [ERROR] 1136: Column count doesn't match value count at row 1
mysql_upgrade failed with exit status 5
dpkg: erreur de traitement du paquet mysql-server-5.7 (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent.
dpkg: des problèmes de dépendances empêchent la configuration de mysql-server :
mysql-server dépend de mysql-server-5.7 ; cependant :
Le paquet mysql-server-5.7 n'est pas encore configuré.
dpkg: erreur de traitement du paquet mysql-server (--configure) :
problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
mysql-server-5.7
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
I did purge and reinstall mysql-server, I even set password to null without expiration for debian-sys-maint ( it's on a dev computer so no sensitive data ) but the issue still remains.
I don't know how to solve it and it's very annoyince since now I can't even update my system because this process is involved every time.
Thanks for you help !
apt 16.04 mysql
Possible duplicate of mysql installation stuck on Ubuntu 16.04 (no root user privilege)
– Rael Gugelmin Cunha
Apr 23 '18 at 21:28
@RaelGugelminCunha: I doubt it. The accepted answer on this question are quite different from the answers to your linked question.
– David Foerster
Apr 24 '18 at 7:24
add a comment |
I'm trying to install / update packages and everytime the process fails because of a mysql-server error :
sudo apt install graylog-server
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
graylog-server is already the newest version (2.0.3-1).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 10 non mis à jour.
2 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Paramétrage de mysql-server-5.7 (5.7.12-0ubuntu1.1) ...
Checking if update is needed.
Checking server version.
Running queries to upgrade MySQL server.
mysql_upgrade: (non fatal) [ERROR] 1545: Failed to open mysql.event
Checking system database.
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.engine_cost OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.gtid_executed OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.server_cost OK
mysql.servers OK
mysql.slave_master_info OK
mysql.slave_relay_log_info OK
mysql.slave_worker_info OK
mysql.slow_log OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
The sys schema is already up to date (version 1.5.0).
Found 0 sys functions, but expected 21. Re-installing the sys schema.
Upgrading the sys schema.
mysql_upgrade: [ERROR] 1136: Column count doesn't match value count at row 1
mysql_upgrade failed with exit status 5
dpkg: erreur de traitement du paquet mysql-server-5.7 (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent.
dpkg: des problèmes de dépendances empêchent la configuration de mysql-server :
mysql-server dépend de mysql-server-5.7 ; cependant :
Le paquet mysql-server-5.7 n'est pas encore configuré.
dpkg: erreur de traitement du paquet mysql-server (--configure) :
problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
mysql-server-5.7
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
I did purge and reinstall mysql-server, I even set password to null without expiration for debian-sys-maint ( it's on a dev computer so no sensitive data ) but the issue still remains.
I don't know how to solve it and it's very annoyince since now I can't even update my system because this process is involved every time.
Thanks for you help !
apt 16.04 mysql
I'm trying to install / update packages and everytime the process fails because of a mysql-server error :
sudo apt install graylog-server
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
graylog-server is already the newest version (2.0.3-1).
0 mis à jour, 0 nouvellement installés, 0 à enlever et 10 non mis à jour.
2 partiellement installés ou enlevés.
Après cette opération, 0 o d'espace disque supplémentaires seront utilisés.
Souhaitez-vous continuer ? [O/n] o
Paramétrage de mysql-server-5.7 (5.7.12-0ubuntu1.1) ...
Checking if update is needed.
Checking server version.
Running queries to upgrade MySQL server.
mysql_upgrade: (non fatal) [ERROR] 1545: Failed to open mysql.event
Checking system database.
mysql.column_stats OK
mysql.columns_priv OK
mysql.db OK
mysql.engine_cost OK
mysql.event OK
mysql.func OK
mysql.general_log OK
mysql.gtid_executed OK
mysql.gtid_slave_pos OK
mysql.help_category OK
mysql.help_keyword OK
mysql.help_relation OK
mysql.help_topic OK
mysql.host OK
mysql.index_stats OK
mysql.innodb_index_stats OK
mysql.innodb_table_stats OK
mysql.ndb_binlog_index OK
mysql.plugin OK
mysql.proc OK
mysql.procs_priv OK
mysql.proxies_priv OK
mysql.roles_mapping OK
mysql.server_cost OK
mysql.servers OK
mysql.slave_master_info OK
mysql.slave_relay_log_info OK
mysql.slave_worker_info OK
mysql.slow_log OK
mysql.table_stats OK
mysql.tables_priv OK
mysql.time_zone OK
mysql.time_zone_leap_second OK
mysql.time_zone_name OK
mysql.time_zone_transition OK
mysql.time_zone_transition_type OK
mysql.user OK
The sys schema is already up to date (version 1.5.0).
Found 0 sys functions, but expected 21. Re-installing the sys schema.
Upgrading the sys schema.
mysql_upgrade: [ERROR] 1136: Column count doesn't match value count at row 1
mysql_upgrade failed with exit status 5
dpkg: erreur de traitement du paquet mysql-server-5.7 (--configure) :
le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1
Aucun rapport « apport » n'a été créé car le message d'erreur indique une erreur consécutive à un échec précédent.
dpkg: des problèmes de dépendances empêchent la configuration de mysql-server :
mysql-server dépend de mysql-server-5.7 ; cependant :
Le paquet mysql-server-5.7 n'est pas encore configuré.
dpkg: erreur de traitement du paquet mysql-server (--configure) :
problèmes de dépendances - laissé non configuré
Des erreurs ont été rencontrées pendant l'exécution :
mysql-server-5.7
mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
I did purge and reinstall mysql-server, I even set password to null without expiration for debian-sys-maint ( it's on a dev computer so no sensitive data ) but the issue still remains.
I don't know how to solve it and it's very annoyince since now I can't even update my system because this process is involved every time.
Thanks for you help !
apt 16.04 mysql
apt 16.04 mysql
edited Oct 25 '16 at 23:03
Jeremy
1,46531832
1,46531832
asked Jul 6 '16 at 9:13
Charles-Antoine FournelCharles-Antoine Fournel
14415
14415
Possible duplicate of mysql installation stuck on Ubuntu 16.04 (no root user privilege)
– Rael Gugelmin Cunha
Apr 23 '18 at 21:28
@RaelGugelminCunha: I doubt it. The accepted answer on this question are quite different from the answers to your linked question.
– David Foerster
Apr 24 '18 at 7:24
add a comment |
Possible duplicate of mysql installation stuck on Ubuntu 16.04 (no root user privilege)
– Rael Gugelmin Cunha
Apr 23 '18 at 21:28
@RaelGugelminCunha: I doubt it. The accepted answer on this question are quite different from the answers to your linked question.
– David Foerster
Apr 24 '18 at 7:24
Possible duplicate of mysql installation stuck on Ubuntu 16.04 (no root user privilege)
– Rael Gugelmin Cunha
Apr 23 '18 at 21:28
Possible duplicate of mysql installation stuck on Ubuntu 16.04 (no root user privilege)
– Rael Gugelmin Cunha
Apr 23 '18 at 21:28
@RaelGugelminCunha: I doubt it. The accepted answer on this question are quite different from the answers to your linked question.
– David Foerster
Apr 24 '18 at 7:24
@RaelGugelminCunha: I doubt it. The accepted answer on this question are quite different from the answers to your linked question.
– David Foerster
Apr 24 '18 at 7:24
add a comment |
4 Answers
4
active
oldest
votes
I managed to fix this without having to purge everything. It seems the problem is that the sys schema database was never created, so here's the solution:
- Clone https://github.com/mysql/mysql-sys and
cd
into the cloned folder. - In a terminal, run
mysql -u root -p < ./sys_57.sql
(orsys_56.sql
, depending on your version) - Enjoy mysql_upgrade working again.
I guess this probably was, as @skerit said, an upgrading scripts mess-up.
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of thelast_update
column in the internalmysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.
– Marc
Jul 31 '17 at 1:51
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
add a comment |
Someone messed up the upgrade scripts, and in an LTS release no less.
The main problem lies in the upgrading of the system schema. If you don't want to delete all your data, you can force the update like this:
mysql_upgrade -uroot -p --verbose --skip-sys-schema
This is a dirty workaround, of course, since the system schema is now not what it's supposed to be, but at least you can continue using mysql.
1
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
add a comment |
I removed only /var/lib/mysql/sys
dir and then ran this command:
mysql_update -u root -p
All went fine.
add a comment |
I finally remove everything mysql components ( mysql-server, mysql-server-5.7, mysql-server-core-5.7 ) and data ( /var/lib/mysql , /etc/mysql ) and do a fresh install of it .
Everythings works fine now.
I thing the mysql internal dbs were somehow corrupted or with data missing during the migration from 5.6 to 5.7 ( from the change log , the column password from user table has been deleted for a new one )
hope it will help
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f795467%2fubuntu-16-04-can-t-apt-due-to-mysql-server-5-7-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
I managed to fix this without having to purge everything. It seems the problem is that the sys schema database was never created, so here's the solution:
- Clone https://github.com/mysql/mysql-sys and
cd
into the cloned folder. - In a terminal, run
mysql -u root -p < ./sys_57.sql
(orsys_56.sql
, depending on your version) - Enjoy mysql_upgrade working again.
I guess this probably was, as @skerit said, an upgrading scripts mess-up.
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of thelast_update
column in the internalmysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.
– Marc
Jul 31 '17 at 1:51
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
add a comment |
I managed to fix this without having to purge everything. It seems the problem is that the sys schema database was never created, so here's the solution:
- Clone https://github.com/mysql/mysql-sys and
cd
into the cloned folder. - In a terminal, run
mysql -u root -p < ./sys_57.sql
(orsys_56.sql
, depending on your version) - Enjoy mysql_upgrade working again.
I guess this probably was, as @skerit said, an upgrading scripts mess-up.
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of thelast_update
column in the internalmysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.
– Marc
Jul 31 '17 at 1:51
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
add a comment |
I managed to fix this without having to purge everything. It seems the problem is that the sys schema database was never created, so here's the solution:
- Clone https://github.com/mysql/mysql-sys and
cd
into the cloned folder. - In a terminal, run
mysql -u root -p < ./sys_57.sql
(orsys_56.sql
, depending on your version) - Enjoy mysql_upgrade working again.
I guess this probably was, as @skerit said, an upgrading scripts mess-up.
I managed to fix this without having to purge everything. It seems the problem is that the sys schema database was never created, so here's the solution:
- Clone https://github.com/mysql/mysql-sys and
cd
into the cloned folder. - In a terminal, run
mysql -u root -p < ./sys_57.sql
(orsys_56.sql
, depending on your version) - Enjoy mysql_upgrade working again.
I guess this probably was, as @skerit said, an upgrading scripts mess-up.
edited Dec 4 '16 at 19:41
answered Oct 25 '16 at 22:36
MarcMarc
28634
28634
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of thelast_update
column in the internalmysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.
– Marc
Jul 31 '17 at 1:51
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
add a comment |
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of thelast_update
column in the internalmysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.
– Marc
Jul 31 '17 at 1:51
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
This worked but I had to login to mysql and run the sql file using the source command.
– cnizzardini
Dec 15 '16 at 8:26
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of the
last_update
column in the internal mysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.– Marc
Jul 31 '17 at 1:51
So, this has happened again to me, using Ubuntu 17.04. This time apparently it's a type mismatch of the
last_update
column in the internal mysql.innodb_index_stats
table. I don't know if it's the packager's, MySQL's or someone else's fault, but my recommendation after my experience with MySQL since 16.04 is that you migrate to MariaDB as soon as you can. Like, tomorrow if possible.– Marc
Jul 31 '17 at 1:51
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
I have had problems with MariaDb as well as its basically the same as MySQL. Most new stuff I am doing is in PostgreSQL.
– cnizzardini
Aug 1 '17 at 16:35
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
This is still happening in Ubuntu 17.10... I upgraded Ubuntu for the sole reason to get rid of this annoyance.... FFS UBUNTU!
– BlackDivine
Jan 26 '18 at 6:17
add a comment |
Someone messed up the upgrade scripts, and in an LTS release no less.
The main problem lies in the upgrading of the system schema. If you don't want to delete all your data, you can force the update like this:
mysql_upgrade -uroot -p --verbose --skip-sys-schema
This is a dirty workaround, of course, since the system schema is now not what it's supposed to be, but at least you can continue using mysql.
1
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
add a comment |
Someone messed up the upgrade scripts, and in an LTS release no less.
The main problem lies in the upgrading of the system schema. If you don't want to delete all your data, you can force the update like this:
mysql_upgrade -uroot -p --verbose --skip-sys-schema
This is a dirty workaround, of course, since the system schema is now not what it's supposed to be, but at least you can continue using mysql.
1
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
add a comment |
Someone messed up the upgrade scripts, and in an LTS release no less.
The main problem lies in the upgrading of the system schema. If you don't want to delete all your data, you can force the update like this:
mysql_upgrade -uroot -p --verbose --skip-sys-schema
This is a dirty workaround, of course, since the system schema is now not what it's supposed to be, but at least you can continue using mysql.
Someone messed up the upgrade scripts, and in an LTS release no less.
The main problem lies in the upgrading of the system schema. If you don't want to delete all your data, you can force the update like this:
mysql_upgrade -uroot -p --verbose --skip-sys-schema
This is a dirty workaround, of course, since the system schema is now not what it's supposed to be, but at least you can continue using mysql.
answered Jul 28 '16 at 10:15
skeritskerit
63941431
63941431
1
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
add a comment |
1
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
1
1
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
Yeah the idiots at mysql screwed up
– Stevie G
Feb 25 '17 at 14:37
add a comment |
I removed only /var/lib/mysql/sys
dir and then ran this command:
mysql_update -u root -p
All went fine.
add a comment |
I removed only /var/lib/mysql/sys
dir and then ran this command:
mysql_update -u root -p
All went fine.
add a comment |
I removed only /var/lib/mysql/sys
dir and then ran this command:
mysql_update -u root -p
All went fine.
I removed only /var/lib/mysql/sys
dir and then ran this command:
mysql_update -u root -p
All went fine.
edited Feb 6 at 10:48
answered Jan 29 at 18:54
Fabio ZeriFabio Zeri
12
12
add a comment |
add a comment |
I finally remove everything mysql components ( mysql-server, mysql-server-5.7, mysql-server-core-5.7 ) and data ( /var/lib/mysql , /etc/mysql ) and do a fresh install of it .
Everythings works fine now.
I thing the mysql internal dbs were somehow corrupted or with data missing during the migration from 5.6 to 5.7 ( from the change log , the column password from user table has been deleted for a new one )
hope it will help
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
add a comment |
I finally remove everything mysql components ( mysql-server, mysql-server-5.7, mysql-server-core-5.7 ) and data ( /var/lib/mysql , /etc/mysql ) and do a fresh install of it .
Everythings works fine now.
I thing the mysql internal dbs were somehow corrupted or with data missing during the migration from 5.6 to 5.7 ( from the change log , the column password from user table has been deleted for a new one )
hope it will help
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
add a comment |
I finally remove everything mysql components ( mysql-server, mysql-server-5.7, mysql-server-core-5.7 ) and data ( /var/lib/mysql , /etc/mysql ) and do a fresh install of it .
Everythings works fine now.
I thing the mysql internal dbs were somehow corrupted or with data missing during the migration from 5.6 to 5.7 ( from the change log , the column password from user table has been deleted for a new one )
hope it will help
I finally remove everything mysql components ( mysql-server, mysql-server-5.7, mysql-server-core-5.7 ) and data ( /var/lib/mysql , /etc/mysql ) and do a fresh install of it .
Everythings works fine now.
I thing the mysql internal dbs were somehow corrupted or with data missing during the migration from 5.6 to 5.7 ( from the change log , the column password from user table has been deleted for a new one )
hope it will help
answered Jul 7 '16 at 7:08
Charles-Antoine FournelCharles-Antoine Fournel
14415
14415
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
add a comment |
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
I recommend editing this answer to expand it with specific details about how to do this. (See also How do I write a good answer? for general advice about what sorts of answers are considered most valuable on AskUbuntu.)
– David Foerster
Oct 25 '16 at 23:03
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f795467%2fubuntu-16-04-can-t-apt-due-to-mysql-server-5-7-issue%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of mysql installation stuck on Ubuntu 16.04 (no root user privilege)
– Rael Gugelmin Cunha
Apr 23 '18 at 21:28
@RaelGugelminCunha: I doubt it. The accepted answer on this question are quite different from the answers to your linked question.
– David Foerster
Apr 24 '18 at 7:24