Hi! I’ve the same problem. I searched and found this post a few days ago, so according to your feedback @sam we decided to wait before doing any action in the forum, but after 4 days the convert process is killing our machine and pulling down the forum (it starts going slower and then starts throwing 502 for any request).
This is the top at this moment:
%CPU %MEM TIME+ COMMAND
51.5 3.0 0:07.73 ruby
27.9 7.2 3:42.61 postmaster
14.3 7.4 0:09.51 convert
13.6 7.3 1:52.68 postmaster
13.0 3.6 0:02.20 convert
11.3 3.8 0:02.41 convert
10.3 3.9 0:02.20 convert
8.3 6.3 0:17.23 convert
8.3 9.5 0:09.11 convert
8.3 1.0 0:10.39 convert
8.3 3.7 0:01.96 convert
7.3 0.7 0:09.91 convert
7.0 7.1 0:01.69 convert
4.0 3.3 0:05.59 convert
1.3 0.0 0:53.90 kswapd0
0.7 0.0 0:00.40 kworker/u4:1ert
1.3 0.0 0:53.90 kswapd0
0.7 0.0 0:00.40 kworker/u4:1
Our setup is a one-click DigitalOcean image and the problem started last Friday 2019-02-22 10:00 after upgrading the forum to the last version from 2.2.0beta1 +20 to 2.3.0.beta2.
Taken actions:
- Waiting for the process to end
- Clearing old containers + images and rebuilding
- Restarting 3-4 times the machine
- Crying
Any idea?
Thank you very much and sorry for bothering you.