1 votes

L'installation de MySQL ne se termine pas correctement sur Ubuntu 20.04

J'ai essayé de supprimer tout ce qui est lié à l'ancienne installation en utilisant purge, y compris les configurations. Cela a commencé à se produire après la mise à jour vers Ubuntu 20.04 et la suppression de l'ancienne installation mysql faite dans Ubuntu 18.04.

(EDIT) après un long moment, le terminal affiche cette erreur :

Job for mysql.service failed because a timeout was exceeded.
See "systemctl status mysql.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
 mysql.service - MySQL Community Server
     Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: 
enabled)
    Drop-In: /etc/systemd/system/mysql.service.d
             override.conf
     Active: activating (auto-restart) (Result: timeout) since Mon 2020-10-26 19
:06:58 PKT; 6ms ago
    Process: 103253 ExecStartPre=/usr/share/mysql/mysql-systemd-start pre (code=
exited, status=0/SUCCESS)
    Process: 103280 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/run/mysql
d/mysqld.pid --skip-grant-tables --skip-networking (code=exited, status=0/SUCCES
S)
   Main PID: 103280 (code=exited, status=0/SUCCESS)
     Status: "Server shutdown complete"
      Error: 2 (No such file or directory)

 26 19:06:58 in01-nbk-429 systemd[1]: mysql.service: Scheduled restart job
, restart counter is at 1.
 26 19:06:58 in01-nbk-429 systemd[1]: Stopped MySQL Community Server.
 26 19:06:58 in01-nbk-429 systemd[1]: Starting MySQL Community Server...
dpkg: error processing package mysql-server-8.0 (--configure):
 installed mysql-server-8.0 package post-installation script subprocess returned
 error exit status 1
dpkg: dependency problems prevent configuration of mysql-server:
 mysql-server depends on mysql-server-8.0; however:
  Package mysql-server-8.0 is not configured yet.

dpkg: error processing package mysql-server (--configure):
 dependency problems - leaving unconfigured
Processing triggers for systemd (245.4-4ubuntu3.2) ...
No apport report written because the error message indicates its a followup erro
r from a previous failure.
                          Processing triggers for man-db (2.9.1-1) ...
Processing triggers for libc-bin (2.31-0ubuntu9.1) ...
Errors were encountered while processing:
 mysql-server-8.0
 mysql-server
E: Sub-process /usr/bin/dpkg returned an error code (1)
W: Operation was interrupted before it could finish

C'est la sortie de mon terminal pendant l'installation et il s'arrête ici pendant un long moment.

reading /usr/share/mecab/dic/ipadic/Noun.proper.csv ... 27328
reading /usr/share/mecab/dic/ipadic/Adverb.csv ... 3032
reading /usr/share/mecab/dic/ipadic/Noun.csv ... 60477
reading /usr/share/mecab/dic/ipadic/Noun.number.csv ... 42
reading /usr/share/mecab/dic/ipadic/Adj.csv ... 27210
emitting double-array: 100% |###########################################| 
reading /usr/share/mecab/dic/ipadic/matrix.def ... 1316x1316
emitting matrix      : 100% |###########################################| 

done!
update-alternatives: using /var/lib/mecab/dic/ipadic-utf8 to provide /var/lib/me
cab/dic/debian (mecab-dictionary) in auto mode
Setting up mysql-server-8.0 (8.0.21-0ubuntu0.20.04.4) ...
update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my
.cnf) in auto mode
Renaming removed key_buffer and myisam-recover options (if present)
mysqld will log errors to /var/log/mysql/error.log
mysqld is running as pid 102997
Created symlink /etc/systemd/system/multi-user.target.wants/mysql.service  /lib
/systemd/system/mysql.service.

c'est mon /var/log/mysql/error.log

2020-10-26T13:56:47.953648Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 102995
2020-10-26T13:56:47.988142Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-26T13:56:48.523413Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-26T13:56:48.704356Z 0 [ERROR] [MY-011292] [Server] Plugin mysqlx reported: 'Preparation of I/O interfaces failed, X Protocol won't be accessible'
2020-10-26T13:56:48.704600Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
2020-10-26T13:56:48.827698Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-26T13:56:48.827982Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-26T13:56:48.834057Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory.
2020-10-26T13:56:48.872336Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.21-0ubuntu0.20.04.4'  socket: '/tmp/tmp.cPePEr7iWv/mysqld.sock'  port: 0  (Ubuntu).
2020-10-26T13:56:48.926842Z 0 [System] [MY-013172] [Server] Received SHUTDOWN from user <via user signal>. Shutting down mysqld (Version: 8.0.21-0ubuntu0.20.04.4).
2020-10-26T13:56:50.282042Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu).
2020-10-26T13:56:51.586812Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 103061
2020-10-26T13:56:51.595462Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-26T13:56:52.057199Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-26T13:56:52.228093Z 0 [ERROR] [MY-011300] [Server] Plugin mysqlx reported: 'Setup of socket: '/var/run/mysqld/mysqlx.sock' failed, can't create lock file /var/run/mysqld/mysqlx.sock.lock'
2020-10-26T13:56:52.228512Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060
2020-10-26T13:56:52.334615Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-26T13:56:52.334923Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-26T13:56:52.347505Z 0 [Warning] [MY-011810] [Server] Insecure configuration for --pid-file: Location '/tmp' in the path is accessible to all OS users. Consider choosing a different directory.
2020-10-26T13:56:52.387655Z 7 [System] [MY-013172] [Server] Received SHUTDOWN from user boot. Shutting down mysqld (Version: 8.0.21-0ubuntu0.20.04.4).
2020-10-26T13:56:54.774192Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.21-0ubuntu0.20.04.4)  (Ubuntu).
2020-10-26T13:56:57.028746Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.21-0ubuntu0.20.04.4) starting as process 103271
2020-10-26T13:56:57.052635Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-10-26T13:56:57.522416Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-10-26T13:56:57.719154Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: /var/run/mysqld/mysqlx.sock
2020-10-26T13:56:57.876130Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-10-26T13:56:57.876430Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel.
2020-10-26T13:56:57.890871Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.21-0ubuntu0.20.04.4'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  (Ubuntu).

1voto

rbrussell82 Points 31

Vérifiez /var/log/syslog après avoir exécuté apt update. J'ai eu les mêmes problèmes que vous et dans mon syslog j'ai trouvé quelques entrées qui commençaient par apparmor="DENIED" operation="open" profile="/usr/sbin/mysqld"

Si AppArmor est activé et que mysqld est en mode renforcé, il se peut que vous ayez un problème. L'exécution de ces commandes désactivera AppArmor pour MySQL, puis j'ai pu mettre à jour MySQL.

sudo ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/
sudo apparmor_parser -R /etc/apparmor.d/disable/usr.sbin.mysqld

Pour en savoir plus sur mon dépannage, cliquez ici : Erreurs de mise à jour de MySQL 8.0 sur Ubuntu 20.04

SistemesEz.com

SystemesEZ est une communauté de sysadmins où vous pouvez résoudre vos problèmes et vos doutes. Vous pouvez consulter les questions des autres sysadmins, poser vos propres questions ou résoudre celles des autres.

Powered by:

X