We recently updated to “v2.2.0.beta3 +36 tests-passed” and have started getting /admin/dashboard/general.json Server 502 errors. On a quick search it looks very similar to this one: [画像] Admin dashboard won't load after upgrade to v2.1.0.beta3 +20 installation I rebuilt…

Yes, that was it - problem solved. I created a clean new S3 bucket for the backup location and now the backup/index works quickly. Problem Summary: With the introduction of direct backups to S3 using the new Backup Location feature, the listing of objects in S3 at the ‘S3 backup location’ setting c…

Awesome - is there a way to remove the backups for now so that the Dashboard works again until this is fixed?

If you have S3 backups enabled try you can try to run this from the rails console: ./launcher enter app rails c SiteSetting.backup_location = 'local' refresh the site and see if you can access the dashboard

Instead of doing that I just did it from the Settings and reloaded the page and Dashboard stats work again - but I can’t rely on that as I need S3 backups… BUT this is a good workaround so that we can check stats until the full fix is in.

Ah sorry, I thought that you were unable to enter the dashboard at all. The result is the same. Then you need to wait for the official fix before reactivate the setting

[画像] j.jaffeux: @gerhard and I have a plan to fix this, it’s not related to reports, but how we get backups size. I can confirm that changing ‘Settings / Backup / Backup location’ to ‘local’ from ‘Amazon S3’ means the dashboard loads quickly again. Thanks for looking at it, and we’ll await t…

I’m not sure what’s actually causing the timeout… How many objects are in your backup bucket? Does Admin -> Backups load without problems when backup_location is set to S3?

Our /admin/backups page (or rather then underlying request for .backups.json) takes about 50 seconds to come up each time, so it looks like the culprit of why the dashboard times out. There are six entries in the ‘filename’ list for us, as we only keep that amount of backups rolling in S3 for 7 day…

The backups to S3 seem to be working ok, which is good, as I did a manual backup and it worked. One ‘funny’ is that there is a new entry at the bottom of the list, perhaps showing some mismatch between what’s in the DB and what is actually in S3? [image] Note: the odd ‘3a97e…gz’ entry at the bot…

Not sure if helpful, but one potential tweak to this would be to put the S3 backups with a ‘discoursebackup/’ prefix and then you could pass that here to filter the object.list call to AWS - that way it would filter it and return quickly without an empty bucket expected: @s3_helper.list(S3BACKUP_PR…

v2.2.0.beta3 へのアップグレード後、管理ダッシュボードが読み込まれない +36

サポート

pfaffman (Jay Pfaffman) 2018 年 10 月 26 日午後 9:54 31

Does that mean that the new Backup location is broken? Or does it mean that if you did it the old way it’s broken because of the change?

トピック		返信	表示
Admin dashboard won't load after upgrade to v2.1.0.beta3 +20 Self-hosting	32	1941	2018 年 8 月 7 日
After latest admin/upgrade my Admin dashboard won't load Support	9	2201	2021 年 7 月 20 日
After update to 2.1.0 admin dashboard have errors and not load Bug	16	1174	2018 年 9 月 15 日
Admin functions Support	11	297	2025 年 9 月 26 日
Disk usage spike during backup, Discourse crashed hard :-( Self-hosting server-resources	21	2680	2020 年 7 月 23 日

v2.2.0.beta3 へのアップグレード後、管理ダッシュボードが読み込まれない +36

関連トピック