503 Service Unavailable after error about space

I figured out what was happening, the 503 was totally unrelated to the S3 template error.

It looks like launcher had downloaded/created about 5GB of docker images/instances and eaten up every last bit of space on the server. So when the launcher tried to run it had absolutely no space to use for discourse, the server has a 10GB HDD on it and the launcher managed to eat up every last bit of it with only a handful of rebuilds.

It’s resolved now, but thank you for responding, I think probably what happened with the S3 settings is that I was filling in the settings as discourse was basically in it’s death throes (from lack of space) and thats why the errors occurred and the log entries happened.

2 Likes