V
vincentwansink
I have a website on two servers (Windows Server 2016 and Windows Server 2012). On the 2016 server mysql is crashing every 30 minutes. In trying to track down what could be causing it I noticed that "Windows Insider Service" enters a running state right before mysql crashes every time.
The weird thing is that the Windows Insider Service is set to a Manual Startup Type so I don't understand why it's starting up every 30 minutes, yet this is what I see in my event log right before every mysql crash.
"The Windows Insider Service service entered the running state." Event ID 7036
And when I say "right before" I mean at the exact same second, but listed just before the mysql crash in the event log. I'm assuming that means it happened a fraction of a second before the mysql crash.
Thankfully I'm running ipSentry on my server which automatically detects the mysql crash and restarts it right away. So mysql is automatically restarted and then approximately 55 seconds after mysql enters the running state, the Windows Insider Service enters the stopped state (or at least that's when it's recording in Windows event log).
And exactly 30 minutes after mysql enters the running state, the Windows Insider Service also enters the running state, causing mysql to crash again.
Also, mysql is not crashing on my 2012 Server, presumably because there is no Windows Insider Service on that version of the operating system, so I'm pretty sure this is what's causing mysql to crash.
To confirm my suspicions I want to obviously prevent this service from starting. My question is, how can I find out what's causing it to start, and if I can't find that out, then is there a way to make sure it doesn't start?
UPDATE: I noticed that the Windows Error Reporting Service is also starting up at the exact same second that the Windows Insider Service is starting (yet listed ahead of the Insider Service), and that service is triggered to restart automatically after 2 minutes when it fails. I also noticed that exactly 1 minute after the Windows Insider Service enters the stopped state, so does the Windows Error Reporting Service.
So this seems to be the process:
These are the settings for Windows Error Reporting Service.
So obviously I don't see anywhere in these settings that would cause the Windows Error Reporting service to stop after 2 minutes, and I also don't see any setting that would cause it to restart exactly 30 minutes after MySQL starts. I also don't understand why these two services (Error Reporting & Insider Service) seem to be joined at the hip.
My main goal here is to stop MySQL from crashing. I'm only bringing up these services because they seem to be the cause and I don't understand why they're doing what they're doing so I'm not sure how to stop it.
Continue reading...
The weird thing is that the Windows Insider Service is set to a Manual Startup Type so I don't understand why it's starting up every 30 minutes, yet this is what I see in my event log right before every mysql crash.
"The Windows Insider Service service entered the running state." Event ID 7036
And when I say "right before" I mean at the exact same second, but listed just before the mysql crash in the event log. I'm assuming that means it happened a fraction of a second before the mysql crash.
Thankfully I'm running ipSentry on my server which automatically detects the mysql crash and restarts it right away. So mysql is automatically restarted and then approximately 55 seconds after mysql enters the running state, the Windows Insider Service enters the stopped state (or at least that's when it's recording in Windows event log).
And exactly 30 minutes after mysql enters the running state, the Windows Insider Service also enters the running state, causing mysql to crash again.
Also, mysql is not crashing on my 2012 Server, presumably because there is no Windows Insider Service on that version of the operating system, so I'm pretty sure this is what's causing mysql to crash.
To confirm my suspicions I want to obviously prevent this service from starting. My question is, how can I find out what's causing it to start, and if I can't find that out, then is there a way to make sure it doesn't start?
UPDATE: I noticed that the Windows Error Reporting Service is also starting up at the exact same second that the Windows Insider Service is starting (yet listed ahead of the Insider Service), and that service is triggered to restart automatically after 2 minutes when it fails. I also noticed that exactly 1 minute after the Windows Insider Service enters the stopped state, so does the Windows Error Reporting Service.
So this seems to be the process:
- Windows Error Reporting Service starts
- Windows Insider Service starts
- MySQL service stops (Steps 1 to 3 all happen in the same second but in this order)
- ipSentry automatically restarts MySQL
- Exactly 1 minute after Windows Insider Service started, it stops
- Exactly 2 minutes after Windows Error Reporting started, it stops
- Exactly 30 minutes after MySQL starts the entire cycle begins again
These are the settings for Windows Error Reporting Service.
So obviously I don't see anywhere in these settings that would cause the Windows Error Reporting service to stop after 2 minutes, and I also don't see any setting that would cause it to restart exactly 30 minutes after MySQL starts. I also don't understand why these two services (Error Reporting & Insider Service) seem to be joined at the hip.
My main goal here is to stop MySQL from crashing. I'm only bringing up these services because they seem to be the cause and I don't understand why they're doing what they're doing so I'm not sure how to stop it.
Continue reading...