# Upgrade Error from v1.6.0.beta1 to 1.6.0.beta2?
**URL:** https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963
**Category:** Self-hosting
**Tags:** server-resources
**Created:** [22 באפריל, 2016, 1:05am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963 "2016-04-22T01:05:31Z")
**Posts on this page:** 20
**Page:** 1
### Author:  [@Ninetailz](https://meta.discourse.org/u/Ninetailz)
#### Post date: [22 באפריל, 2016, 1:05am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/1 "2016-04-22T01:05:31Z")
Hello,
I tried to upgrade today from beta1 to beta2. In that process somehow it got stuck and it showed as upgrading… I reseted the upgrade now it shows i am at the latest version when i am not?
---
### Author:  [@ron\_jeremy](https://meta.discourse.org/u/ron_jeremy)
#### Post date: [22 באפריל, 2016, 1:23am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/2 "2016-04-22T01:23:42Z")
I hope I’m not hijacking your thread, and it’s not the same error as yours, but when I tried updating from +281 to beta 2 yesterday it would always fail with the following:
`$ cd /var/www/discourse && git fetch && git reset --hard HEAD@{upstream}
HEAD is now at e7d1fa8 Merge pull request #4186 from shaktikatare1989/suspention-details-in-log
.
.
.
.
.
Compressing: docker-manager-app-c32d676193f61b3085ec0e77f8d9fca361291a549828d82d1e33c356786f8ca0.js
gzip /var/www/discourse/public/assets/docker-manager-app-c32d676193f61b3085ec0e77f8d9fca361291a549828d82d1e33c356786f8ca0.js
Bundling assets
Compressing Javascript and Generating Source Maps
rake aborted!
Errno::ENOMEM: Cannot allocate memory - gzip -f -c -7 /var/www/discourse/public/assets/docker-manager-app-c32d676193f61b3085ec0e77f8d9fca361291a549828d82d1e33c356786f8ca0.js > /var/www/discourse/public/assets/docker-manager-app-c32d676193f61b3085ec0e77f8d9fca361291a549828d82d1e33c356786f8ca0.js.gz
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/core_ext/kernel/agnostics.rb:7:in ``'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/core_ext/kernel/agnostics.rb:7:in ``'
/var/www/discourse/lib/tasks/assets.rake:108:in `gzip'
/var/www/discourse/lib/tasks/assets.rake:161:in `block (4 levels) in '
/var/www/discourse/lib/tasks/assets.rake:125:in `call'
/var/www/discourse/lib/tasks/assets.rake:125:in `block in concurrent?'
/var/www/discourse/lib/tasks/assets.rake:152:in `call'
/var/www/discourse/lib/tasks/assets.rake:152:in `block (3 levels) in '
/var/www/discourse/lib/tasks/assets.rake:141:in `each'
/var/www/discourse/lib/tasks/assets.rake:141:in `block (2 levels) in '
/var/www/discourse/lib/tasks/assets.rake:125:in `concurrent?'
/var/www/discourse/lib/tasks/assets.rake:137:in `block in '
Tasks: TOP => assets:precompile`
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [22 באפריל, 2016, 2:00am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/3 "2016-04-22T02:00:21Z")
> [@ron\_jeremy](#):
>
> Errno::ENOMEM: Cannot allocate memory
Be sure to add swap to this instance of yours.
---
### Author:  [@ron\_jeremy](https://meta.discourse.org/u/ron_jeremy)
#### Post date: [22 באפריל, 2016, 2:17am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/4 "2016-04-22T02:17:24Z")
Already has 2GB swap. I added swap immediately after the Droplet was created.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [22 באפריל, 2016, 2:18am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/5 "2016-04-22T02:18:12Z")
What does `free` return?
---
### Author:  [@ron\_jeremy](https://meta.discourse.org/u/ron_jeremy)
#### Post date: [22 באפריל, 2016, 2:27am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/6 "2016-04-22T02:27:15Z")
It returns that I should hang my head in shame. I added swap but did not edit the /etc/fstab file, so I lost swap during a reboot somewhere. I have corrected that.
I also went ahead and added the following entries to **/etc/sysctl.conf** :
`vm.swappiness=10
vm.vfs_cache_pressure=50`
---
### Author:  [@precessor](https://meta.discourse.org/u/precessor)
#### Post date: [22 באפריל, 2016, 2:27pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/7 "2016-04-22T14:27:28Z")
Returning to this topic’s original flavour of upgrade error:
Me too
after `git pull` and `./launcher rebuild app`
---
### Author:  [@karussell](https://meta.discourse.org/u/karussell)
#### Post date: [22 באפריל, 2016, 3:29pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/8 "2016-04-22T15:29:39Z")
I have the same problem described in more details here: [Cannot access topics after upgrade from 1.6.0.beta1 to beta2](https://meta.discourse.org/t/cannot-access-topics-after-upgrade-from-1-6-0-beta1-to-beta2/42992)
---
### Author:  [@Ninetailz](https://meta.discourse.org/u/Ninetailz)
#### Post date: [22 באפריל, 2016, 10:10pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/9 "2016-04-22T22:10:27Z")
Bumping this topic since it got derailed, i did git pull and rebuild too
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [22 באפריל, 2016, 10:12pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/10 "2016-04-22T22:12:16Z")
Did you reboot your server?
---
### Author:  [@Ninetailz](https://meta.discourse.org/u/Ninetailz)
#### Post date: [22 באפריל, 2016, 10:13pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/11 "2016-04-22T22:13:28Z")
Nope? Should i do that?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [22 באפריל, 2016, 10:14pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/12 "2016-04-22T22:14:39Z")
Yes, you should try that.
---
### Author:  [@Ninetailz](https://meta.discourse.org/u/Ninetailz)
#### Post date: [22 באפריל, 2016, 10:24pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/13 "2016-04-22T22:24:38Z")
Same result after rebooting
---
### Author:  [@karussell](https://meta.discourse.org/u/karussell)
#### Post date: [23 באפריל, 2016, 1:01am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/14 "2016-04-23T01:01:05Z")
What mechanism is there to use v1.6.0.beta2 if there is a more recent `test_pass` version? It looks like my build is saying the identical (wrong) thing and pointing to [this commit](https://github.com/discourse/discourse/commits/ed446ca4876639f6bfc7b064c2e3deb85da9f4c1) but stating this is v1.6.0.beta1+281. I’ll try if [my problem](https://meta.discourse.org/t/cannot-access-topics-after-upgrade-from-1-6-0-beta1-to-beta2/42992) still happens if I explicitely use
---
### Author:  [@Ninetailz](https://meta.discourse.org/u/Ninetailz)
#### Post date: [24 באפריל, 2016, 11:17pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/15 "2016-04-24T23:17:16Z")
Umm any other way i can solve this??
---
### Author:  [@cpradio](https://meta.discourse.org/u/cpradio)
#### Post date: [24 באפריל, 2016, 11:31pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/16 "2016-04-24T23:31:59Z")
You are simply referring to the version mis-match right? If so, don’t sweat it. You can always visit admin/upgrade to pick up the latest changes. My sandbox is showing the same thing as your screenshot.
---
### Author:  [@SidV](https://meta.discourse.org/u/SidV)
#### Post date: [25 באפריל, 2016, 1:04am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/17 "2016-04-25T01:04:42Z")
Same here:
I’ve already tried:
```
cd /var/discourse
git pull
./launcher rebuild app
```
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [26 באפריל, 2016, 4:50am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/18 "2016-04-26T04:50:14Z")
Well then this is completely unrelated to the OP on the topic but somehow we forgot to bump versions right @neil
Meta is at v1.6.0.beta1 +316 … latest is beta2
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [26 באפריל, 2016, 4:56am UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/19 "2016-04-26T04:56:21Z")
Well that explains all the version issue reports ☹
---
### Author:  [@neil](https://meta.discourse.org/u/neil)
#### Post date: [26 באפריל, 2016, 2:36pm UTC](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963/20 "2016-04-26T14:36:47Z")
Hmm I don’t see how we forgot to bump version.
Both [master](https://github.com/discourse/discourse/blob/master/lib/version.rb) and [beta](https://github.com/discourse/discourse/blob/beta/lib/version.rb) branches have the version.
The `installed_describe` value is wrong, but everything else is correct:
Something about this isn’t working anymore:
```plaintext
installed_describe: `git describe --dirty`
```
[Next page](https://meta.discourse.org/t/upgrade-error-from-v1-6-0-beta1-to-1-6-0-beta2/42963.md?page=2)