# "500 Internal Server Error" ao aprovar uma postagem em revisão

**URL:** https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606
**Category:** Self-hosting
**Created:** [10 Setembro , 2020 11:55 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606 "2020-09-10T11:55:25Z")
**Posts on this page:** 11
**Page:** 1

<div class="post-metadata">

### Author: ![CamilleRoux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/camilleroux/32/119575_2.png) [@CamilleRoux](https://meta.discourse.org/u/CamilleRoux)
#### Post date: [10 Setembro , 2020 11:55 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/1 "2020-09-10T11:55:25Z")

</div>

Olá,

Estou usando a versão 2.5.1 do Discourse e recebo um “Erro 500 do Servidor Interno” ao aprovar uma postagem em revisão.

Aqui está o erro em `/logs`:

```
Mensagem (7 cópias relatadas)

ActiveRecord::StatementInvalid (PG::InFailedSqlTransaction: ERRO: transação atual foi abortada, comandos ignorados até o fim do bloco de transação
)
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-2.0.2/lib/patches/db/pg.rb:72:in `exec_params'

Backtrace

rack-mini-profiler-2.0.2/lib/patches/db/pg.rb:72:in `exec_params'
rack-mini-profiler-2.0.2/lib/patches/db/pg.rb:72:in `exec_params'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql_adapter.rb:675:in `block (2 levels) in exec_no_cache'
activesupport-6.0.3.1/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
activesupport-6.0.3.1/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
activesupport-6.0.3.1/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql_adapter.rb:674:in `block in exec_no_cache'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract_adapter.rb:722:in `block (2 levels) in log'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `block in synchronize'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `handle_interrupt'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:21:in `synchronize'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract_adapter.rb:721:in `block in log'
activesupport-6.0.3.1/lib/active_support/notifications/instrumenter.rb:24:in `instrument'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract_adapter.rb:712:in `log'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql_adapter.rb:673:in `exec_no_cache'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql_adapter.rb:654:in `execute_and_clear'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:111:in `exec_delete'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract/database_statements.rb:180:in `delete'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract/query_cache.rb:22:in `delete'
activerecord-6.0.3.1/lib/active_record/relation.rb:587:in `delete_all'
/var/www/discourse/app/models/topic_link.rb:376:in `cleanup_entries'
/var/www/discourse/app/models/topic_link.rb:139:in `extract_from'
/var/www/discourse/lib/post_creator.rb:576:in `extract_links'
/var/www/discourse/lib/post_creator.rb:180:in `block in create'
/var/www/discourse/lib/post_creator.rb:359:in `block in transaction'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract/database_statements.rb:278:in `transaction'
activerecord-6.0.3.1/lib/active_record/transactions.rb:212:in `transaction'
/var/www/discourse/lib/post_creator.rb:358:in `transaction'
/var/www/discourse/lib/post_creator.rb:174:in `create'
/var/www/discourse/app/models/reviewable_queued_post.rb:80:in `perform_approve_post'
/var/www/discourse/app/models/reviewable.rb:355:in `public_send'
/var/www/discourse/app/models/reviewable.rb:355:in `block in perform'

```

---

<div class="post-metadata">

### Author: ![Maurizio\_Mattoli](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/maurizio_mattoli/32/194792_2.png) [@Maurizio\_Mattoli](https://meta.discourse.org/u/Maurizio_Mattoli)
#### Post date: [22 Setembro , 2020 19:51 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/2 "2020-09-22T19:51:58Z")

</div>

Estamos enfrentando o mesmo problema nas mesmas circunstâncias descritas por Camille.

Então, tentamos editar a postagem primeiro e, em seguida, tentamos aprová-la novamente, mas o problema persiste.

Há alguma solução disponível?

Obrigado

---

<div class="post-metadata">

### Author: ![CamilleRoux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/camilleroux/32/119575_2.png) [@CamilleRoux](https://meta.discourse.org/u/CamilleRoux)
#### Post date: [1 Outubro , 2020 14:48 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/3 "2020-10-01T14:48:56Z")

</div>

Ainda estou com o mesmo problema na versão v2.5.2 +2.  
Parece que isso ocorre com as postagens que ativam a opção ‘silenciar automaticamente digitadores rápidos na primeira postagem’.

---

<div class="post-metadata">

### Author: ![Roman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/roman/32/157504_2.png) [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [1 Outubro , 2020 15:30 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/4 "2020-10-01T15:30:24Z")

</div>

Olá @CamilleRoux!

Não consegui reproduzir isso localmente, então talvez eu esteja perdendo algo. Isso acontece quando você tenta aprovar qualquer post em fila, ou apenas em um específico?

---

<div class="post-metadata">

### Author: ![CamilleRoux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/camilleroux/32/119575_2.png) [@CamilleRoux](https://meta.discourse.org/u/CamilleRoux)
#### Post date: [1 Outubro , 2020 15:52 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/5 "2020-10-01T15:52:06Z")

</div>

Não tenho outra mensagem para revisão… O que posso fazer para fornecer mais informações?

Acabei de definir “aprovar novos tópicos a menos que nível de confiança” para o máximo e agora recebo um erro 500 ao postar um novo tópico. Parece ser exatamente o mesmo erro:

```
ActiveRecord::StatementInvalid (PG::InFailedSqlTransaction: ERROR: current transaction is aborted, commands ignored until end of transaction block
)
/var/www/discourse/vendor/bundle/ruby/2.6.0/gems/rack-mini-profiler-2.0.2/lib/patches/db/pg.rb:72:in `exec_params'

Backtrace

rack-mini-profiler-2.0.2/lib/patches/db/pg.rb:72:in `exec_params'
rack-mini-profiler-2.0.2/lib/patches/db/pg.rb:72:in `exec_params'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql_adapter.rb:675:in `block (2 levels) in exec_no_cache'
activesupport-6.0.3.1/lib/active_support/dependencies/interlock.rb:48:in `block in permit_concurrent_loads'
activesupport-6.0.3.1/lib/active_support/concurrency/share_lock.rb:187:in `yield_shares'
activesupport-6.0.3.1/lib/active_support/dependencies/interlock.rb:47:in `permit_concurrent_loads'
activerecord-6.0.3.1/lib/active_record/connection_adapters/postgresql_adapter.rb:674:in `block in exec_no_cache'
activerecord-6.0.3.1/lib/active_record/connection_adapters/abstract_adapter.rb:722:in `block (2 levels) in log'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:26:in `block (2 levels) in synchronize'
activesupport-6.0.3.1/lib/active_support/concurrency/load_interlock_aware_monitor.rb:25:in `handle_interrupt'

```

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [1 Outubro , 2020 16:13 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/6 "2020-10-01T16:13:58Z")

</div>

Você pode entrar no container e verificar os logs do PostgreSQL em busca de um erro por volta do mesmo horário?

---

<div class="post-metadata">

### Author: ![CamilleRoux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/camilleroux/32/119575_2.png) [@CamilleRoux](https://meta.discourse.org/u/CamilleRoux)
#### Post date: [1 Outubro , 2020 18:40 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/7 "2020-10-01T18:40:01Z")

</div>

Aqui está o erro (referente ao erro do tópico):

```
2020-10-01 18:37:18.894 UTC [25661] discourse@discourse ERROR: valor nulo na coluna "private_message" viola a restrição not-null
2020-10-01 18:37:18.894 UTC [25661] discourse@discourse DETAIL: A linha com falha contém (8803, 'a':25 'api':4A,17 'arriv':23 'avanc':48 'bas':14 'cod':54 'comm..., Comment obtenir l'API odoo sur React Native? Developpement J'u..., fr, 3, null).
2020-10-01 18:37:18.894 UTC [25661] discourse@discourse STATEMENT: INSERT INTO post_search_data
	(post_id, search_data, locale, raw_data, version)
	VALUES (8803, setweight(to_tsvector('french', coalesce('Comment obtenir l''API odoo sur React Native?','')), 'A') ||
	setweight(to_tsvector('french', coalesce('Developpement','')), 'B') ||
	setweight(to_tsvector('french', coalesce('','')), 'C') ||
	setweight(to_tsvector('french', coalesce('J’utilise Odoo comme base de donnees API sur react native mais j’arrive pas a me connecter, j’ai utilise le package npm react-native-odoo , vous pouvez voir mon erreur sur l’image. Merci d’avance pour vos reponses Voici mon Code oddo et l’erreur que j’obtiens error','')), 'D')
	, 'fr', 'Comment obtenir l''API odoo sur React Native? Developpement J’utilise Odoo comme base de donnees API sur react native mais j’arrive pas a me connecter, j’ai utilise le package npm react-native-odoo , vous pouvez voir mon erreur sur l’image. Merci d’avance pour vos reponses Voici mon Code oddo et l’erreur que j’obtiens error', 3)

2020-10-01 18:37:18.897 UTC [25661] discourse@discourse ERROR: a transação atual foi abortada, comandos ignorados até o fim do bloco de transação
2020-10-01 18:37:18.897 UTC [25661] discourse@discourse STATEMENT: UPDATE topic_search_data
	SET
	   raw_data = 'Comment obtenir l''API odoo sur React Native? J’utilise Odoo comme base de donnees API sur react native mais j’arrive pas a me connecter, j’ai utilise le package npm react-native-odoo , vous pouvez voir mon erreur sur l’image. Merci d’avance pour',
	   locale = 'fr',
	   search_data = setweight(to_tsvector('french', coalesce('Comment obtenir l''API odoo sur React Native?','')), 'A') ||
	setweight(to_tsvector('french', coalesce('J’utilise Odoo comme base de donnees API sur react native mais j’arrive pas a me connecter, j’ai utilise le package npm react-native-odoo , vous pouvez voir mon erreur sur l’image. Merci d’avance pour','')), 'B') ||
	setweight(to_tsvector('french', coalesce(NULL,'')), 'C') ||
	setweight(to_tsvector('french', coalesce(NULL,'')), 'D')
	,
	   version = 3
	WHERE topic_id = 4351

2020-10-01 18:37:18.900 UTC [25661] discourse@discourse ERROR: a transação atual foi abortada, comandos ignorados até o fim do bloco de transação
2020-10-01 18:37:18.900 UTC [25661] discourse@discourse STATEMENT: DELETE FROM "topic_links" WHERE ((post_id = 8803 AND NOT reflection) OR (link_post_id = 8803 AND reflection))

```

---

<div class="post-metadata">

### Author: ![Roman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/roman/32/157504_2.png) [@Roman](https://meta.discourse.org/u/Roman)
#### Post date: [1 Outubro , 2020 21:37 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/8 "2020-10-01T21:37:59Z")

</div>

Obrigado, isso realmente ajuda!

Você estava rastreando a branch `beta` em algum momento e depois mudou para a `stable`? A coluna `private_message` foi adicionada na `v2.6.0.beta2`, mas o commit não está incluído na `v2.5.2 +2`. Este é o commit:

> <https://github.com/discourse/discourse/commit/92b7fe4c62094275c5dd09b1f3dac5c5cbcad1c0>

---

<div class="post-metadata">

### Author: ![CamilleRoux](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/camilleroux/32/119575_2.png) [@CamilleRoux](https://meta.discourse.org/u/CamilleRoux)
#### Post date: [1 Outubro , 2020 21:47 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/9 "2020-10-01T21:47:38Z")

</div>

Arf… Sim, eu fiz isso, minha culpa. Muito obrigado!

Você sabe se a próxima versão estável será lançada em breve?

---

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [1 Outubro , 2020 21:55 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/10 "2020-10-01T21:55:18Z")

</div>

> [@CamilleRoux](#):
>
> Sim, fiz isso.

Isso é totalmente não suportado e resultará em um Discourse quebrado. Reverta para o padrão `tests-passed` ou `beta` o mais rápido possível.

> [@CamilleRoux](#):
>
> Você sabe se a próxima versão estável será lançada em breve?

Lançamos uma versão “estável” aproximadamente a cada 6 meses. A próxima está sendo rastreada em [Versão 2.6 do Discourse](https://meta.discourse.org/t/discourse-version-2-6/151394).

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [31 Outubro , 2020 21:56 UTC](https://meta.discourse.org/t/500-internal-server-error-when-approving-a-post-in-review/163606/11 "2020-10-31T21:56:34Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
