@Vitaly Zasimovichโ , Ganglia metrics are available only if the job runs for more than 15 minutes. For assignments completed within 15 minutes, the metrics won't be available.
How to fix a 502 Bad Gateway error
There are several critical steps that users can take to attempt to fix a 502 Bad Gateway error.
- Refresh your browser: Refresh your browser: One of the simplest tricks that can help resolve the issue is to refresh the browser a few times. The error can sometimes be displayed due to a server becoming overloaded with requests - a topic that is often resolved quickly. Refreshing the browser and sending new proposals to the website can help rest the connection and get your browsing back up.
- Clear your browser cache: Every browser is different, but modern browsers such as Chrome, Firefox, Safari, and Microsoft Edge make it easy to find this setting, often located in the browser history section. Clearing the cache is another effective way to overcome 502 bad gateway errors, so itโs worth trying, just in case.
- Temporarily disable your firewall: Weโll preface this by saying that a firewall should always be active, and it is not recommended to disable it for any significant time. But in some cases, disabling it and successfully re-attempting to connect to the website may indicate a problem with the firewallโs settings, which can be usually altered through the admin console of your security provider.
- Check with monitoring sites: If this doesn't work, you could always turn to online services such as Down for everyone or just me? or Down detector. These monitor the web for any outages and allow users to report any problems they may be encountering. If it's an issue affecting not just you, then the chances are others will have said it, and the more people are reporting problems, the more likely itโs a prolonged issue.
- Use a VPN to access the site: Various online virtual private networks (VPNs), such as Hide My *** and others, can reroute your connection before you access the site. This means you'll be able to figure out whether any issues may have popped up with your ISP, for example, when ISPs block access to specific sites for any particular reason.
- Examine web server logs: If this error persists, it may require some further investigation to find a solution. Examining web server logs when the error occurs will be an excellent place to start. If you are the website owner, you can check your FQDN (fully qualified domain name) is correctly resolving. You can also check if a server is reachable via a ping text or traceroute.
