0
I am a Sysadmin & I don’t know much about MySQL DB. The thing is that we have an Application deployed on our windows Server 2012 Machine. What happens is that MySQL DB Service is crashing then I have to restart it manually. It’s happening at least twice a Day now.When I check Events in the Event Viewer I see below Events with EventID 1000. kindly guide me how can I resolve this issue
Below is the complete error details Faulting application name: mysqld.exe, version: 5.6.11.0, time stamp: 0x515ee7da Faulting module name: mysqld.exe, version: 5.6.11.0, time stamp: 0x515ee7da Exception code: 0xc0000005 Fault offset: 0x001f5997 Faulting process id: 0x7dc Faulting application start time: 0x01da7691f2806f13 Faulting application path: C:\Program Files (x86)\MySQL\MySQL Server 5.6\bin\mysqld.exe Faulting module path: C:\Program Files (x86)\MySQL\MySQL Server 5.6\bin\mysqld.exe Report Id: 9da9db4b-e293-11ee-8110-00155d006742 Faulting package full name: Faulting package-relative application ID:
Try to read its log file under C:\Program Files (x86)\MySQL\MySQL Server 5.6\data
I need to known what is the root cause due to which sql application crashes.
Hi,
The Windows events do not give much detail about the crash.
Have you checked the MySQL logs mentioned in that event?
That should explain more about the issue.
@yunus.uyanik Thank you so much for your response I am pasting some other useful information.
socket: '' port: 3306 MySQL Community Server (GPL)
2024-03-14 12:04:04 3276 [Note] Plugin 'FEDERATED' is disabled.
2024-03-14 12:04:04 3276 [Note] InnoDB: The InnoDB memory heap is disabled
2024-03-14 12:04:04 3276 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-03-14 12:04:04 3276 [Note] InnoDB: Compressed tables use zlib 1.2.3
2024-03-14 12:04:04 3276 [Note] InnoDB: Not using CPU crc32 instructions
2024-03-14 12:04:04 3276 [Note] InnoDB: Initializing buffer pool, size = 1.0G
2024-03-14 12:04:04 3276 [Note] InnoDB: Completed initialization of buffer pool
2024-03-14 12:04:04 3276 [Note] InnoDB: Highest supported file format is Barracuda.
2024-03-14 12:04:04 3276 [Note] InnoDB: The log sequence numbers 23829460923 and 23829460923 in ibdata files do not match the log sequence number 23920667293 in the ib_logfiles!
2024-03-14 12:04:04 3276 [Note] InnoDB: Database was not shutdown normally!
2024-03-14 12:04:04 3276 [Note] InnoDB: Starting crash recovery.
2024-03-14 12:04:04 3276 [Note] InnoDB: Reading tablespace information from the .ibd files...
2024-03-14 12:04:05 3276 [Note] InnoDB: Restoring possible half-written data pages
2024-03-14 12:04:05 3276 [Note] InnoDB: from the doublewrite buffer...
2024-03-14 12:04:06 3276 [Note] InnoDB: 128 rollback segment(s) are active.
2024-03-14 12:04:06 3276 [Note] InnoDB: Waiting for purge to start
2024-03-14 12:04:06 3276 [Note] InnoDB: 5.6.11 started; log sequence number 23920667293
2024-03-14 12:04:06 3276 [Note] Server hostname (bind-address): '*'; port: 3306
2024-03-14 12:04:06 3276 [Note] IPv6 is available.
2024-03-14 12:04:06 3276 [Note] - '::' resolves to '::';
2024-03-14 12:04:06 3276 [Note] Server socket created on IP: '::'.
2024-03-14 12:04:06 3276 [Note] Event Scheduler: Loaded 0 events
2024-03-14 12:04:06 3276 [Note] MySQL: ready for connections.
Version: '5.6.11' socket: '' port: 3306 MySQL Community Server (GPL)
SELECT COUNT(*), sum(data_length), sum(index_length), sum(data_free) FROM information_schema.tables LIMIT 100000;
Result :
"593","566850656","236166144","176590914"
As the log said, it was not shutdown normally, and the reason should be in the logs. You might go up a bit and try to look at a bit older logs then this one to find out the reason.
@yunus.uyanik
complete logs pasted above
Hi @osamamansoor
Seems you are running on Windows yes? Unfortunately Percona doesn’t provide Windows builds so our ability to troubleshoot Exceptions on Windows is limited.
This is a message that an external process to MySQL shut it down. Do you have perhaps a scheduled job or Event to restart the database?
FYI MySQL 5.6 was End of Life February 2021. You should consider upgrading at some point
I would suggest you look at adding some monitoring to the server. If you don’t have anything deployed yet may I recommend PMM as then you’ll be able to better understand the activity within the database, and perhaps from some graphs we can point you in the right direction. Perhaps we are exhausting resources on the host (not enough RAM) and then mysqld.exe aborts.
@Michael_Coburn
Thanks for your response.
Yes, This is Windows Server.
No scheduled activity to down MySql as this interruption is the main reason for our concern.
OK we will consider updating MySQL
Do you think RAM can be cause to reboot abort down of MySQL ?