I came here hoping to find a step by step diagnostic for when a Discourse site is found in a 502 Bad Gateway condition. It seems the only options are along these lines:
- Discourse update might have failed, use
./launcher rebuild app.
- Update and reboot server.
These are the kind of responses we get from a tier-1 support tech, or an email bot.
What else can we do to look at logs and see exactly why the environment died? With that info we might learn how to prevent the issue in the future.
For example, would it be appropriate to script a cron process to occasionally ping Discourse, and if the response is a 502 or similar return code, auto rebuild?
Rebuilding seems to be a rather brutal way to solve a problem too. It’s not a diagnostic.
I’m really hoping someone can point us to a popular “Diagnosing Discourse Issues” document that dummies like me have missed.
From reading a lot of posts here, typically forum admins aren’t the cause of 502s, and it’s a plugin/core error. So there wouldn’t be particularly much you could do to avoid those issues.
Console logs always help, they can pinpoint the problematic plugin a lot of times.
I can open the console on this VPS but the text window is limited.
Are there specific logs that can be checked in the container or in the OS?
Is there already some form of ping process in the host OS or the container that detects when processes are down?
Might a simple server restart within the container be a good way to approach this rather than a full rebuild?
BTW, I am running the latest beta/dev, so it’s entirely possible that a recent update took the server down, as we’ve seen in the past. I don’t recall at the moment if there are any non-default plugins installed.
I have the freedom to help with the diagnostics of this without our community getting upset, though within some number of months we’ll need to move to more stable versions just to keep our users comfortable. So if this is something in the build, I’m happy to help find it.
I meant browser logs, from dev tools or the equivalent on your browser.
I don’t believe so, but you could always try.
Is the disk full?
Does this happen frequently?
Look at /var/discourse/logs/rails/production.log