What are the hardware specs? Is it heavily memory constrained, or are the disks slow (not SSD)?
It’s not a problem to update via SSH command line if that works better, but it shouldn’t be required.
I’m not sure what the criteria is for constrained, the site has been relatively speedy (with no cloudflare, CDN or other tricks). It’s a KVM VM with 2GB. Here is an output from free:
total used free shared buff/cache available Mem: 2047876 1263844 121092 280544 662940 325164 Swap: 2097148 549032 1548116
There is nothing else running on this but Discourse. However, the disks are definitely slow, non-SSD, in RAID-10, and shared with a few other VMs. I ran iotop as the nightly backup was going and didn’t see anything above 50MBps.
The exported non-compressed backup .sql is ~600MB, average daily engaged this past month <50, and daily pageviews are <6000 per day.
I do see one major difference in the output between what you posted originally and what @danekhollas and I are getting. In our output, it takes Unicorn significantly longer to reload (based on the number of dots), however it’s always been that way since that was added to the upgrade process.
The swap usage is fairly high there. This implies you have a busy instance. Also, slow disks are going to be quite painful in several dimensions.
In my case I have SSD and plenty RAM, but CPU is slow (1.7 GHz) and I usually have only around 7Gb free space on HDD. I noticed that Discourse seems to want at least 5Gb free during upgrade, could this be the issue?
Note that this problem started happening at a specific point in time (probably around this topic got started but I am not sure) and since then I was not able to upgrade via UI at all, which lead me to believe that something must have changed…
I gave @tgxworld access to my instance in case it is helpful.
Note tgx is out for a bit, he may have a chance to have a quick look next week.
Just to update since my last post ~4 months ago. I took the advice given and moved over to a whole new machine, with a significant RAM+CPU increase and switch to full SSD. This problem has not occurred again.
I am also facing this issue in the last several times I have tried to upgrade using the web UI.
My instance is hosted on a VM that is configurable to higher specs if I request it, but it’s not clear to me what are the recommended specs for running a typical Discourse instance.
Can someone provide these specs?
The above question is assuming the upgrade failure only happens because of lack of resources on the host.
도움 필요합니다. docker_manager 업그레이드 중 오류가 발생하고 있습니다.
Sorry, there was an error upgrading Discourse. Please check the logs below.
같은 오류입니다.
Spinning up 1 Unicorn worker(s) that were stopped initially
현재 Remote Version: 2c89085입니다.
Reset Upgrade 옵션이 있는데, 이걸 실행해야 할까요? 도움을 부탁드립니다. 미리 감사드립니다!!
웹 UI를 통해 v2.4.0.beta10 +1(“docker_manager 2c89085 Up to date”) 업그레이드 후 이 문제를 처음 경험했다는 보고입니다. 로그가 필요하신 분은 첨부 파일을 참고해 주세요. Discourse2.4beta10error.txt (10.2 KB)
./launcher rebuild app 명령어는 정상적으로 작동했습니다.
이 문제는 집에서 자가 호스팅으로 운영 중인 테스트 시스템에서 발생했습니다. 하드웨어 사양은 Intel Atom D525 1.8GHz 2코어 / 4스레드, 4GB RAM, SSD이며 Lubuntu 16.04 LTS를 사용 중입니다. Docker/Discourse만 실행 중이며 다른 작업은 없습니다.
2.7.4 업데이트를 시도하던 중 이 문제가 갑자기 발생했습니다.
명령줄을 통해 다시 빌드를 시도했지만, discourse-doctor를 실행한 후 다음과 같은 오류가 발생했습니다.
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' failed with return #<Process::Status: pid 4115 exit 1>
Location of failure: /pups/lib/pups/exec_command.rb:112:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"assets_precompile", "cmd"=>["su discourse -c 'bundle exec rake themes:update assets:precompile'"]}
5b36313b3f2b9e2173d52f8a7519d6aba3c4a975182d80150776d9c83659c351
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
==================== END REBUILD LOG ====================
Failed to rebuild app.
새로운 버전 2.7.4가 표시되는 것이 이상하며, 테마 컴포넌트를 업데이트하려고 했을 때 "about.json contains invalid values: Maximum discourse version is invalid"라는 오류가 발생했습니다.
discourse를 다시 정상적인 상태로 되돌리는 방법에 대해 조언을 주실 분이 있을까요?