maria-discuss team mailing list archive
Mailing list archive
Re: Aria engine: log initialization failed
Am 05.08.2014 um 15:47 schrieb Oleksandr Byelkin:
> 02.08.2014 21:12, Reindl Harald пишет:
>> what is in "aria_log.00000001" and "aria_log_control" and can i
>> skip them from backups? as far as i see they don't contain any
>> really needed informations
> It is transaction log files, as well as some parameters (block size).
> Transaction log used in recovery, so in normal server start if there is database but no transaction files something
> went wrong and we can't check integrity.
> Probably recovery can restore the files, but normal server start have to fail on damaged files.
if they are not there they are created
i just don't understand why they are damaged by stop two mysql instances,
rsync their whole datadir and start both, see bugreport to systemd below
frankly if it would be a general problem the innodb logfiles
would also get damaged from time to time which did not happen
a single time over years
the most interesting: that machines don't use a single Aria
table so how can it be that they are at writing back while
systemctl returns and innodb is clean
still not sure if it is a systemd or MariaDB problem but currently
work around that with "ExecStopPost=/usr/bin/sleep 1" because over
months until remove that from the systemd-units no problems
>> * so can i exclude that files completly from backups
>> * could MariaDB delete them instead of refuse to start
>> in case the are damaged?
>> see my last comment on the following bugreport
>> 140802 19:35:31 [ERROR] mysqld: Aria engine: log initialization failed
>> 140802 19:35:31 [ERROR] Plugin 'Aria' init function returned error.
>> 140802 19:35:31 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
>> 140802 19:35:31 [ERROR] Aria engine is not enabled or did not start. The Aria engine must be enabled to continue as
>> mysqld was configured with --with-aria-tmp-tables
Description: OpenPGP digital signature