# Imagens de perfil do usuário carregando lentamente, falha ao carregar

**URL:** https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595
**Category:** Support
**Created:** [3 Janeiro , 2019 15:54 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595 "2019-01-03T15:54:09Z")
**Posts on this page:** 12
**Page:** 2

<div class="post-metadata">

### Author: ![AlexMl](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@AlexMl](https://meta.discourse.org/u/AlexMl)
#### Post date: [4 Janeiro , 2019 17:21 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/21 "2019-01-04T17:21:55Z")

</div>

I usually update Discourse forum via command line.  
Can you, please, specify, when avatars and images resizing tasks will be executed - during run of command `sudo``/var/discourse/launcher``bootstrap app` or after that - when I executed - `sudo``/var/discourse/launcher``start app` and app is running ?

Will this resize task be executed only during update to version 2.2.0.beta7, or it will be executed during updates to all next Discourse releases ?

---

<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: [4 Janeiro , 2019 17:25 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/22 "2019-01-04T17:25:04Z")

</div>

After the `/launcher start app` it will run in the background while the app is running.

It’s a one time thing, however we trigger those rebakes whenever something big changes, like when we moved the markdown processor library.

Those are rare events, and we don’t have another one planned.

---

<div class="post-metadata">

### Author: ![bts](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bts/32/184556_2.png) [@bts](https://meta.discourse.org/u/bts)
#### Post date: [4 Janeiro , 2019 17:38 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/23 "2019-01-04T17:38:52Z")

</div>

That sounds good! For any future things like this I wonder if it could be useful to prompt admins w/ a suggestion to beef up server resources temporarily before running.

Not sure what impact this would have, but for a big forum like @bartv’s could temporarily switching to e.g. a Digital Ocean droplet w/ tons more RAM / CPUs make this update process substantially faster?

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [6 Janeiro , 2019 22:46 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/24 "2019-01-06T22:46:43Z")

</div>

Hi,  
After three days (v2.2.0.beta7 +13) there are a lot of missed user profiles (say 5-10% of 3000 users). How to check if it’s still processing something or should I apologize and ask users to upload profile image once again.

Thanks

---

<div class="post-metadata">

### Author: ![bartv](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/bartv/32/130052_2.png) [@bartv](https://meta.discourse.org/u/bartv)
#### Post date: [8 Janeiro , 2019 12:01 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/26 "2019-01-08T12:01:44Z")

</div>

> [@sam](#):
>
> If you must you can run a 1 liner to disable the rebake

Yeah I feel this is the best way for me, what’s the code?

---

<div class="post-metadata">

### Author: ![AlexMl](https://avatars.discourse-cdn.com/v4/letter/a/c67d28/32.png) [@AlexMl](https://meta.discourse.org/u/AlexMl)
#### Post date: [8 Janeiro , 2019 12:11 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/27 "2019-01-08T12:11:38Z")

</div>

Can you, please, tell me what triggers start of images rebake process ?  
I started 1 instance with the latest version of Discourse and during 40 minutes convert command was not started.  
ps aux command doesn’t show convert process.

As I understand convert process should do rebake of images.

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [10 Janeiro , 2019 06:00 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/28 "2019-01-10T06:00:13Z")

</div>

Something along the lines of:

```plaintext
./launcher enter app
Post.where(baked_version: nil).update_all(baked_version: 2)

```

But this is not something I am going to support and I **strongly** recommend you test this on your testing instance first.

Instead I would just reduce `rebake old posts count` to a number you find acceptable, at `1` you will not notice any impact.

---

<div class="post-metadata">

### Author: ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [10 Janeiro , 2019 13:08 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/29 "2019-01-10T13:08:27Z")

</div>

Another reason not to do this is that some future rebake you will want to take advantage of. At some point you’ll likely need to throw more resources to your server.

---

<div class="post-metadata">

### Author: ![Dmitry\_Krasnoperov](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/dmitry_krasnoperov/32/65079_2.png) [@Dmitry\_Krasnoperov](https://meta.discourse.org/u/Dmitry_Krasnoperov)
#### Post date: [2 Março , 2019 23:51 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/30 "2019-03-02T23:51:52Z")

</div>

### [v2.3.0.beta3 +1](https://github.com/discourse/discourse/compare/fd9671f7fe0dec435a4152eb95fd4e2f3e4f77d6...tests-passed)

a lot of broken profile images after update to it

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3 Março , 2019 20:27 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/31 "2019-03-03T20:27:22Z")

</div>

Rebuild your container, it should stop

---

<div class="post-metadata">

### Author: ![Overgrow](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/overgrow/32/478189_2.png) [@Overgrow](https://meta.discourse.org/u/Overgrow)
#### Post date: [23 Fevereiro , 2020 22:41 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/32 "2020-02-23T22:41:33Z")

</div>

> [@sam](#):
>
> Em vez disso, eu apenas reduziria o `rebake old posts count` para um número que você considere aceitável; em `1`, você não notará nenhum impacto.

Posso perguntar se a regeneração de avatares depende da rebake de todas as postagens? O motivo é que gostaria de deixar `rebake old posts count` no padrão, mas acelerar a regeneração de avatares. Obrigado antecipadamente!

> [@sam](#):
>
> Esse problema deve se corrigir automaticamente após um tempo; precisávamos reconstruir todos os avatares redimensionados, então pode levar um tempo para acontecer.

Qual processo é responsável por isso?

---

<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: [30 Janeiro , 2024 18:31 UTC](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595/33 "2024-01-30T18:31:02Z")

</div>



[Previous page](https://meta.discourse.org/t/user-profile-images-loading-slowly-failing-to-load/105595.md?page=1)
