Le forum Discourse se fige et expiré, ne charge pas

Soutien Installation
1

Depuis peu, notre forum Discourse commence à expirer sur la plupart des requêtes : https://caddy.community

Aucune mise à jour ou modification n’a été effectuée lorsque le problème a commencé il y a quelques jours. Parfois, il se charge correctement, mais quelques minutes plus tard, il faut plusieurs minutes pour qu’il se charge. (Si le lien ci-dessus se charge rapidement pour vous, réessayez quelques minutes plus tard. Vous pouvez également essayer avec curl.)

Nous sommes hébergés sur DigitalOcean.

Les ressources de la machine ne sont pas saturées : il y a suffisamment de CPU, de RAM, d’espace disque et d’E/S réseau disponibles.

Il n’y a aucune erreur dans les journaux, et aucun processus inconnu n’est en cours d’exécution sur la machine. Elle fonctionnait correctement depuis environ 3 ans, mais maintenant elle ne se charge plus.

Quelqu’un sait comment rendre le forum plus rapide ? Nous avons redémarré la machine, mais le forum fonctionne toujours lentement.

2 « J'aime »
2

Hey @mholt :wave:,

I did try going back and forth between /latest and /categories and it’s pretty fast.

Are you seeing slowdown in specific routes of the app?

Also, do you have the MiniProfiler enabled?

Please follow this to enable it:Long loading times for user summary page with slow database

After enabling it, when you hit a slow down you will know exactly where it is.

7 « J'aime »
3

Huh… dang, it is loading faster today. :thinking: (Others in our community have also experienced it, I know it’s not just me, haha – but it can be intermittent, it seems.)

I’ll try that out when I have a chance, thanks!

5 « J'aime »
4

Hmm, it seems my ssh connections also time out sometimes.

I wonder if DigitalOcean is having network issues (they haven’t reported anything, though) – maybe I will have to open a ticket with DO to find out. It might not be specific to Discourse.

2 « J'aime »
5

This has started happening again recently: takes several minutes for the forum to load.

Ping times to the DigitalOcean droplet are nominal: ~80ms. Server load is also nominal:

46%20PM
46%20PM1992×1750 284 KB

The timings in the debug thing in the corner (MiniProfiler) don’t reveal any problems: all times are within ~300ms:

12%20PM
12%20PM1284×416 62.9 KB

(This page took about 3 minutes to load.)

Is there any part of the loading process between reaching the server and rendering the page that are not counted by the MiniProfiler?

2 « J'aime »
6

Time spent on Redis isn’t counted and can cause what you see. You will have to dig into the server and check if Redis is having trouble to persist changes to disk.

2 « J'aime »
8

Interesting, any tips on how to do that? Or link to a relevant guide? This is outside my pay grade :sweat_smile:

2 « J'aime »
9

Oh let me correct myself a bit here. The time spent on redis won’t be on the broken down part of mini profiler, but be counted in the overall time in the first column. So looking at your screenshot, this doesn’t appear to be the case.

Does Caddy logs time waiting on the backend and overall time spent on each request? Is there a possibility that the reverse proxy was waiting?

3 « J'aime »
10

I will add this to the logs and try to find out next time it happens.

1 « J'aime »
11

This could be time it is taking it to grab static assets ? Maybe have a look in chrome dev tools next time this happens?

1 « J'aime »
12

Thanks for the idea Sam. I have looked at the network inspector before and I do not believe I remember anything too telling – but I’ll check it in more detail next time.

This tends to happen every few days or so, I’ll report back when it does!

1 « J'aime »