Hey @sandrodelmonte –
I’m seeing a bunch of errors that look like this:
2019-02-10T13:52:31.568742Z 0 [Note] InnoDB: Doing recovery: scanned up to log sequence number 4618136
2019-02-10T13:52:31.568928Z 0 [ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT between the checkpoint 4617569 and the end 4618136.
2019-02-10T13:52:31.569061Z 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2019-02-10T13:52:32.172803Z 0 [ERROR] Plugin 'InnoDB' init function returned error.
2019-02-10T13:52:32.173042Z 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2019-02-10T13:52:32.173184Z 0 [ERROR] Failed to initialize builtin plugins.
2019-02-10T13:52:32.173336Z 0 [ERROR] Aborting
That definitely seems like an issue with the database, possibly from some sort of issue with the site not being shutdown properly before losing power, or another event that crashed the database.
I’ve never seen that specific error message, but I Googled
[ERROR] InnoDB: Ignoring the redo log due to missing MLOG_CHECKPOINT and there were a number of pages with information about this. This StackOverflow message looks the most promising: https://dba.stackexchange.com/questions/163445/innodb-ignoring-the-redo-log-due-to-missing-mlog-checkpoint
That being said, if you do have a recent backup of the site, it might be easiest to import the backup and continue working on the site.