Erros 503, não é possível postar, editar, curtir, etc

dylanb · Dezembro 28, 2023, 8:27pm

Migrei meu site para uma nova instância (Azure para Lightsail, 32 GB de RAM) e estou enfrentando uma série de problemas.

O site está no ar e funcionando, mas aparentemente não está operando corretamente.

Parece que estou derrubando a instância, mesmo sem ter muito tráfego no momento e usando a instância Lightsail máxima.

Não consigo fazer nada no site: criar tópicos, curtir posts, etc.

Estou recebendo os seguintes erros:

Mensagem

'hijack topics timings ' ainda está em execução após 90 segundos no banco de dados padrão; este processo pode precisar ser reiniciado!

Backtrace

/var/www/discourse/lib/scheduler/defer.rb:105:in `block (2 levels) in do_work'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.8/lib/message_bus/timer_thread.rb:117:in `do_work'
/var/www/discourse/vendor/bundle/ruby/3.2.0/gems/message_bus-4.3.8/lib/message_bus/timer_thread.rb:95:in `block (2 levels) in queue'

Falha ao carregar recurso: o servidor respondeu com status 503 ()
/admin/reports/bulk?reports%5Bdau_by_mau%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bdau_by_mau%5D%5Bstart_date%5D=2023-11-28&reports%5Bdau_by_mau%5D%5Bend_date%5D=2023-12-28&reports%5Bdaily_engaged_users%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bdaily_engaged_users%5D%5Bstart_date%5D=2023-11-28&reports%5Bdaily_engaged_users%5D%5Bend_date%5D=2023-12-28&reports%5Bnew_contributors%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bnew_contributors%5D%5Bstart_date%5D=2023-11-28&reports%5Bnew_contributors%5D%5Bend_date%5D=2023-12-28&reports%5Bpage_view_total_reqs%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bpage_view_total_reqs%5D%5Bstart_date%5D=2023-11-28&reports%5Bpage_view_total_reqs%5D%5Bend_date%5D=2023-12-28:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
/admin/reports/bulk?reports%5Bvisits%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bvisits%5D%5Bstart_date%5D=2023-11-28&reports%5Bvisits%5D%5Bend_date%5D=2023-12-28&reports%5Btime_to_first_response%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Btime_to_first_response%5D%5Bstart_date%5D=2023-11-28&reports%5Btime_to_first_response%5D%5Bend_date%5D=2023-12-28&reports%5Blikes%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Blikes%5D%5Bstart_date%5D=2023-11-28&reports%5Blikes%5D%5Bend_date%5D=2023-12-28&reports%5Bflags%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bflags%5D%5Bstart_date%5D=2023-11-28&reports%5Bflags%5D%5Bend_date%5D=2023-12-28:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
/admin/reports/bulk?reports%5Buser_to_user_private_messages_with_replies%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Buser_to_user_private_messages_with_replies%5D%5Bstart_date%5D=2023-11-28&reports%5Buser_to_user_private_messages_with_replies%5D%5Bend_date%5D=2023-12-28&reports%5Busers_by_type%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Busers_by_type%5D%5Bstart_date%5D=2023-12-28&reports%5Busers_by_type%5D%5Bend_date%5D=2023-12-28&reports%5Busers_by_trust_level%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Busers_by_trust_level%5D%5Bstart_date%5D=2023-12-28&reports%5Busers_by_trust_level%5D%5Bend_date%5D=2023-12-28&reports%5Bstorage_stats%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Bstorage_stats%5D%5Bstart_date%5D=2023-12-28&reports%5Bstorage_stats%5D%5Bend_date%5D=2023-12-28:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
/admin/reports/bulk?reports%5Btop_referred_topics%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Btop_referred_topics%5D%5Bstart_date%5D=2023-12-22&reports%5Btop_referred_topics%5D%5Bend_date%5D=2023-12-28&reports%5Btop_referred_topics%5D%5Blimit%5D=8&reports%5Btrending_search%5D%5Bfacets%5D%5B%5D=prev_period&reports%5Btrending_search%5D%5Bstart_date%5D=2023-11-28&reports%5Btrending_search%5D%5Bend_date%5D=2023-12-28&reports%5Btrending_search%5D%5Blimit%5D=8:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
9953_2.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
24.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
24.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
24.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
24.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
24.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
24.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 503 ()
af975f5419770f3b2e0d38133d107299c2192045.png:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 404 ()
posts:1 
        
        
       Falha ao carregar recurso: o servidor respondeu com status 502 ()
ajax-error.js:35 SyntaxError: Token inesperado '<', "<html>
<h"... não é JSON válido
    at Function.parse [as parseJSON] (<anonymous>)
    at l (ajax-error.js:31:20)
    at u (ajax-error.js:74:10)
    at e.createPost (composer.js:1165:13)
l @ ajax-error.js:35
u @ ajax-error.js:74
createPost @ composer.js:1165
presence.js:211 Canal de presença '/discourse-presence/reply/14067' perdeu mensagem (recebeu 28, esperando 29), ressincronizando...
jquery.js:9940 
        
        
       POST https://forum.umhoops.com/topics/timings 503 (Serviço Indisponível)
send @ jquery.js:9940
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
flush @ screen-track.js:301
tick @ screen-track.js:365
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
screen-track.js:231 Falha ao atualizar os tempos do tópico 14067 devido ao erro 503
(anonymous) @ screen-track.js:231
_ @ rsvp.js:434
y @ rsvp.js:420
m @ rsvp.js:369
p.invoke @ queue.ts:203
p.flush @ queue.ts:98
h.flush @ deferred-action-queues.ts:75
$._end @ index.ts:616
$.end @ index.ts:298
$._run @ index.ts:667
$.run @ index.ts:339
d @ index.js:108
t.error @ ajax.js:148
u @ jquery.js:3223
fireWith @ jquery.js:3353
x @ jquery.js:9629
(anonymous) @ jquery.js:9888
load (async)
send @ jquery.js:9907
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
flush @ screen-track.js:301
tick @ screen-track.js:365
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
jquery.js:9940 
        
        
       POST https://forum.umhoops.com/topics/timings 503 (Serviço Indisponível)
send @ jquery.js:9940
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
tick @ screen-track.js:370
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
screen-track.js:231 Falha ao atualizar os tempos do tópico 14067 devido ao erro 503
(anonymous) @ screen-track.js:231
_ @ rsvp.js:434
y @ rsvp.js:420
m @ rsvp.js:369
p.invoke @ queue.ts:203
p.flush @ queue.ts:98
h.flush @ deferred-action-queues.ts:75
$._end @ index.ts:616
$.end @ index.ts:298
$._run @ index.ts:667
$.run @ index.ts:339
d @ index.js:108
t.error @ ajax.js:148
u @ jquery.js:3223
fireWith @ jquery.js:3353
x @ jquery.js:9629
(anonymous) @ jquery.js:9888
load (async)
send @ jquery.js:9907
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
tick @ screen-track.js:370
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
jquery.js:9940 
        
        
       POST https://forum.umhoops.com/topics/timings 503 (Serviço Indisponível)
send @ jquery.js:9940
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
tick @ screen-track.js:370
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
screen-track.js:231 Falha ao atualizar os tempos do tópico 14067 devido ao erro 503
(anonymous) @ screen-track.js:231
_ @ rsvp.js:434
y @ rsvp.js:420
m @ rsvp.js:369
p.invoke @ queue.ts:203
p.flush @ queue.ts:98
h.flush @ deferred-action-queues.ts:75
$._end @ index.ts:616
$.end @ index.ts:298
$._run @ index.ts:667
$.run @ index.ts:339
d @ index.js:108
t.error @ ajax.js:148
u @ jquery.js:3223
fireWith @ jquery.js:3353
x @ jquery.js:9629
(anonymous) @ jquery.js:9888
load (async)
send @ jquery.js:9907
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
tick @ screen-track.js:370
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
jquery.js:9940 
        
        
       POST https://forum.umhoops.com/topics/timings 503 (Serviço Indisponível)
send @ jquery.js:9940
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
tick @ screen-track.js:370
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60
screen-track.js:231 Falha ao atualizar os tempos do tópico 14067 devido ao erro 503
(anonymous) @ screen-track.js:231
_ @ rsvp.js:434
y @ rsvp.js:420
m @ rsvp.js:369
p.invoke @ queue.ts:203
p.flush @ queue.ts:98
h.flush @ deferred-action-queues.ts:75
$._end @ index.ts:616
$.end @ index.ts:298
$._run @ index.ts:667
$.run @ index.ts:339
d @ index.js:108
t.error @ ajax.js:148
u @ jquery.js:3223
fireWith @ jquery.js:3353
x @ jquery.js:9629
(anonymous) @ jquery.js:9888
load (async)
send @ jquery.js:9907
ajax @ jquery.js:9521
f @ ajax.js:173
(anonymous) @ rsvp.js:459
R @ rsvp.js:915
k @ ajax.js:192
sendNextConsolidatedTiming @ screen-track.js:188
tick @ screen-track.js:370
(anonymous) @ screen-track.js:60
$._run @ index.ts:665
$.run @ index.ts:339
d @ index.js:108
(anonymous) @ screen-track.js:60

Estava funcionando em algum momento, mas alguns posts parecem ter derrubado tudo. É possível que haja algum conjunto de tarefas em execução ou algo assim causando os problemas?

Falco · Dezembro 28, 2023, 8:32pm

Parece um banco de dados sobrecarregado.

Você ajustou o app.yml para usar essa RAM?

Você executou um vacuum no banco de dados após a migração?

dylanb · Dezembro 28, 2023, 8:33pm

Se for esta configuração, então sim. Eu a dobrei para isso.

Existe uma prática recomendada de como fazer isso? Eu não fiz.

dylanb · Dezembro 28, 2023, 8:58pm

Executei VACUUM CLEAN no postgres.

Ainda estou recebendo estes erros no log:
'hijack topics timings ’ ainda está em execução após 90 segundos no banco de dados padrão, este processo pode precisar ser reiniciado!
‘Track Visit’ ainda está em execução após 90 segundos no banco de dados padrão, este processo pode precisar ser reiniciado!

angus · Março 18, 2025, 7:33pm

@dylanb Estou vendo isso em uma instância e estava me perguntando se você avançou mais em sua investigação?

Tópico		Respostas	Visualizações
Moving posts returns 502 bad gateway Self-hosting performance , server-resources	71	5000	12 de Janeiro de 2025
Users reporting lots of 502 errors when attempting to post due to "max consecutive replies" check Bug	36	3043	18 de Janeiro de 2019
502 Bad Gateway for only two Topics Self-hosting arm	19	1913	17 de Novembro de 2022
User can't post: 500 internal server error Support	10	1432	18 de Abril de 2018
Could sidekiq queue be reason for 500 errors? Self-hosting server-resources	30	4047	13 de Junho de 2018

Erros 503, não é possível postar, editar, curtir, etc

Tópicos relacionados