ericr Posted May 9, 2019 Report Share Posted May 9, 2019 CLoudlinux has confirmed a kernel bug that requires a reboot of the servers to resolve that is causing unexpected high load and downtimes. We will be doing the restarts tonight after 10PM EST Quote Link to comment Share on other sites More sharing options...
SarisIsop Posted May 9, 2019 Report Share Posted May 9, 2019 Thank you for the heads up. Do you know if will we notice any downtime ? Quote Link to comment Share on other sites More sharing options...
ericr Posted May 10, 2019 Author Report Share Posted May 10, 2019 If you do it will only be for a minute or two at most. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 10, 2019 Author Report Share Posted May 10, 2019 I have started teh reboots at this time. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 10, 2019 Author Report Share Posted May 10, 2019 P2's restart suffered a unexpected issue which in the end required a second restart to resolve. I am taking a break from the restarts to settle ticket's and ensure things are stable. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 10, 2019 Author Report Share Posted May 10, 2019 Due to the unexpected issues with p2 I am going to delay further reboots till tomorrow evening to ensure there are no further unexpected issues. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 11, 2019 Author Report Share Posted May 11, 2019 I am going to be restarting the s* servers one by one. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 11, 2019 Author Report Share Posted May 11, 2019 The shared servers are done rebooting. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 11, 2019 Author Report Share Posted May 11, 2019 Starting the reboots of the R* servers. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 11, 2019 Author Report Share Posted May 11, 2019 R2 is taking longer as I am being forced to FSCK the server to address orphaned inodes. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 11, 2019 Author Report Share Posted May 11, 2019 R2 is back up and now R3 is giving the same issues. Quote Link to comment Share on other sites More sharing options...
ericr Posted May 11, 2019 Author Report Share Posted May 11, 2019 R3 is online and r4 does not a restart as it rebooted into the correct kernel with the crash a few days ago. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.