Folding Forum

Yep, I noticed that too... I'm guessing the guys are doing some DB work... If it's still not updating by morning I'll shoot them an email to see if I can get an ETA....

Hey everyone,
after reading the call for help regarding corona I joined the project, but it seems that not every part of the web presence is as fresh as the blog. The donor and team statistics are all showing a bad gateway.

This also breaks the web interface, as the following links are returning bad gateways as well:
https://apps.foldingathome.org/project- ... sion=7.5.1
https://apps.foldingathome.org/stats.py ... 3251805880

Will this be fixed anytime soon?

Welcome to the folding support forum.

I have second hand information that some work was going to be done on the stats database, but do not have exact times this was to occur. If this does not clear up later, please post details. You might also need to clear browser cache.

Thanks for the welcome!

What kind of details do you need? You can execute , it always returns a 502.

It's definitely not his browser cache. I see this issue from multiple clients in geographically diverse locations.

The error is either "bad gateway" or "gateway timeout" every time accessing stats.foldingathome.org.

PT

Yup, still giving 'Bad Gateway'.

Nothing dynamic is working on the stats website outside of the static portions of the pages. "Bad Gateway" errors everywhere.

The /api/donors page, for example, gives

> 502 Bad Gateway
> nginx/1.14.2

Usually, when something like this happens, it's the flat files that get hit, but this time, it's ONLY the Teams flat file that is suffering. The User's flat file is updating normally, but the Teams file hasn't been properly updated since the 3am update on Feb 3rd.

Still bad gateway for me too , started folding because of the coronavirus initiative.

I suppose the WU's still get submitted as they are different servers ? Just the database is not working to collect all points together and show in a list?

The problems are with the server that acts as a frontend for the database. So WU's are still being entered into the database, just some of the reports that get pulled from the database are not working at this time.

Joe_H wrote:The problems are with the server that acts as a frontend for the database. So WU's are still being entered into the database, just some of the reports that get pulled from the database are not working at this time.

Ah good, thought so , seeing all the different servers for collection and work.

So I can leave it running without worrying too much.

hamba wrote:So I can leave it running without worrying too much.

Yes. It will catch up in time and there's nothing you can do anyway to either help or hurt that situation.

Seems to be working again.

Joe_H wrote:The problems are with the server that acts as a frontend for the database. So WU's are still being entered into the database, just some of the reports that get pulled from the database are not working at this time.

I noticed a problem under viewtopic.php?f=61&t=32283. Is there any chance the performance report is also compiled from the affected parts of that server?

502 Bad Gateway is back.