Jump to content
matkordell

LabTech MySQL Server Crashes Every Few Weeks

Recommended Posts

Hi,

 

My depth of MySQL knowledge is fairly shallow. Hoping someone might be able to help with next steps as multiple tickets with LT Support have not been fruitful.

 

Issue is that the LabTech MySQL Server service crashes every few weeks, seemingly at random, which leaves the application non-functional.

 

Sometimes a restart of the service is all it takes to recover. Sometimes it will continue to fail after 5-10 minutes of the service being restarted, at which point it requires a reboot to bring the server back to stable.

 

In the windows event logs I see:

Faulting module name: mysqld.exe, version: 5.5.31.0, time stamp: 0x51505171

Exception code: 0x80000003

Fault offset: 0x000000000021ba32

Faulting process id: 0x2ae0

Faulting application start time: 0x01d1b50ff0f82216

Faulting application path: C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe

Faulting module path: C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld.exe

Report Id: 943b33d8-27b5-11e6-a705-000c29226cea

 

Some searching on various aspects of the event log lead me to the servername.err log, in which I found:

Version: '5.5.31' socket: '' port: 3306 MySQL Community Server (GPL)

160531 21:59:09 InnoDB: Operating system error number 2 in a file operation.

InnoDB: Some operating system error numbers are described at

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/operating-system-error-codes.html

InnoDB: File name C:\Windows\TEMP\#sql2ae0_4037_ee.ibd

InnoDB: File operation call: 'open'.

160531 21:59:09 InnoDB: Assertion failure in thread 12224 in file fil0fil.c line 834

InnoDB: Failing assertion: ret

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

 

Any ideas on next steps?

Share this post


Link to post
Share on other sites

If you still have support / pay monthly for Labtech, I'd advise calling support, rather than chancing a break of mysql.

Share this post


Link to post
Share on other sites

Yeah, looks like I forgot to mention, many tickets open with LT, not a lot of luck on an actual fix. I do have a ticket open with them as well.

Share this post


Link to post
Share on other sites

I should follow up on this. I called LT support and pushed them on a fix. Ended up being DB corruption that they worked on immediately for about 6 hours and and I have not had an issue since (though it's not uncommon for us to go weeks without issue).

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×