Be sure to add swap to this instance of yours.
1 Like
Already has 2GB swap. I added swap immediately after the Droplet was created.
What does free return?
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
7 Likes
Returning to this topic’s original flavour of upgrade error:
Me too
after git pull and ./launcher rebuild app
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
Did you reboot your server?
Nope? Should i do that?
Yes, you should try that.
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 but stating this is v1.6.0.beta1+281. I’ll try if my problem still happens if I explicitely use
Umm any other way i can solve this??
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.
Same here:
I’ve already tried:
cd /var/discourse
git pull
./launcher rebuild appWell 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
Well that explains all the version issue reports 
Hmm I don’t see how we forgot to bump version.
Both master and beta branches have the version.
The installed_describe value is wrong, but everything else is correct:
Something about this isn’t working anymore:
installed_describe: `git describe --dirty`
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.
7 Likes