Mysql Server startet nicht mehr

F

f.gruber

New Member
Hallo, nach Upgrade von openSUSE 42.3 auf 15.0 bekomme ich den MySql Server (mariadb 10.2.15) nicht mehr zum Laufen.
Code: 
Starting MySQL server...
mysql-systemd-helper[24873]: [Note] /usr/sbin/mysqld (mysqld 10.2.15-MariaDB) starting as process 24873 ...
mysql-systemd-helper[24873]: [Warning] InnoDB: Using innodb_file_format is deprecated and the parameter may be remove>
mysql-systemd-helper[24873]: [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
mysql-systemd-helper[24873]: [Note] InnoDB: Uses event mutexes
mysql-systemd-helper[24873]: [Note] InnoDB: Compressed tables use zlib 1.2.11
mysql-systemd-helper[24873]: [Note] InnoDB: Using Linux native AIO
mysql-systemd-helper[24873]: [Note] InnoDB: Number of pools: 1
mysql-systemd-helper[24873]: [Note] InnoDB: Using generic crc32 instructions
mysql-systemd-helper[24873]: [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = >
mysql-systemd-helper[24873]: [Note] InnoDB: Completed initialization of buffer pool
mysql-systemd-helper[24873]: [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority >
mysql-systemd-helper[24873]: [Note] InnoDB: Highest supported file format is Barracuda.
mysql-systemd-helper[24873]: [Note] InnoDB: 128 out of 128 rollback segments are active.
mysql-systemd-helper[24873]: [Note] InnoDB: Creating shared tablespace for temporary tables
mysql-systemd-helper[24873]: [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; >
mysql-systemd-helper[24873]: [Note] InnoDB: File './ibtmp1' size is now 12 MB.
mysql-systemd-helper[24873]: [Note] InnoDB: Waiting for purge to start
mysql-systemd-helper[24873]: [Note] InnoDB: 5.7.22 started; log sequence number 16708494671
mysql-systemd-helper[24873]: [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mysql-systemd-helper[24873]: [Note] InnoDB: Buffer pool(s) load completed at 180905  0:38:56
mysql-systemd-helper[24873]: [Note] Plugin 'FEEDBACK' is disabled.
mysql-systemd-helper[24873]: [Note] Recovering after a crash using tc.log
mysql-systemd-helper[24873]: [ERROR] Recovery failed! You must enable all engines that were enabled at the moment of >
mysql-systemd-helper[24873]: [ERROR] Crash recovery failed. Either correct the problem (if it's, for example, out of >
mysql-systemd-helper[24873]: [ERROR] Can't init tc log
mysql-systemd-helper[24873]: [ERROR] Aborting
systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
systemd[1]: Failed to start MySQL server.
systemd[1]: mariadb.service: Unit entered failed state.
systemd[1]: mariadb.service: Failed with result 'exit-code'.

Die Serverversion nach dem Upgrade ist
Code: 
mariadb 10.2.15

Bitte um Hilfe. Bin dankbar für jeden Tipp.
 
Last edited by a moderator:
... und die Version vor dem Upgrade war welche?

Generell ist es bei Versionssprüngen keine gute Idee, das Datenverzeichnis einfach 1:1 hinzuklatschen sondern man macht in der alten Version einen Dump / Export und in der neuen einen Import.
 
marce said:
... Generell ist es bei Versionssprüngen keine gute Idee, das Datenverzeichnis einfach 1:1 hinzuklatschen sondern man macht in der alten Version einen Dump / Export und in der neuen einen Import.
Click to expand...

Ja, ich hatte einen Dump.

Ich habe den MySql Server auf folgende Weise wieder zum Laufen gebracht:
  • rm /var/lib/mysql -R
  • zypper remove mariadb
  • zypper install mariadb
  • rcmysql start
  • /usr/bin/mysqladmin -u root password new-password
  • mysql -u root -p < /backupverzeichnis/mysqldump.sql
 
You must log in or register to reply here.
Back
Top