# Discourse stopping working - CPU/RAM load? **URL:** \ **Category:** Product Support\ **Created:** [7 בספטמבר,‏ 2019,‏ 2:35pm UTC](https://meta.discourse.org/t/discourse-stopping-working-cpu-ram-load/127889 "2019-09-07T14:35:53Z")\ **Posts on this page:** 1\ **Showing post:** 1
**Author:** ![Yetidragon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/yetidragon/32/155539_2.png) [@Yetidragon](https://meta.discourse.org/u/Yetidragon)\ **Post date:** [7 בספטמבר,‏ 2019,‏ 2:35pm UTC](https://meta.discourse.org/t/discourse-stopping-working-cpu-ram-load/127889/1 "2019-09-07T14:35:53Z")
Hi all. Hoping that someone will be able to help me resolve an issue that we are currently having on our forum :- [https://forum.combustionpunks.co.uk](https://forum.combustionpunks.co.uk) This is a long story… but I want to give all info that may help resolve the issue, so please bear with me. Over the course of this you will notice that I do not have much experience with Ubuntu ☹ Everything has been working swimmingly for quite sometime now 😃 right up until yesterday evening. We are having a little rebrand, updated logos and that sort of thing, so yesterday I was in the admin panel uploading the new logos. I also noticed that we were a few versions behind so I run the updates, had to perform it manually following the instructions here:- > [@Manually update Discourse and Docker image to latest](https://meta.discourse.org/t/how-do-i-manually-update-discourse-and-docker-image-to-latest/23325): > > bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa… eg cd /var/discourse git pull ./launcher rebuild app everything seemed to go fine, updates completed, logos uploaded and displaying, tried a few themes, went back to the original, then popped out to a social engagement related to the forum… yeah, I went to the pub for a meal with my mates. about 30 mins later while out, we noticed the forum was offline… small bit of panic, then notice that Digital Ocean having issues, so relaxed. Came back about 2 hours later, DO issues resolved, but forum still offline… no worries, I restarted the droplet, all came back on fine… 30 mins or so later it was offline again… next I thought it would be best to clear any other updates outstanding, so tried to update docker with wget -qO- [https://get.docker.com/](https://get.docker.com/) | sh this didnt seem to do much. Rebuilt app ./launcher rebuild app I dont believe it has updated as when rebuilding app it is saying docker version 17.05.0-ce depreciated and when running docker version it is reporting 17.05.0-ce then noticed that just before forum was going off line we were getting messages along lines of:- Out of memory: kill process (convert) or sacrifice child Out of memory: kill process (ruby) or sacrifice child Ran Htop lots of instances of sidekiq , found a post about reducing amount of threads rebaked at a time - reduced from 80 to 2 - issues continued instances of convert running against JPEGs in var/www/discourse/public/uploads/default/original/ (dont know how to sdisplay rest of the string to see which images these are running against) CPU usage 100% - Ruby var/www/discourse/vendor/buundle/ruby/2.6.0/bin/unicorn -E Updated OS - now running Ubuntu 18.04 Docker still on 17.05.0-ce. Droplet resized from the 2GB 1vCPU 50GB ($10) to the 3GB 1vCPU 50GB ($15) issues continuing. Restarting the droplet or rebuilding discourse gets it back up and running for a short period (10 - 30 mins) before it goes offline again. Any help with this would be very much appriciated, many thanks in advance Matt --- _[View the full topic](https://meta.discourse.org/t/discourse-stopping-working-cpu-ram-load/127889)._