Out of the blue, my Discourse instance (docker installed) is returning Bad Gateway errors at intervals. The container is still running, but I need to manually stop and start the app to get things going again. Then it seems fine … until this occurs again sometime shortly later. I’m unsure of the appropriate log location for more info. Where should I start? Thanks very much!
1 Like
Are you running out of RAM? What does free -h say?
What do you see in /var/discourse/shared/standalone/log/rails/production.log (I think I typed it right, but if not, you’ll have to adjust). And /var/discourse/shared/standalone/log/var_log/nginx/..something...
1 Like
I’ll check the next time this happens. Thanks! Right now less than 50% RAM in use.
1 Like
Probably not RAM, then. You can look at the logs now.
1 Like
The logs look OK. Nothing obvious anyway. Even when it’s up, it’s been very sluggish. Often takes a long time to respond, long enough that it timeouts for users (or even me, locally). Really strange since that box has been stable for a long time and little changes on it other than routine Ubuntu updates (18.04).