MySQL service will not stay running - Master/Slave error?

Alles, was MariaDB und MySQL betrifft, kann hier besprochen werden.

MySQL service will not stay running - Master/Slave error?

Postby kj2757 » 01. September 2020 16:03

Hello Everyone,
I am attempting to troubleshoot a problem whereby Omeka is unable to connect to the underlying database by way of XAmpp:

Omeka Database Error
No connection could be made because the target machine actively refused it.
Confirm that the information in your db.ini file is correct.

Everything is installed on a Windows 2012R2 server. Using the XAmpp Control Panel (v 3.2.4), I attempt to start the MySQL service which is off and after a few moments, the service stops by itself. Looking at mysql_error.log, I see the following error entries:

2020-08-05 15:55:07 7 [Warning] Neither --relay-log nor --relay-log-index were used; so replication may break when this MySQL server acts as a slave and has his hostname changed!! Please use '--log-basename=#' or '--relay-log=mysql-relay-bin' to avoid this problem.
2020-08-05 15:55:07 7 [ERROR] log 2020-08-05 13:27:58 7 [Note] Initialized Master_info from ''
listed in the index, but failed to stat
2020-08-05 15:55:07 7 [ERROR] Error counting relay log space
2020-08-05 15:55:07 7 [ERROR] Initialized Master_info from '' failed

I tried to overlay the following files with corresponding original ones:


and re-start the MySQL service. The service did re-start and stayed running. However errors were being generated in the log and Omeka seemed to think at that point that the database instance was brand new:

2020-08-18 11:45:10 0 [ERROR] InnoDB: Page [page id: space=0, page number=7] log sequence number 288046 is in the future! Current system log sequence number 140309.
2020-08-18 11:45:10 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 for information about forcing recovery.

So I restored the files back to the current ones and again the MySQL service would not remain running more than a few seconds:

InnoDB: using atomic writes.
2020-09-01 11:01:50 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2020-09-01 11:01:50 0 [Note] InnoDB: Uses event mutexes
2020-09-01 11:01:50 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2020-09-01 11:01:50 0 [Note] InnoDB: Number of pools: 1
2020-09-01 11:01:50 0 [Note] InnoDB: Using SSE2 crc32 instructions
2020-09-01 11:01:50 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2020-09-01 11:01:50 0 [Note] InnoDB: Completed initialization of buffer pool
2020-09-01 11:01:51 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2020-09-01 11:01:51 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2020-09-01 11:01:51 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2020-09-01 11:01:51 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2020-09-01 11:01:51 0 [Note] InnoDB: Waiting for purge to start
2020-09-01 11:01:51 0 [Note] InnoDB: 10.4.11 started; log sequence number 6880304; transaction id 19226
2020-09-01 11:01:51 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2020-09-01 11:01:51 0 [Note] Plugin 'FEEDBACK' is disabled.
2020-09-01 11:01:51 0 [Note] Server socket created on IP: '::'.

Please let me know if I need to provide more info to help with this issue. I would greatly appreciate any pointers or tips to help with getting our database back up and serving the installed Omeka instance.

Best Regards
Posts: 1
Joined: 01. September 2020 15:16
XAMPP version: 7.3.18
Operating System: Windows Server 2012R2

Return to MariaDB - MySQL

Who is online

Users browsing this forum: No registered users and 6 guests