Il forum Discourse si blocca e scade, non si carica

Supporto Installazione
1

Da qualche tempo, il nostro forum Discourse inizia a timeout su la maggior parte delle richieste: https://caddy.community

Non sono state apportate aggiornamenti o modifiche quando il problema è iniziato alcuni giorni fa. A volte si carica correttamente, ma dopo pochi minuti impiega minuti per caricare. (Quindi se il link sopra si carica velocemente per te, riprova dopo alcuni minuti. Puoi anche provare con curl.)

Siamo ospitati su DigitalOcean.

Le risorse della macchina non sono sature: ci sono abbondanti CPU, RAM, spazio su disco e I/O di rete disponibili.

Non ci sono errori nei log e non ci sono processi sconosciuti in esecuzione sulla macchina. Ha funzionato bene per circa 3 anni, ma ora non si carica più.

Qualcuno sa come far ripartire il forum più velocemente? Abbiamo riavviato la macchina, ma il forum continua a essere lento.

2 Mi Piace
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 Mi Piace
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 Mi Piace
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 Mi Piace
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 Mi Piace
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 Mi Piace
8

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

2 Mi Piace
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 Mi Piace
10

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

1 Mi Piace
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 Mi Piace
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 Mi Piace