[Eisfair] [E1] MySQL 2.5.0 - Crash nach Systemupdate auf MariaDB

[Benjamin Heide]

Am 20.10.2015 um 16:26 schrieb Benjamin Heide:

Nachtrag:

das kommt davor:

Activate configuration now (y/n) [yes]?
 * Starting MariaDB/MySQL database server .........................

                                               [ FAIL ]

MariaDB/MySQL ERROR: cannot start!
 * MariaDB/MySQL Server not running

                                               [ WARN ]
 * MariaDB ERROR: Please run mariadb config
Press ENTER to continue


> Hi Leuts,
> 
> nach dem Update des kompl. Servers wurde bei der Option "A" natürlich
> auch MySQL mit geupdatet, was ja auch ok ist. Aber leider ist da ein
> Fehler aufgetreten den ich jetzt nicht weiter ergründen kann.
> 
> Auszug aus dem Logfile:
> 
> ---
> 151020 15:39:11 [Note] /usr/local/mysql/bin/mysqld: Normal heruntergefahren
> 
> 151020 15:39:11 [Note] Event Scheduler: Purging the queue. 0 events
> 151020 15:39:11  InnoDB: Starting shutdown...
> 151020 15:39:14  InnoDB: Shutdown completed; log sequence number 0 44566
> 151020 15:39:14 [Note] /usr/local/mysql/bin/mysqld: Herunterfahren beendet
> 
> 151020 15:39:15 mysqld_safe mysqld from pid file /var/run/mysql.pid ended
> 151020 15:39:39 [ERROR] Incorrect definition of table mysql.proc:
> expected column 'sql_mode' at position 14 to have type
> set('REAL_AS_FLOAT','PIPES_AS_CONCAT','ANSI_QUOTES','IGNORE_SPACE','IGNORE_BAD_TABLE_OPTIONS','ONLY_FULL_GROUP_BY','NO_UNSIGNED_SUBTRACTION','NO_DIR_IN_CREATE','POSTGRESQL','ORACLE','MSSQL','DB2','MAXDB','NO_KEY_OPTIONS','NO_TABLE_OPTIONS','NO_FIELD_OPTIONS','MYSQL323','MYSQL40','ANSI','NO_AUTO_VALUE_ON_ZERO','NO_BACKSLASH_ESCAPES','STRICT_TRANS_TABLES','STRICT_ALL_TABLES','NO_ZERO_IN_DATE','NO_ZERO_DATE','INVA
> ERROR: 1548  Cannot load from mysql.proc. The table is probably corrupted
> 151020 15:39:39 [ERROR] Aborting
> 
> 151020 15:39:39 [Note] /usr/sbin/mysqld: Shutdown complete
> 
> 151020 15:39:40 mysqld_safe Starting mysqld daemon with databases from
> /var/lib/mysql
> 151020 15:39:40 [Note] /usr/bin/mysqld (mysqld 5.5.45-MariaDB) starting
> as process 32154 ...
> 151020 15:39:40 InnoDB: The InnoDB memory heap is disabled
> 151020 15:39:40 InnoDB: Mutexes and rw_locks use GCC atomic builtins
> 151020 15:39:40 InnoDB: Compressed tables use zlib 1.2.8
> 151020 15:39:40 InnoDB: Using Linux native AIO
> 151020 15:39:40 InnoDB: Initializing buffer pool, size = 128.0M
> 151020 15:39:40 InnoDB: Completed initialization of buffer pool
> InnoDB: Error: inconsistent data in space header in data file ./ibdata1
> 151020 15:39:40 InnoDB: Could not open or create data files.
> 151020 15:39:40 InnoDB: If you tried to add new data files, and it
> failed here,
> 151020 15:39:40 InnoDB: you should now edit innodb_data_file_path in
> my.cnf back
> 151020 15:39:40 InnoDB: to what it was, and remove the new ibdata files
> InnoDB created
> 151020 15:39:40 InnoDB: in this failed attempt. InnoDB only wrote those
> files full of
> 151020 15:39:40 InnoDB: zeros, but did not yet use them in any way. But
> be careful: do not
> 151020 15:39:40 InnoDB: remove old data files which contain your
> precious data!
> 151020 15:39:40 [ERROR] Plugin 'InnoDB' init function returned error.
> 151020 15:39:40 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE
> failed.
> 151020 15:39:40 [ERROR] Unknown/unsupported storage engine: InnoDB
> 151020 15:39:40 [ERROR] Aborting
> 
> ich darf auf keinen Fall die Datenbanken verlieren.
> 
> Bitte um einen guten Tip.
> 
>