Closed dominicporter closed 4 years ago
The obvious question would be if you're hitting your DO droplet's memory limit when loading the grain. Maybe bigger repos are causing you to hit it?
So it turns out your rather obvious question was the right one... it looked like I had about half a gig free but when I rean htop
in the box whilst creating a new gitlab grain it was spiking right up to 100% memory. I added another gig of swap apace (because I am too stingy to pay more for my droplet) and it worked first time. Might be one to put in docs somewhere (I will if I can find where) - "Best to have more than 1Gb RAM, or at least some swap space".
Trying to create a new grain I get a 404 page.
Logs show this line which looks like the culprit:
I'm running Sandstorm on a DigitalOcean Droplet following the tuorial on how to transition from hosted server a few months ago.
Some of my previous GL grains do load, some do not. I am fairly certain I have created at least one successful GL grain since migrating, but not certain.
Full log as follows: