Hello, i have a problem with old installation of ispconfig. After a server restart, mariadb won't to start. This is the output of journalctl -xe Code: août 26 04:49:41 ns3066859 systemd[1]: Starting MariaDB 10.1.48 database server... -- Subject: L'unité (unit) mariadb.service a commencé à démarrer -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- L'unité (unit) mariadb.service a commencé à démarrer. août 26 04:49:41 ns3066859 mysqld[20399]: 2022-08-26 4:49:41 140205134912896 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB-0+deb9u2) starting as process 20399 ... août 26 04:49:44 ns3066859 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE août 26 04:49:44 ns3066859 systemd[1]: Failed to start MariaDB 10.1.48 database server. -- Subject: L'unité (unit) mariadb.service a échoué -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- L'unité (unit) mariadb.service a échoué, avec le résultat failed. août 26 04:49:44 ns3066859 systemd[1]: mariadb.service: Unit entered failed state. août 26 04:49:44 ns3066859 systemd[1]: mariadb.service: Failed with result 'exit-code'. this is 50-client-cnf Code: # # This group is read by the client library # Use it for options that affect all clients, but not the server # [client] # Default is Latin1, if you need UTF-8 set this (also in server section) default-character-set = utf8mb4 # Example of client certificate usage # ssl-cert=/etc/mysql/client-cert.pem # ssl-key=/etc/mysql/client-key.pem # # Allow only TLS encrypted connections # ssl-verify-server-cert=on # This group is *never* read by mysql client library, though this # /etc/mysql/mariadb.cnf.d/client.cnf file is not read by Oracle MySQL # client anyway. # If you use the same .cnf file for MySQL and MariaDB, # use it for MariaDB-only client options [client-mariadb] this 50-mysql-clients.cnf Code: # # These groups are read by MariaDB command-line tools # Use it for options that affect only one utility # [mysql] # Default is Latin1, if you need UTF-8 set this (also in server section) default-character-set = utf8mb4 [mysql_upgrade] [mysqladmin] [mysqlbinlog] [mysqlcheck] [mysqldump] [mysqlimport] [mysqlshow] [mysqlslap] this Code: # NOTE: This file is read only by the traditional SysV init script, not systemd. # MariaDB systemd does _not_ utilize mysqld_safe nor read this file. # # For similar behaviour, systemd users should create the following file: # /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf # # To achieve the same result as the default 50-mysqld_safe.cnf, please create # /etc/systemd/system/mariadb.service.d/migrated-from-my.cnf-settings.conf # with the following contents: # # [Service] # User=mysql # StandardOutput=syslog # StandardError=syslog # SyslogFacility=daemon # SyslogLevel=err # SyslogIdentifier=mysqld # # For more information, please read https://mariadb.com/kb/en/mariadb/systemd/ # [mysqld_safe] # This will be passed to all mysql clients # It has been reported that passwords should be enclosed with ticks/quotes # especially if they contain "#" chars... # Remember to edit /etc/mysql/debian.cnf when changing the socket location. socket = /var/run/mysqld/mysqld.sock nice = 0 skip_log_error syslog this 50-server.cnf Code: # # These groups are read by MariaDB server. # Use it for options that only the server (but not clients) should see # # See the examples of server my.cnf files in /usr/share/mysql/ # # this is read by the standalone daemon and embedded servers [server] # this is only for the mysqld standalone daemon [mysqld] # Replication settings server-id = 1 replicate-same-server-id = 0 auto-increment-increment = 2 auto-increment-offset = 1 log-bin = mysql-bin.log expire_logs_days = 10 max_binlog_size = 100M binlog_format = mixed sync_binlog = 1 relay-log = slave-relay.log relay-log-index = slave-relay-log.index slave_skip_errors = 1007,1008,1050,1396 bind-address = :: # # * Basic Settings # user = mysql pid-file = /var/run/mysqld/mysqld.pid socket = /var/run/mysqld/mysqld.sock port = 3306 basedir = /usr datadir = /var/lib/mysql tmpdir = /tmp lc-messages-dir = /usr/share/mysql skip-external-locking log-error=/var/log/mysql/mysql.err log-bin=/var/log/mysql/mysql-replication.log # Instead of skip-networking the default is now to listen only on # localhost which is more compatible and is not less secure. # bind-address = 127.0.0.1 sql-mode="NO_ENGINE_SUBSTITUTION" # # * Fine Tuning # key_buffer_size = 16M max_allowed_packet = 16M thread_stack = 192K thread_cache_size = 8 # This replaces the startup script and checks MyISAM tables if needed # the first time they are touched myisam_recover_options = BACKUP #max_connections = 100 #table_cache = 64 #thread_concurrency = 10 # # * Query Cache Configuration # query_cache_limit = 1M query_cache_size = 16M # # * Logging and Replication # # Both location gets rotated by the cronjob. # Be aware that this log type is a performance killer. # As of 5.1 you can enable the log at runtime! #general_log_file = /var/log/mysql/mysql.log #general_log = 1 # # Error log - should be very few entries. # log_error = /var/log/mysql/error.log # # Enable the slow query log to see queries with especially long duration #slow_query_log_file = /var/log/mysql/mariadb-slow.log #long_query_time = 10 #log_slow_rate_limit = 1000 #log_slow_verbosity = query_plan #log-queries-not-using-indexes # # The following can be used as easy to replay backup logs or for replication. # note: if you are setting up a replication slave, see README.Debian about # other settings you may need to change. #server-id = 1 #log_bin = /var/log/mysql/mysql-bin.log #expire_logs_days = 10 #max_binlog_size = 100M #binlog_do_db = include_database_name #binlog_ignore_db = exclude_database_name # # * InnoDB # # InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/. # Read the manual for more InnoDB related options. There are many! # # * Security Features # # Read the manual, too, if you want chroot! # chroot = /var/lib/mysql/ # # For generating SSL certificates you can use for example the GUI tool "tinyca". # # ssl-ca=/etc/mysql/cacert.pem # ssl-cert=/etc/mysql/server-cert.pem # ssl-key=/etc/mysql/server-key.pem # # Accept only connections using the latest and most secure TLS protocol version. # ..when MariaDB is compiled with OpenSSL: # ssl-cipher=TLSv1.2 # ..when MariaDB is compiled with YaSSL (default in Debian): # ssl=on # # * Character sets # # MySQL/MariaDB default is Latin1, but in Debian we rather default to the full # utf8 4-byte character set. See also client.cnf # character-set-server = utf8mb4 collation-server = utf8mb4_general_ci # # * Unix socket authentication plugin is built-in since 10.0.22-6 # # Needed so the root database user can authenticate without a password but # only when running as the unix root user. # # Also available for other users if required. # See https://mariadb.com/kb/en/unix_socket-authentication-plugin/ # this is only for embedded server [embedded] # This group is only read by MariaDB servers, not by MySQL. # If you use the same .cnf file for MySQL and MariaDB, # you can put MariaDB-only options here [mariadb] # This group is only read by MariaDB-10.1 servers. # If you use the same .cnf file for MariaDB of different versions, # use this group for options that older servers don't understand [mariadb-10.1]
the result of systemctl status mariadb.service Code: ● mariadb.service - MariaDB 10.1.48 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/mysql.service.d └─limits.conf Active: failed (Result: exit-code) since Fri 2022-08-26 05:20:41 UTC; 8s ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 25119 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 25003 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$V Process: 25000 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 24997 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 25119 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" And i test to reinstall mariadb-server package but i have a problem : it's impossible to reinstall or desinstall Code: dpkg: erreur de traitement du paquet mariadb-server-10.1 (--configure) : le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1 Des erreurs ont été rencontrées pendant l'exécution : mariadb-server-10.1 E: Sub-process /usr/bin/dpkg returned an error code (1)
Start with this: https://forum.howtoforge.com/threads/please-read-before-posting.58408/ Those command results you post would be better in english, so use LANG=C at the beginning of the command line. Like so: Code: LANG=C journalctl -xe What happens if you try to start mariadb now? Use Code: LANG=C systemctl start mariadb
Thanks for reply The result in english Code: Subject: Unit mariadb.service has begun star -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit mariadb.service has begun starting up. Aug 26 09:59:03 ns3066859 mysqld[2413]: 2022-08 Aug 26 09:59:06 ns3066859 systemd[1]: mariadb.s Aug 26 09:59:06 ns3066859 systemd[1]: Failed to -- Subject: Unit mariadb.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit mariadb.service has failed. -- -- The result is failed.
Sorry, i haven't got my labtop, this is the error : Code: Aug 29 05:31:25 ns3066859 systemd[1]: Starting MariaDB 10.1.48 database server... -- Subject: Unit mariadb.service has begun start-up -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit mariadb.service has begun starting up. Aug 29 05:31:26 ns3066859 mysqld[25238]: 2022-08-29 5:31:26 139712251329920 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB-0+deb9u2) starting as process 25238 ... Aug 29 05:31:29 ns3066859 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Aug 29 05:31:29 ns3066859 systemd[1]: Failed to start MariaDB 10.1.48 database server. -- Subject: Unit mariadb.service has failed -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- Unit mariadb.service has failed. -- -- The result is failed. Aug 29 05:31:29 ns3066859 systemd[1]: mariadb.service: Unit entered failed state. Aug 29 05:31:29 ns3066859 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Troubleshoot further: Code: LANG=C systemctl status mariadb.service What is in log file /var/log/mysql/error.log ? Examine other log files for clues.
Code: root@ns3066859:~# LANG=C systemctl status mariadb.service * mariadb.service - MariaDB 10.1.48 database server Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled) Drop-In: /etc/systemd/system/mysql.service.d `-limits.conf Active: failed (Result: exit-code) since Mon 2022-08-29 05:31:29 UTC; 5h 14min ago Docs: man:mysqld(8) https://mariadb.com/kb/en/library/systemd/ Process: 25238 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE) Process: 25121 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$V Process: 25118 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS) Process: 25116 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS) Main PID: 25238 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" Aug 29 05:31:25 ns3066859 systemd[1]: Starting MariaDB 10.1.48 database server... Aug 29 05:31:26 ns3066859 mysqld[25238]: 2022-08-29 5:31:26 139712251329920 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB-0+deb9u2) starting as process 25238 ... Aug 29 05:31:29 ns3066859 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Aug 29 05:31:29 ns3066859 systemd[1]: Failed to start MariaDB 10.1.48 database server. Aug 29 05:31:29 ns3066859 systemd[1]: mariadb.service: Unit entered failed state. Aug 29 05:31:29 ns3066859 systemd[1]: mariadb.service: Failed with result 'exit-code'.
/var/log/mysql/error.log Code: 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up$ 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: The InnoDB memory heap is disabled 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Compressed tables use zlib 1.2.8 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Using Linux native AIO 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Using generic crc32 instructions 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2022-08-29 5:30:49 140077384158592 [Note] InnoDB: Completed initialization of buffer pool 2022-08-29 5:30:50 140077384158592 [Note] InnoDB: Highest supported file format is Barracuda. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 7 log sequence number 160201060595 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 2 log sequence number 160201032651 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 4 log sequence number 160200949133 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 11 log sequence number 153860080732 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 1 log sequence number 20876452101 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 6 log sequence number 160200958261 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 531 log sequence number 160200996458 InnoDB: is in the future! Current system log sequence number 7049838764. InnoDB: Your database may be corrupt or you may have copied the InnoDB InnoDB: tablespace but not the InnoDB log files. See InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html InnoDB: for more information. 2022-08-29 05:30:50 7f664eb94d80 InnoDB: Error: page 381 log sequence number 160200958261 InnoDB: is in the future! Current system log sequence number 7049838764. /var/log/syslog Code: Aug 29 10:58:22 ns3066859 systemd[1]: Starting MariaDB 10.1.48 database server... Aug 29 10:58:22 ns3066859 mysqld[9808]: 2022-08-29 10:58:22 139736172473728 [Note] /usr/sbin/mysqld (mysqld 10.1.48-MariaDB-0+deb9u2) starting as process 9808 ... Aug 29 10:58:25 ns3066859 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE Aug 29 10:58:25 ns3066859 systemd[1]: Failed to start MariaDB 10.1.48 database server. Aug 29 10:58:25 ns3066859 systemd[1]: mariadb.service: Unit entered failed state. Aug 29 10:58:25 ns3066859 systemd[1]: mariadb.service: Failed with result 'exit-code'.
Seems as if your InnoDB database is corrupted. the error messages in the log contain a link with instructions on how to proceed.
So it's okay, I restart with the option mysqld --tc-heuristic-recover=ROLLBACK and the database restart well Thanks all for your help !
