# 502 Bad Gateway após atualização para 2.7.0beta2

**URL:** https://meta.discourse.org/t/502-bad-gateway-after-upgrade-to-2-7-0beta2/177030
**Category:** Self-hosting
**Created:** [23 Janeiro , 2021 12:46 UTC](https://meta.discourse.org/t/502-bad-gateway-after-upgrade-to-2-7-0beta2/177030 "2021-01-23T12:46:38Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![napcok](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/napcok/32/68153_2.png) [@napcok](https://meta.discourse.org/u/napcok)
#### Post date: [23 Janeiro , 2021 12:46 UTC](https://meta.discourse.org/t/502-bad-gateway-after-upgrade-to-2-7-0beta2/177030/1 "2021-01-23T12:46:38Z")

</div>

Atualizado via CLI:

```plaintext
cd /var/discourse
git pull
./launcher rebuild app

```

Tudo ocorreu normalmente, mas obtive o erro 502 Bad Gateway.

**docker ps**

```plaintext
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
6598e9407e29 local_discourse/app "/sbin/boot" 35 minutes ago Up 22 minutes 0.0.0.0:2045->80/tcp app

```

**./launcher logs app**

```plaintext
(105) exiting
ok: run: redis: (pid 47) 17s
ok: run: postgres: (pid 44) 17s
supervisor pid: 114 unicorn pid: 118
config/unicorn_launcher: line 71: kill: (118) - No such process
config/unicorn_launcher: line 15: kill: (118) - No such process
(114) exiting
ok: run: redis: (pid 47) 21s
ok: run: postgres: (pid 44) 21s
supervisor pid: 123 unicorn pid: 127
config/unicorn_launcher: line 71: kill: (127) - No such process
config/unicorn_launcher: line 15: kill: (127) - No such process
(123) exiting
ok: run: redis: (pid 47) 26s
ok: run: postgres: (pid 44) 26s
supervisor pid: 132 unicorn pid: 136

```

**curl localhost:2045**

```plaintext
<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx</center>
</body>
</html>

```

O Discourse está rodando dentro de um container LXC. Meu segundo fórum, também dentro de um container LXC, funciona perfeitamente após a atualização. Muito estranho.  
Alguma sugestão?

Atualização:  
Percebi que algum processo Ruby ainda está rodando e consumindo muita CPU:

```plaintext
/usr/local/bin/ruby /usr/local/bin/bundle exec config/unicorn_launcher -E production -c config/unicorn.conf.rb

```

Atualização 2:  
Resolvido alterando o container LXC de não privilegiado para privilegiado.

---

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [19 Agosto , 2023 11:11 UTC](https://meta.discourse.org/t/502-bad-gateway-after-upgrade-to-2-7-0beta2/177030/2 "2023-08-19T11:11:39Z")

</div>


