Our team has updated the OS packages on the hypervisor and changed some
boot options that might be part of our crashes. We will be keeping an
eye on our services for a few days and making note of any possible issues
so that we can continue working with the data center to get to the bottom
of whatever is causing us to crash.
Month: May 2024
05/15 18:40EST:
We are still in communication with the data center to figure out what is
going on and are not really making any headway on the issue. For the time
being, if you are a project member and you notice that routing is suddenly
not working or that you cannot reach our game services, please reach out to
Skylar and she will fix things as quickly as she can.
—The data center techs have swapped out the memory in our server. Our team will
be keeping an eye on the server logs for the next few days and switching out
loads to see if the fault crops up again. As of now, all services should be
operational again.
—I have awakened and got out of bed for the day. A message has
been sent in to the data center about this issue. We are waiting to see what
they say and what our options are before our team does any further looking
into this.
—I will reach out to the data center once I have woke up for the
day, but it appears we are crashing once again without warning.
May 15 00:46:24 adrian kernel: microcode: Current revision: 0x08701021
May 15 00:46:24 adrian kernel: mce: [Hardware Error]: Machine check events logged
May 15 00:46:24 adrian kernel: mce: [Hardware Error]: CPU 12: Machine Check: 0 Bank 5: bea0000000000108
May 15 00:46:24 adrian kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffa3138e02 MISC d012000100000000 SYND 4d000000 IPID 500b000000000
May 15 00:46:24 adrian kernel: mce: [Hardware Error]: PROCESSOR 2:8