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? [image]

I recreated the v1.6.0.beta2 tag so maybe it will fix the installed_describe value… I don’t know what happened to it.

[image] ron_jeremy: Errno::ENOMEM: Cannot allocate memory Be sure to add swap to this instance of yours.

Already has 2GB swap. I added swap immediately after the Droplet was created.

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

Returning to this topic’s original flavour of upgrade error: Me too after git pull and ./launcher rebuild app [image]

I have the same problem described in more details here: Cannot access topics after upgrade from 1.6.0.beta1 to beta2

Bumping this topic since it got derailed, i did git pull and rebuild too

Upgrade Error from v1.6.0.beta1 to 1.6.0.beta2?

Product Support Self-hosting

codinghorror (Jeff Atwood) April 22, 2016, 10:12pm 10

Did you reboot your server?

Topic		Replies	Views
Fail to upgrade - Make sure that `gem install json -v '1.8.2'` succeeds before bundling Self-hosting server-resources	17	6930	February 13, 2015
Errno::ENOMEM: Cannot allocate memory Self-hosting server-resources	14	9155	January 16, 2019
Upgrade Failed from v1.7.0.beta3 +20 TO 1.7.0.beta3 Product Support	4	1043	August 29, 2016
Upgrading problems Self-hosting server-resources	1	1619	May 23, 2016
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	3008	September 26, 2020

Upgrade Error from v1.6.0.beta1 to 1.6.0.beta2?

Related topics