ubuntuusers.de

MySQL Probleme seit Upgrade auf 25.04

Status: Ungelöst | Ubuntu-Version: Ubuntu 25.04 (Plucky Puffin)
Antworten |

Doc_Symbiosis

Avatar von Doc_Symbiosis

Anmeldungsdatum:
11. Oktober 2006

Beiträge: 4473

Wohnort: Göttingen

Hast Du denn mal versucht, das tmpdir für Mysql zu ändern?

Kommt der Fehler jetzt immernoch im Errorlog vor? Was sagt denn journalctl nach einem Neustart des Mysql-Servers?

malo66

(Themenstarter)

Anmeldungsdatum:
24. August 2011

Beiträge: 893

Ich hatte mal den # entfernt. Aber das half nichts. Ich versuche mal einen andern Pfad.

Fehlermeldung sieht jetzt folgendermaßen aus

/var/log/mysql$ cat error.log 
2025-11-17T11:00:21.303789Z 0 [System] [MY-015015] [Server] MySQL Server - start.
2025-11-17T11:00:21.552729Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.4.6-0ubuntu0.25.04.3) starting as process 33705
2025-11-17T11:00:21.563355Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started.
mysqld: Can't create/write to file '/tmp/user/0/ibHj4Qs8' (OS errno 13 - Permission denied)
2025-11-17T11:00:21.614234Z 1 [ERROR] [MY-012576] [InnoDB] Unable to create temporary file inside "/tmp/user/0"; errno: 13
2025-11-17T11:00:21.614271Z 1 [ERROR] [MY-012930] [InnoDB] Plugin initialization aborted with error Generic error.
2025-11-17T11:00:21.614303Z 1 [ERROR] [MY-010334] [Server] Failed to initialize DD Storage Engine
2025-11-17T11:00:21.614570Z 0 [ERROR] [MY-010020] [Server] Data Dictionary initialization failed.
2025-11-17T11:00:21.614627Z 0 [ERROR] [MY-010119] [Server] Aborting
2025-11-17T11:00:21.617288Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.4.6-0ubuntu0.25.04.3)  (Ubuntu).
2025-11-17T11:00:21.617313Z 0 [System] [MY-015016] [Server] MySQL Server - end.

Sorry, du meintest ja journalctl

journalctl | grep mysql
Nov 17 15:51:24 marcx apparmor.systemd[1241]: AppArmor-Analysefehler f?r /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.mysqld in Zeile 83: >>local/usr.sbin.mysqld<< konnte nicht ge?ffnet werden
Nov 17 15:51:25 marcx apparmor.systemd[1816]: AppArmor-Analysefehler f?r /etc/apparmor.d in profile /etc/apparmor.d/usr.sbin.mysqld in Zeile 83: >>local/usr.sbin.mysqld<< konnte nicht ge?ffnet werden
Nov 17 19:21:32 marcx sudo[12009]:     marc : TTY=pts/0 ; PWD=/var/log/mysql ; USER=root ; COMMAND=/usr/sbin/service mysql restart
Nov 17 19:21:32 marcx systemd[1]: Starting mysql.service - MySQL Community Server...
Nov 17 19:21:35 marcx systemd[1]: Started mysql.service - MySQL Community Server.

Doc_Symbiosis

Avatar von Doc_Symbiosis

Anmeldungsdatum:
11. Oktober 2006

Beiträge: 4473

Wohnort: Göttingen

Kannst Du mal etwas mehr Infos liefern: Wo in welcher Datei hast Du das '#' entfernt? Hast Du danach das mysql neu gestartet?

malo66

(Themenstarter)

Anmeldungsdatum:
24. August 2011

Beiträge: 893

Ich hatte aus der mysql.cnf

# tmpdir		= /tmp

die Raute entfernt.

und mysql neu gestartet. Hatte jedoch nichts geändert.

vergrößern

/etc/mysql/mysql.conf.d$ cat mysql.cnf
#
# The MySQL database client configuration file
#
# Ref to https://dev.mysql.com/doc/refman/en/mysql-command-options.html

[mysql]
marc@marcx:/etc/mysql/mysql.conf.d$ cat mysqld.cnf
#
# The MySQL database server configuration file.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

[mysqld]
#
# * Basic Settings
#
user		= mysql
# pid-file	= /var/run/mysqld/mysqld.pid
# socket	= /var/run/mysqld/mysqld.sock
# port		= 3306
# datadir	= /var/lib/mysql


# If MySQL is running as a replication slave, this should be
# changed. Ref https://dev.mysql.com/doc/refman/8.4/en/server-system-variables.html#sysvar_tmpdir
# tmpdir		= /tmp
#
# 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
mysqlx-bind-address	= 127.0.0.1
#
# * Fine Tuning
#
key_buffer_size		= 16M
# max_allowed_packet	= 64M
# thread_stack		= 256K

# thread_cache_size       = -1

# This replaces the startup script and checks MyISAM tables if needed
# the first time they are touched
myisam-recover-options  = BACKUP

# max_connections        = 151

# table_open_cache       = 4000

#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
#
# Log all queries
# Be aware that this log type is a performance killer.
# general_log_file        = /var/log/mysql/query.log
# general_log             = 1
#
# Error log - should be very few entries.
#
log_error = /var/log/mysql/error.log
#
# Here you can see queries with especially long duration
# slow_query_log		= 1
# slow_query_log_file	= /var/log/mysql/mysql-slow.log
# long_query_time = 2
# 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
# binlog_expire_logs_seconds	= 2592000
max_binlog_size   = 100M
# binlog_do_db		= include_database_name
# binlog_ignore_db	= include_database_name
Antworten |