Michael D. Posted October 27, 2019 Report Share Posted October 27, 2019 At 11:02 AM ET on Sat October 26, 2019 the S3 server exhausted all of its physical RAM resulting in an outage. Before bringing the server back online we applied an additional 30GB of ram to the system bringing it up to a total of 120GB. At 7:53 PM ET on Sat October 26, 2019 the S3 server once again experienced a brief outage. We presently believe the issue to be with CloudLinux and it not properly applying RAM limits to all accounts. A ticket has been opened with CloudLinux and we are watching the server closely. Quote Link to comment Share on other sites More sharing options...
Michael D. Posted October 27, 2019 Author Report Share Posted October 27, 2019 It looks like OOM Killer [out of memory killer] was going wild over a few accounts - and the amount it was running was causing system wide issues. The system itself didn't exhaust RAM, but the user-level issues did cause some problems. We adjusted some system settings as per CloudLinux's advice and we believe this issue should not recur. We are going to continue watching the server closely regardless. The changes recommended by CloudLinux have been applied to all servers. 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.