# Update has stuck, what shall I do?
**URL:** https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866
**Category:** Self-hosting
**Created:** [3월 10, 2017, 11:39오후 UTC](https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866 "2017-03-10T23:39:56Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@lt100](https://meta.discourse.org/u/lt100)
#### Post date: [3월 10, 2017, 11:39오후 UTC](https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866/1 "2017-03-10T23:39:56Z")
I’ve started an update to `6ebddc4` from `a6dd1a2` and it got stuck at
`Writing /var/www/discourse/public/assets/discourse/templates/user/messages-randomstring.hbs`
It’s been 30+ minutes already, and updates on my server never take so long. What should I do?
load averages are ok at `0.05, 0.17, 0.49`
Memory: `4046604 total, 581436 free, 2563080 used, 902088 buff/cache`
Swap: `0 total, 0 free, 0 used. 612656 avail Mem`
Disk has some 39 Gb free
I’m on Ubuntu 16.04.1 LTS at DigitalOcean
Apparently, in the very beginning of the update log there is a warning:
`Warning: the running version of Bundler (1.14.4) is older than the version that created the lockfile (1.14.6). We suggest you upgrade to the latest version of Bundler by running gem install bundler` - but I didn’t notice it at first since the update proceeded without interruption.
Thank you!
p.s. prior to that I’ve updated docker manager to `97c3b03` - the update has stuck once (it has been cleaning temp files and then got `killed`) - I’ve restarted it, and it succeeded. Docker\_manager is now ‘Up to date’. Could it have somehow affected the Discourse update process?
---
### Author:  [@lt100](https://meta.discourse.org/u/lt100)
#### Post date: [3월 10, 2017, 11:47오후 UTC](https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866/2 "2017-03-10T23:47:18Z")
I’ve navigated away from the update page, and now the log doesn’t show anything at all:
The status is as following:
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [3월 11, 2017, 12:31오전 UTC](https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866/3 "2017-03-11T00:31:01Z")
You might have run out of ram during the upgrade. If your system is up and you think it’s not still rebuilding you can click that ominious sounding “Make it stop” button (I can’t remember the actual words).
If all else fails, you can ssh in to your host (or use Digital Ocean’s console if you use Windows and don’t have a terminal) and
```plaintext
cd /var/discourse
./launcher rebuild app
```
---
### Author:  [@lt100](https://meta.discourse.org/u/lt100)
#### Post date: [3월 11, 2017, 12:50오전 UTC](https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866/4 "2017-03-11T00:50:41Z")
Thank you, Jay! I’ve clicked the scary red button and status went from “Currently updating” to “Up to date”, but suspiciously swiftly, which made me decide to run `./launcher rebuild app`. Everything went well, my forum is up, running and up to date, for real this time.
For future reference, is it better to update using `./launcher rebuild app` rather then from the admin panel?
Thanks again!
p.s. and yes, it might have been the ram issue, after all (a spike before app rebuild)
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [6월 8, 2024, 12:45오후 UTC](https://meta.discourse.org/t/update-has-stuck-what-shall-i-do/58866/5 "2024-06-08T12:45:00Z")
이 주제는 2646일 후 자동으로 닫혔습니다. 더 이상 새 답변을 작성할 수 없습니다.