Mariadb auf Raspiu läuft nicht mehr

wowonk

Benutzer
Beiträge
12
Hallo,
ich hatte auf dem raspi Probleme das die SD-Karte "übergelaufen" ist.
Ich habe jetzt das System auf eine größere SD-Karte geklont, der raspi läuft, aber mariadb läuft nicht mehr.
Ich erhalte den Fehler siehe Anhang. Kann ich da als Linux-dummy noch etwas tun, z.B. Datenbankreparatur (?), oder muss ich neu installieren?Screenshot phpmyadmin.png
 
Werbung:
Keine Ahnung. Manche Programme haben die Unart, dass sie ständig ihre eigene Konfig neu schreiben. Die Meldungen riechen ein wenig so, als ob die Konfigdatei im Eimer ist (leer) oder gar nicht mehr vorhanden.
Vielleicht fehlt auch nur ein Mount..
Schwer zu sagen.

Schau mal, ob die Datei noch da ist. Wär jedenfalls ein Anfang.
 
Hallo,
unter /etc/mysql/mariadb.cnf steht:
Code:
# Import all .cnf files from configuration directory
!includedir /etc/mysql/conf.d/
!includedir /etc/mysql/mariadb.conf.d/
unter /etc/mysql/conf.d/mysql.cnf:
Code:
[mysql]
unter /etc/mysql/mariadb.conf.d/:
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]

#
# * 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

# 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

#
# * 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]

Alle Dateine haben ein Jahre altes Datum.
var/log/mysql/error.log:
Code:
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2023-06-05 16:45:13 1988370432 [Note] InnoDB: The InnoDB memory heap is disabled
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2023-06-05 16:45:13 1988370432 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Compressed tables use zlib 1.2.8
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Using Linux native AIO
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Using generic crc32 instructions
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Completed initialization of buffer pool
2023-06-05 16:45:13 1988370432 [Note] InnoDB: Highest supported file format is Barracuda.
2023-06-05 16:45:14 1988370432 [Note] InnoDB: 128 rollback segment(s) are active.
2023-06-05 16:45:14 1988370432 [Note] InnoDB: Waiting for purge to start
2023-06-05 16:45:14 1988370432 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.35-80.0 started; log sequence number 373013728
2023-06-05 16:45:14 1442837312 [Note] InnoDB: Dumping buffer pool(s) not yet started
2023-06-05 16:45:14 1988370432 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-05 16:45:14 1988370432 [Note] Recovering after a crash using tc.log
2023-06-05 16:45:14 1988370432 [ERROR] Can't init tc log
2023-06-05 16:45:14 1988370432 [ERROR] Aborting

Mir sagt das alles leider nichts.
In /etc/phpmyadmin haben auch alle Dateien eine Jahre altes Datum.
 
Werbung:
Hallo,
ich habe es jetzt mit Hilfe von anderer Seite hinbekommen. Die Datei /val/lib/mysql/tcp.log hatte 0 Byte mit Absturzdatum. Nach Löschen der Datei konnte ich mariadb wieder starten.
Gruss, wowonk
 
Zurück
Oben