InnoDB/mariaDB errors

Support
#1

Situation
I’m running windows 11, latest openemr version

So - this has been a long, difficult road. Trying to get this new version of openemr working and my first attempt a while ago involved trying to import data from her very old version. Eventually that stopped working due to InnoDB/MariaDB errors, so I assumed it was from trying to move the data over

However, this is a virgin copy of everything - xampp, mysql, openemr - and it’s happened again. I think it’s possible it’s because i was a little late to make the xampp running as administrator(? - is that possibly why I’m getting the errors below?)

I can start all over again (again) with a virgin copy of everything (and this time make sure xampp is running as administrator to start, assuming that is the problem), but I have already put in some data, so i’d prefer not to do that. And it would be great if i can just rectify this problem and keep the data. Plus would be great to know it won’t happen yet again

Here’s the beginning of the mysql log - again any ideas are appreciated

2024-03-29 12:00:35 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 2704
2024-03-29 12:00:35 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-03-29 12:00:35 0 [Note] InnoDB: Uses event mutexes
2024-03-29 12:00:35 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-03-29 12:00:35 0 [Note] InnoDB: Number of pools: 1
2024-03-29 12:00:35 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-03-29 12:00:35 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-03-29 12:00:35 0 [Note] InnoDB: Completed initialization of buffer pool
2024-03-29 12:00:35 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 6444468 is in the future! Current system log sequence number 141342.
2024-03-29 12:00:35 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-03-29 12:00:35 0 [ERROR] InnoDB: Page [page id: space=0, page number=3] log sequence number 136422225 is in the future! Current system log sequence number 141342.
2024-03-29 12:00:35 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.
2024-03-29 12:00:35 0 [ERROR] InnoDB: Page [page id: space=0, page number=2] log sequence number 193752645 is in the future! Current system log sequence number 141342.

OpenEMR Version
I’m using OpenEMR version

Browser:
I’m using:

Operating System
I’m using:

Search
Did you search the forum for similar questions?

Logs
Did you check the logs?
Was there anything pertinent in them?
Please paste them here (surround with three backticks (```) for readability.
You can also turn on User Debugging under Administration->Globals->Logging User Debugging Options=>All

#2

What do you mean by ‘importing’ data. Are you copying over the MySQL data files, are you doing an import using a SQL export file, are you using phpmyadmin. We need more information on what you are doing before you’ll get much help.

From the looks of it you are copying over the raw MySQL files in the data tables and have not copied everything over. That’s what this error message means:

Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files.```
1 Like
#3

Thanks for response

Just to clarify-

The first time i tried to install this newer version of openemr I was trying to bring the data from the old openemr- I used insert queries and tried to bring as much data over as I could. That is what I mean by “import”

But eventually I got some sort of MySQL error- maybe not this one exactly. And as a result I gave up on that install attempt, and I presumed it occurred because I hadn’t moved the data over properly

But this time, I tried a virgin install and figured we’d manually enter the small amount of data we needed from before- it’s a small practice and she doesn’t need historical records at all

So: in the last few days I installed from scratch and after a few reboots (without xampp running as administrator) it seemed to run into this problem, with some sort of innodb/mariaDB error (possibly not exactly this)

Somewhere I read the recommendation to remove some log files, and I did and now I am getting this error

As far as I know, the only possible mistake I made in the installation was not setting xampp to run as administrator from the very beginning. Do you think it’s possible that this caused this problem?

And secondly, is there a way to rescue this installation? I see that in theory I can save the data with a setting in the mariaDB configuration file, but if there is a way to reset it more easily that would be nice

Thanks!

#4

Removing the MySQL innodb log files corrupts the MySQL database and creates the error you are running into. Did you create a backup before you removed the log files? You can read more on the recovery process of a MySQL database here: https://dev.mysql.com/doc/refman/8.3/en/innodb-recovery.html

OpenEMR actually has a database upgrade process. If you have a complete database export (from mysqldump or phpmyadmin) you should be able to import it into a fresh mysql database running openemr and run the OpenEMR sql_upgrade.php process to upgrade your OpenEMR data up to the version you need. Was there a specific table that was failing when you attempted this process?

What version of OpenEMR were you originally running on? Is that system still running or is it shut down?

If I remember correctly, some of the views require you to run XAMPP as a database adminstrator but that shouldn’t have caused you errors on the import process as the older versions of OpenEMR wouldn’t have those. It depends on what version of OpenEMR your source machine is running on.

1 Like
#5

Thanks again for your help

The original version was quite old: 4.2.0. Will I really be able to bring the data in? Somehow I got the impression it was too old for that. At any rate I either didn’t try or did try and it didn’t work

I still do have access to the old installation, and actually did export everything already, but if there is a chance of being able to import the data into the new version I guess I’d do it again since it’s been in use during this ‘transition’

Btw, the original error I got (before removing any log files) was this, below. I’m nervous that even a completely virgin install caused this problem, and after I go through the hassle of bringing data in, I really don’t want to see this error come up a 3rd time, since we seem not to know what’s causing it

==

2024-03-29 11:33:54 0 [Note] Starting MariaDB 10.4.32-MariaDB source revision c4143f909528e3fab0677a28631d10389354c491 as process 20220
2024-03-29 11:33:54 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-03-29 11:33:54 0 [Note] InnoDB: Uses event mutexes
2024-03-29 11:33:54 0 [Note] InnoDB: Compressed tables use zlib 1.3
2024-03-29 11:33:54 0 [Note] InnoDB: Number of pools: 1
2024-03-29 11:33:54 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-03-29 11:33:54 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2024-03-29 11:33:54 0 [Note] InnoDB: Completed initialization of buffer pool
2024-03-29 11:33:54 0 [ERROR] InnoDB: Missing MLOG_CHECKPOINT at 194287752 between the checkpoint 194287752 and the end 194287616.
2024-03-29 11:33:54 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2024-03-29 11:33:54 0 [Note] InnoDB: Starting shutdown…
2024-03-29 11:33:54 0 [ERROR] Plugin ‘InnoDB’ registration as a STORAGE ENGINE failed.
2024-03-29 11:33:54 0 [Note] Plugin ‘FEEDBACK’ is disabled.
2024-03-29 11:33:54 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2024-03-29 11:33:54 0 [ERROR] Aborting

#6

hi @leongruenbaum , try out the windows upgrade process, should be what you need, the instructions mention 7.0.1 but it can be any prior version :slight_smile: there are a couple of folders that have been consolidated into the documents directory

#7

Ok good to know

I still wish I had some confidence that I won’t get this weird MySQL error again , since it happened twice, once even without my moving data into openemr

#8

Just to follow-up - I did change the xampp control panel to run as administrator right from the beginning of the install, and I’ve now rebooted a few times and it seems still to be working. I guess I need to keep restarting it to know for sure, but it’s possible that is a factor after all.

Now that I’m able to keep it running… I’ve posted a separate issue regarding x12 and insurance not filling in in “billing manager”