Partage
  • Partager sur Facebook
  • Partager sur Twitter

Failed to start MariaDB 10.3.22 database server

installation serveur mysql | debian

16 juin 2020 à 14:07:32

Bonjour à toute et à tous !

je viens vers vous aujourd'hui car j'ai quelques soucis dans la configuration de mon serveur web sur debian..

J'ai installé mon serveur Lamp sans soucis apparent sauf une histoire de mysqli manquant quand je voulais lancer phpmyadmin ce qui a été résolu avec la commande :sudo apt install mariadb-server php7.3-mysql

en faite le truc c'est que je peine à me connecter sur phpmyadmin.

Au moment où je tente de me connecter j'ai deux messages d'erreurs

  • impossible de se connecter au serveur MySQL
  • mysqli_real_connect(); (HY000/2002): No such file or directory

et quand je fais la commande : sudo systemctl status mysql

sur mon terminal j'ai cela qui est retourné..

● mariadb.service - MariaDB 10.3.22 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Tue 2020-06-16 11:59:40 UTC; 5min ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 404 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCES
  Process: 444 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCE
  Process: 458 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`;
  Process: 471 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, statu
 Main PID: 471 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"

Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [Note] InnoDB: Starting shutdown...
Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENG
Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [ERROR] Could not open mysql.plugin table. Some plugi
Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Jun 16 11:59:40 vps-e7453ba8 mysqld[471]: 2020-06-16 11:59:40 0 [ERROR] Aborting
Jun 16 11:59:40 vps-e7453ba8 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 16 11:59:40 vps-e7453ba8 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 16 11:59:40 vps-e7453ba8 systemd[1]: Failed to start MariaDB 10.3.22 database server.

Je comprend maintenant pourquoi je peine à me connecter sur phpmyadmin si le serveur mysql ne démarre pas..

Mais je n'arrive pas à résoudre les erreurs retourné.

Quelqu'un peux m'aider ?

Merci d'avance :D

  • Partager sur Facebook
  • Partager sur Twitter
16 juin 2020 à 22:57:23

bonjour, que donne un

apt install mariadb-server



  • Partager sur Facebook
  • Partager sur Twitter
17 juin 2020 à 7:52:08

Bonjour, la commande me retourne cela :


Reading package lists... Done
Building dependency tree
Reading state information... Done
mariadb-server is already the newest version (1:10.3.22-0+deb10u1).
The following packages were automatically installed and are no longer required:
  libmecab2 libnuma1 mecab-ipadic mecab-ipadic-utf8 mecab-utils
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.

  • Partager sur Facebook
  • Partager sur Twitter
17 juin 2020 à 8:24:57

ok, donc il est bien installé..

Essayes:

systemctl restart mariadb
systemctl status mariadb
tail -n 50 /var/log/mysql/error.log



  • Partager sur Facebook
  • Partager sur Twitter
17 juin 2020 à 8:34:42

systemctl restart mariadb

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

systemctl status mariadb

 Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-06-17 06:32:51 UTC; 37s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 24660 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, statu
  Process: 24661 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, stat
  Process: 24663 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_
  Process: 24672 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exi
 Main PID: 24672 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"

Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [Note] InnoDB: Starting shutdown...
Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [ERROR] Plugin 'InnoDB' init function retur
Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [ERROR] Plugin 'InnoDB' registration as a S
Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [ERROR] Could not open mysql.plugin table.
Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [ERROR] Unknown/unsupported storage engine:
Jun 17 06:32:51 vps-e7453ba8 mysqld[24672]: 2020-06-17  6:32:51 0 [ERROR] Aborting
Jun 17 06:32:51 vps-e7453ba8 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 17 06:32:51 vps-e7453ba8 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 17 06:32:51 vps-e7453ba8 systemd[1]: Failed to start MariaDB 10.3.22 database server.

sudo tail -n 50 /var/log/mysql/error.log

2020-06-16T05:54:27.318461Z 0 [System] [MY-013169] [Server] /usr/sbin/mysqld (mysqld 8.0.20) initializing of server in progress as process 31950
2020-06-16T05:54:27.325890Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-06-16T05:54:27.904590Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-06-16T05:54:29.337889Z 6 [Warning] [MY-010453] [Server] root@localhost is created with an empty password ! Please consider switching off the --initialize-insecure option.
2020-06-16T05:54:32.439070Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20) starting as process 31998
2020-06-16T05:54:32.454682Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-06-16T05:54:33.178283Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-06-16T05:54:33.360250Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
2020-06-16T05:54:33.563830Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-16T05:54:33.566136Z 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-06-16T05:54:33.592160Z 7 [System] [MY-013172] [Server] Received SHUTDOWN from user boot. Shutting down mysqld (Version: 8.0.20).
2020-06-16T05:54:35.104444Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20)  MySQL Community Server - GPL.
2020-06-16T05:54:36.008613Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20) starting as process 32129
2020-06-16T05:54:36.017437Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-06-16T05:54:36.269448Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-06-16T05:54:36.397070Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
2020-06-16T05:54:36.473057Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-16T05:54:36.494292Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2020-06-16T06:34:49.403507Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20)  MySQL Community Server - GPL.
2020-06-16T06:35:01.968856Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20) starting as process 499
2020-06-16T06:35:02.005266Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-06-16T06:35:02.417797Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-06-16T06:35:02.583117Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
2020-06-16T06:35:02.651417Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-16T06:35:02.685007Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2020-06-16T06:56:35.536466Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20)  MySQL Community Server - GPL.
2020-06-16T06:56:48.038908Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20) starting as process 498
2020-06-16T06:56:48.070692Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-06-16T06:56:48.462540Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-06-16T06:56:48.623927Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
2020-06-16T06:56:48.692696Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-16T06:56:48.722794Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2020-06-16T09:50:47.341957Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20)  MySQL Community Server - GPL.
2020-06-16T09:51:00.845871Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.20) starting as process 503
2020-06-16T09:51:00.877653Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
2020-06-16T09:51:01.345536Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended.
2020-06-16T09:51:01.570741Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Socket: '/var/run/mysqld/mysqlx.sock' bind-address: '::' port: 33060
2020-06-16T09:51:01.691328Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed.
2020-06-16T09:51:01.726018Z 0 [System] [MY-010931] [Server] /usr/sbin/mysqld: ready for connections. Version: '8.0.20'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  MySQL Community Server - GPL.
2020-06-16T11:41:07.178224Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.20)  MySQL Community Server - GPL.





  • Partager sur Facebook
  • Partager sur Twitter
17 juin 2020 à 10:17:33

ok, ça semble être un problème connu (https://manage.accuwebhosting.com/knowledgebase/2318/How-to-Fix-MySQL-Error-Plugin-andsharp039InnoDBandsharp039-registration-as-a-STORAGE-ENGINE-failed.html)

donc je suggère (en tant que root):

cd /var/lib/mysql
mv ib_logfile0 ib_logfile0.old
mv ib_logfile1 ib_logfile1.old
systemctl stop mariadb
systemctl start mariadb
systemctl status mariadb



  • Partager sur Facebook
  • Partager sur Twitter
17 juin 2020 à 10:32:11

voici les résultats des commandes

cd /var/lib/mysql
mv ib_logfile0 ib_logfile0.old
mv ib_logfile1 ib_logfile1.old
systemctl stop mariadb

start mariadb

cd /var/lib/mysql
mv ib_logfile0 ib_logfile0.old
mv ib_logfile1 ib_logfile1.old
systemctl stop mariadb

start mariadb

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
root@vps-e7453ba8:/var/lib/mysql# systemctl status mariadb
● mariadb.service - MariaDB 10.3.22 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-06-17 08:29:31 UTC; 16s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 3984 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
  Process: 3989 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
  Process: 3991 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= ||   VAR=`/usr/bin/galera_recovery`; [ $? -eq 0 ]   && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
  Process: 4000 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
 Main PID: 4000 (code=exited, status=1/FAILURE)
   Status: "MariaDB server is down"

Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [Note] InnoDB: Starting shutdown...
Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Jun 17 08:29:30 vps-e7453ba8 mysqld[4000]: 2020-06-17  8:29:30 0 [ERROR] Aborting
Jun 17 08:29:31 vps-e7453ba8 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jun 17 08:29:31 vps-e7453ba8 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 17 08:29:31 vps-e7453ba8 systemd[1]: Failed to start MariaDB 10.3.22 database server.

merci pour ton aide !

je vais voir de mon côté sur le lien..

  • Partager sur Facebook
  • Partager sur Twitter
17 juin 2020 à 13:59:06

Peut être plus d'info avec journalctl -xe après avoir fait le systemctl start
  • Partager sur Facebook
  • Partager sur Twitter
18 juin 2020 à 8:11:08

Bonjour, désolé pour la réponse tardive..

Pour la commande : 

systemctl start

elle me retourne la réponse :

Too few arguments.

du coup je fais la commande :

systemctl

et il me retourne plusieurs lignes dont celle-ci :

● logrotate.service                                                                           loaded failed failed    Rotate log files
● mariadb.service                                                                             loaded failed failed    MariaDB 10.3.22 database server

et la commande :

journalctl -xe

me retourne cela

Jun 18 06:06:15 vps-e7453ba8 sshd[23975]: Disconnected from invalid user stunnel 61.216.5.153 port 55058 [preauth]
Jun 18 06:06:17 vps-e7453ba8 sshd[23973]: Received disconnect from 49.234.227.137 port 49222:11: Bye Bye [preauth]
Jun 18 06:06:17 vps-e7453ba8 sshd[23973]: Disconnected from authenticating user root 49.234.227.137 port 49222 [preauth]
Jun 18 06:06:42 vps-e7453ba8 sshd[23978]: Received disconnect from 218.92.0.215 port 22928:11:  [preauth]
Jun 18 06:06:42 vps-e7453ba8 sshd[23978]: Disconnected from 218.92.0.215 port 22928 [preauth]
Jun 18 06:07:55 vps-e7453ba8 sshd[23984]: Invalid user timemachine from 202.62.224.61 port 46009
Jun 18 06:07:56 vps-e7453ba8 sshd[23984]: pam_unix(sshd:auth): check pass; user unknown
Jun 18 06:07:56 vps-e7453ba8 sshd[23984]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=202.62.224.61
Jun 18 06:07:58 vps-e7453ba8 sshd[23984]: Failed password for invalid user timemachine from 202.62.224.61 port 46009 ssh2
Jun 18 06:07:59 vps-e7453ba8 sshd[23984]: Received disconnect from 202.62.224.61 port 46009:11: Bye Bye [preauth]
Jun 18 06:07:59 vps-e7453ba8 sshd[23984]: Disconnected from invalid user timemachine 202.62.224.61 port 46009 [preauth]
Jun 18 06:08:20 vps-e7453ba8 proftpd[23844]: pam_unix(proftpd:session): session closed for user debian
Jun 18 06:08:30 vps-e7453ba8 sshd[23988]: Invalid user team2 from 35.234.136.100 port 34890
Jun 18 06:08:30 vps-e7453ba8 sshd[23988]: pam_unix(sshd:auth): check pass; user unknown
Jun 18 06:08:30 vps-e7453ba8 sshd[23988]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.234.136.100
Jun 18 06:08:33 vps-e7453ba8 sshd[23988]: Failed password for invalid user team2 from 35.234.136.100 port 34890 ssh2
Jun 18 06:08:35 vps-e7453ba8 sshd[23988]: Received disconnect from 35.234.136.100 port 34890:11: Bye Bye [preauth]
Jun 18 06:08:35 vps-e7453ba8 sshd[23988]: Disconnected from invalid user team2 35.234.136.100 port 34890 [preauth]
Jun 18 06:08:40 vps-e7453ba8 sshd[23991]: Invalid user operador from 111.171.207.224 port 56732
Jun 18 06:08:40 vps-e7453ba8 sshd[23991]: pam_unix(sshd:auth): check pass; user unknown
Jun 18 06:08:40 vps-e7453ba8 sshd[23991]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=111.171.207.224
Jun 18 06:08:42 vps-e7453ba8 sshd[23991]: Failed password for invalid user operador from 111.171.207.224 port 56732 ssh2
Jun 18 06:08:44 vps-e7453ba8 sshd[23991]: Received disconnect from 111.171.207.224 port 56732:11: Bye Bye [preauth]
Jun 18 06:08:44 vps-e7453ba8 sshd[23991]: Disconnected from invalid user operador 111.171.207.224 port 56732 [preauth]
Jun 18 06:08:56 vps-e7453ba8 sshd[23994]: Invalid user gsv from 35.214.141.53 port 46696
Jun 18 06:08:56 vps-e7453ba8 sshd[23994]: pam_unix(sshd:auth): check pass; user unknown
Jun 18 06:08:56 vps-e7453ba8 sshd[23994]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=35.214.141.53
Jun 18 06:08:58 vps-e7453ba8 sshd[23994]: Failed password for invalid user gsv from 35.214.141.53 port 46696 ssh2
Jun 18 06:08:58 vps-e7453ba8 sshd[23994]: Received disconnect from 35.214.141.53 port 46696:11: Bye Bye [preauth]
Jun 18 06:08:58 vps-e7453ba8 sshd[23994]: Disconnected from invalid user gsv 35.214.141.53 port 46696 [preauth]
Jun 18 06:09:01 vps-e7453ba8 CRON[23997]: pam_unix(cron:session): session opened for user root by (uid=0)
Jun 18 06:09:01 vps-e7453ba8 CRON[23998]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /usr/lib/php/sessionclean; fi)
Jun 18 06:09:01 vps-e7453ba8 CRON[23997]: pam_unix(cron:session): session closed for user root
Jun 18 06:09:20 vps-e7453ba8 systemd[1]: Starting Clean php session files...
-- Subject: A start job for unit phpsessionclean.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has begun execution.
--
-- The job identifier is 2381.
Jun 18 06:09:20 vps-e7453ba8 sessionclean[24001]: PHP Warning:  PHP Startup: Unable to load dynamic library '/path/to/extension/mysqli.so' (tried: /path/to/extension/mysqli.so (/path/to/extension/mysqli.so: cannot open shared object file
Jun 18 06:09:20 vps-e7453ba8 systemd[1]: phpsessionclean.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit phpsessionclean.service has successfully entered the 'dead' state.
Jun 18 06:09:20 vps-e7453ba8 systemd[1]: Started Clean php session files.
-- Subject: A start job for unit phpsessionclean.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit phpsessionclean.service has finished successfully.
--
-- The job identifier is 2381.
Jun 18 06:09:21 vps-e7453ba8 sshd[23999]: Invalid user wolfgang from 61.216.5.153 port 49812
Jun 18 06:09:21 vps-e7453ba8 sshd[23999]: pam_unix(sshd:auth): check pass; user unknown
Jun 18 06:09:21 vps-e7453ba8 sshd[23999]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=61.216.5.153
Jun 18 06:09:22 vps-e7453ba8 sshd[23999]: Failed password for invalid user wolfgang from 61.216.5.153 port 49812 ssh2
Jun 18 06:09:24 vps-e7453ba8 sshd[23999]: Received disconnect from 61.216.5.153 port 49812:11: Bye Bye [preauth]
Jun 18 06:09:24 vps-e7453ba8 sshd[23999]: Disconnected from invalid user wolfgang 61.216.5.153 port 49812 [preauth]



  • Partager sur Facebook
  • Partager sur Twitter
18 juin 2020 à 14:38:30

hmm c'est systemctl start mariadb puis journalctl -xe
  • Partager sur Facebook
  • Partager sur Twitter
19 juin 2020 à 8:14:46

Bonjour,

pour la commande

 systemctl start mariadb

cela me retourne :

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

et pour la seconde commande j'ai cela..

Jun 19 06:13:53 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:53 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
Jun 19 06:13:53 vps-e7453ba8 sshd[17035]: Received disconnect from 49.233.90.66 port 54480:11: Bye Bye [preauth]
Jun 19 06:13:53 vps-e7453ba8 sshd[17035]: Disconnected from invalid user testserver 49.233.90.66 port 54480 [preauth]
Jun 19 06:13:53 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:53 0 [Note] InnoDB: Starting shutdown...
Jun 19 06:13:54 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:54 0 [ERROR] Plugin 'InnoDB' init function returned error.
Jun 19 06:13:54 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:54 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
Jun 19 06:13:54 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:54 0 [Note] Plugin 'FEEDBACK' is disabled.
Jun 19 06:13:54 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:54 0 [ERROR] Could not open mysql.plugin table. Some plugins may be not loaded
Jun 19 06:13:54 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:54 0 [ERROR] Unknown/unsupported storage engine: InnoDB
Jun 19 06:13:54 vps-e7453ba8 mysqld[17053]: 2020-06-19  6:13:54 0 [ERROR] Aborting
Jun 19 06:13:54 vps-e7453ba8 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
-- Subject: Unit process exited
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- An ExecStart= process belonging to unit mariadb.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Jun 19 06:13:54 vps-e7453ba8 systemd[1]: mariadb.service: Failed with result 'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
Jun 19 06:13:54 vps-e7453ba8 systemd[1]: Failed to start MariaDB 10.3.22 database server.
-- Subject: A start job for unit mariadb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit mariadb.service has finished with a failure.
--
-- The job identifier is 5028 and the job result is failed.
Jun 19 06:14:03 vps-e7453ba8 sshd[17069]: Invalid user web3 from 128.199.141.33 port 42860
Jun 19 06:14:03 vps-e7453ba8 sshd[17069]: pam_unix(sshd:auth): check pass; user unknown
Jun 19 06:14:03 vps-e7453ba8 sshd[17069]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=128.199.141.33
Jun 19 06:14:05 vps-e7453ba8 sshd[17069]: Failed password for invalid user web3 from 128.199.141.33 port 42860 ssh2
Jun 19 06:14:06 vps-e7453ba8 sshd[17069]: Received disconnect from 128.199.141.33 port 42860:11: Bye Bye [preauth]
Jun 19 06:14:06 vps-e7453ba8 sshd[17069]: Disconnected from invalid user web3 128.199.141.33 port 42860 [preauth]
Jun 19 06:14:08 vps-e7453ba8 sshd[17074]: Invalid user lorence from 182.61.185.92 port 38712
Jun 19 06:14:08 vps-e7453ba8 sshd[17074]: pam_unix(sshd:auth): check pass; user unknown
Jun 19 06:14:08 vps-e7453ba8 sshd[17074]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=182.61.185.92
Jun 19 06:14:10 vps-e7453ba8 sshd[17074]: Failed password for invalid user lorence from 182.61.185.92 port 38712 ssh2
Jun 19 06:14:11 vps-e7453ba8 sshd[17072]: Invalid user dong from 121.46.26.126 port 49070
Jun 19 06:14:11 vps-e7453ba8 sshd[17072]: pam_unix(sshd:auth): check pass; user unknown
Jun 19 06:14:11 vps-e7453ba8 sshd[17072]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=121.46.26.126
Jun 19 06:14:11 vps-e7453ba8 sshd[17074]: Received disconnect from 182.61.185.92 port 38712:11: Bye Bye [preauth]
Jun 19 06:14:11 vps-e7453ba8 sshd[17074]: Disconnected from invalid user lorence 182.61.185.92 port 38712 [preauth]
Jun 19 06:14:12 vps-e7453ba8 sshd[17078]: Invalid user support from 167.99.194.54 port 57742
Jun 19 06:14:12 vps-e7453ba8 sshd[17078]: pam_unix(sshd:auth): check pass; user unknown
Jun 19 06:14:12 vps-e7453ba8 sshd[17078]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=167.99.194.54
Jun 19 06:14:13 vps-e7453ba8 sshd[17072]: Failed password for invalid user dong from 121.46.26.126 port 49070 ssh2
Jun 19 06:14:13 vps-e7453ba8 sshd[17072]: Received disconnect from 121.46.26.126 port 49070:11: Bye Bye [preauth]
Jun 19 06:14:13 vps-e7453ba8 sshd[17072]: Disconnected from invalid user dong 121.46.26.126 port 49070 [preauth]
Jun 19 06:14:14 vps-e7453ba8 sshd[17078]: Failed password for invalid user support from 167.99.194.54 port 57742 ssh2
Jun 19 06:14:15 vps-e7453ba8 sshd[17078]: Received disconnect from 167.99.194.54 port 57742:11: Bye Bye [preauth]
Jun 19 06:14:15 vps-e7453ba8 sshd[17078]: Disconnected from invalid user support 167.99.194.54 port 57742 [preauth]
Jun 19 06:14:18 vps-e7453ba8 sshd[17081]: Invalid user cot from 13.79.191.179 port 35196
Jun 19 06:14:18 vps-e7453ba8 sshd[17081]: pam_unix(sshd:auth): check pass; user unknown
Jun 19 06:14:18 vps-e7453ba8 sshd[17081]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=13.79.191.179
Jun 19 06:14:21 vps-e7453ba8 sshd[17081]: Failed password for invalid user cot from 13.79.191.179 port 35196 ssh2
Jun 19 06:14:22 vps-e7453ba8 sshd[17081]: Received disconnect from 13.79.191.179 port 35196:11: Bye Bye [preauth]
Jun 19 06:14:22 vps-e7453ba8 sshd[17081]: Disconnected from invalid user cot 13.79.191.179 port 35196 [preauth]





  • Partager sur Facebook
  • Partager sur Twitter
19 juin 2020 à 14:56:37

Bon on va faire plus violent:

sudo systemctl stop mariadb
sudo rm /var/lib/mysql/ib_logfile*
sudo systemctl start mariadb



  • Partager sur Facebook
  • Partager sur Twitter
22 juin 2020 à 8:12:57

bonjour, désolé pour le délai de ma réponse..

pour la commande :

sudo rm /var/lib/mysql/ib_logfile*

j'ai un message d'erreur

rm: cannot remove '/var/lib/mysql/ib_logfile*': No such file or directory

et pour la dernière commande rien ne change du coup

Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
debian@vps-e7453ba8:~$




  • Partager sur Facebook
  • Partager sur Twitter
22 juin 2020 à 18:27:10

Bon dernier essai:

apt remove --purge mariadb-server
apt install mariadb-server



  • Partager sur Facebook
  • Partager sur Twitter
23 juin 2020 à 7:57:24

résultat de la commande

apt remove --purge mariadb-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  galera-3 libcgi-fast-perl libcgi-pm-perl libconfig-inifiles-perl
  libdbd-mysql-perl libdbi-perl libencode-locale-perl libfcgi-perl
  libhtml-parser-perl libhtml-tagset-perl libhtml-template-perl
  libhttp-date-perl libhttp-message-perl libio-html-perl liblockfile-bin
  liblockfile1 liblwp-mediatypes-perl libmariadb3 libmecab2 libnuma1
  libreadline5 libsnappy1v5 libterm-readkey-perl libtimedate-perl liburi-perl
  lockfile-progs lsof m4 mariadb-client-10.3 mariadb-client-core-10.3
  mariadb-common mariadb-server-10.3 mariadb-server-core-10.3 mecab-ipadic
  mecab-ipadic-utf8 mecab-utils mysql-common rsync sendmail-base sendmail-cf
  socat
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
  mariadb-server*
0 upgraded, 0 newly installed, 1 to remove and 22 not upgraded.
After this operation, 67.6 kB disk space will be freed.
Do you want to continue? [Y/n] Y
(Reading database ... 34933 files and directories currently installed.)
Removing mariadb-server (1:10.3.22-0+deb10u1) ...

après cela j'ai fais quelques commandes et voici le résultat..

Mysql ne veux toujours pas démarrer.. :/

root@vps-e7453ba8:/home/debian# /etc/init.d.mysql start
bash: /etc/init.d.mysql: No such file or directory
root@vps-e7453ba8:/home/debian# /etc/init.d/mysql restart
[....] Restarting mysql (via systemctl): mysql.serviceJob for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
 failed!
root@vps-e7453ba8:/home/debian# /etc/init.d/mysql stop
[ ok ] Stopping mysql (via systemctl): mysql.service.
root@vps-e7453ba8:/home/debian# /etc/init.d/mysql start
[....] Starting mysql (via systemctl): mysql.serviceJob for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
 failed!
root@vps-e7453ba8:/home/debian#



EDIT :

Bon :D

J'ai réussi en grosse partie :D

voici ce que j'ai fais pour ceux qui ont le même problème :

apt-get remove --purge mysql-server mysql-common phpmyadmin

et j'ai ensuite suivi à la lettre se tuto https://projetsdiy.fr/installer-mysql-debian-10-buster/

maintenant quand je fais la commande

sudo systemctl status mysql

elle me retourne :

● mysql.service - MySQL Community Server
   Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: en
   Active: active (running) since Tue 2020-06-23 06:06:25 UTC; 7s ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 14904 ExecStartPre=/usr/share/mysql-8.0/mysql-systemd-start pre (code
 Main PID: 14939 (mysqld)
   Status: "Server is operational"
    Tasks: 39 (limit: 2319)
   Memory: 330.1M
   CGroup: /system.slice/mysql.service
           └─14939 /usr/sbin/mysqld

Jun 23 06:06:24 vps-e7453ba8 systemd[1]: Starting MySQL Community Server...
Jun 23 06:06:25 vps-e7453ba8 systemd[1]: Started MySQL Community Server.

maintenant le soucis c'est que phpmyadmin n'arrive pas à se connecter sur le serveur mysql étant donné que j'ai cette erreur.

 mysqli_real_connect(): The server requested authentication method unknown to the client [caching_sha2_password]

du coup je pense créer un compte avec le mot de passe sans le mot de passe en sha2 afin de pouvoir me connecter sur phpmyadmin.

sauf que par contre une fois fait j'aimerais quand même pouvoir me connecter avec php avec le mot de passe en sha2..

tu as des pistes ?

merciii




-
Edité par Armored 23 juin 2020 à 8:16:49

  • Partager sur Facebook
  • Partager sur Twitter
23 juin 2020 à 16:45:38

je pose une question bête, pourquoi veux tu absolument mysql et non mariadb (sachant que tu accèdes à mariadb exactement avec les meme outils que mysql, comme par exemple phpmyadmin)?
  • Partager sur Facebook
  • Partager sur Twitter