John C Posted July 30, 2019 Posted July 30, 2019 Got this error message in service manager, closed it down and now the instance itself will not load for any og us, please investigate ASAP
Steve Giller Posted July 30, 2019 Posted July 30, 2019 I'll post back when I have the official diagnosis
Steve Giller Posted July 30, 2019 Posted July 30, 2019 At 12:11 on Tuesday 30th July we detected the loss of one of our nodes. The root cause was identified as a Blue Screen of Death and resolved by a restart of node and all services. All instances were recovered by 12:15. The operating systems should not fail in this way, the BSOD reports a driver IRQ conflict which given its a virtual machine and not subject to hardware changes is virtually impossible. Unfortunately, we have been unable to identify a solution/patch from Microsoft thus far. As with any failure of this nature, when it is out of our hands, we always develop a strategy to prevent future problems. To this end, we are now doing the following. Long-Term - Remove windows from our server stack We have already begun the process of moving our application code from Windows to Linux; Windows has been less reliable and more difficult to work within our stack, so we are keen to remove this. This change will be transparent to customers. This migration to Linux will not only significantly increase stability, but is also part of a larger strategic development to an even more flexible microservices architecture.
John C Posted July 30, 2019 Author Posted July 30, 2019 @Steve Giller, that's great Steve, thanks for the prompt response and solution, much appreciated.. Regards,
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now