I see these errors - how can i find the full error log for the installation and post it here for diagnose and maybe fix? I, [2024-02-07T04:52:47.464805 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' warning "@discourse/lint-configs > e…

[이미지] Jay Pfaffman: Warnings: overcommit_memory and Transparent Huge Pages . (I’m not clear if that post describes your to change this settings, so you night need to look elsewhere) Eww - that linked post with the accepted solution is exactly wrong, these days! It is wise to fix those settings…

Try the DIscourse Doctor: [이미지] Announcing Discourse Doctor Development Following the example from Discourse-doctor woman_health_worker , I’ve created discourse-doctor, now included in discourse_docker. If you run ./discourse-doctor, you’ll see something l…

I did try to run the doctor and yet recieve various errors eg: Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake themes:update assets:precompile' failed with return #<Process::Status: pid 3341 exit 1> Location of failure: /usr/local/lib/ruby/gems/3.2.0/gems/pups-1.2.1/lib/…

So discourse doctor restarted your old container? You don’t include the actual error, but I bet that it was “exit code 137”. It that’s the case you case try making the changes this describes Warnings: overcommit_memory and Transparent Huge Pages . (I’m not clear if that post describes your to chang…

I actually allowed overcommitting. My machine is a EC2 with 2 GB ram and 4 GB swap file [2024-02-07 145234]

[이미지] Ed S: that linked post with the accepted solution is exactly wrong, these days! Thanks for noticing that! I wanted to link to our earlier constatation but couldn’t find it on my phone in the middle of the night…

I have successfully root@forum:/home/ubuntu# cat /sys/kernel/mm/transparent_hugepage/enabled always madvise [never] i created a service sudo -s /etc/systemd/system/disable-thp.service [Unit] Description=Disable Transparent Huge Pages (THP) [Service] Type=simple ExecStart=/bin/sh -c 'echo neve…

Here is the full log, since i cannot post in one body message, i have to explit it in two root@forum:/var/discourse# ./launcher rebuild app x86_64 arch detected. Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 600 app app 2.0.2…

part two brotli -f --quality=11 /var/www/discourse/public/assets/break_string-cc617154cd957804f2f6a1f3bc68258c9cdca3d4b9a322bf777d145fed04790e.js --output=/var/www/discourse/public/assets/break_string-cc617154cd957804f2f6a1f3bc68258c9cdca3d4b9a322bf777d145fed04790e.js.br Done 'break_string-cc617…

part 3 Done 'workbox-9b5674ca0ecb89bae1fa6f4b09a18f12/workbox-sw.js' : 0.01 secs Done 'Done compressing all JS files' : 15.84 secs Start compiling CSS: 2024-02-07 09:57:38 UTC ------------- Compiling CSS for default 2024-02-07 09:57:38 UTC precompile target: desktop precompile target: mobile …

[이미지] ElComputer: Done compiling CSS: 2024-02-07 09:57:45 UTC /var/www/discourse/lib/discourse_ip_info.rb:48:in `mmdb_download': undefined method `path' for nil:NilClass (NoMethodError) filename = File.basename(gz_file.path) ^^^^^ from /var/www/di…

설치 후 오류 발생 - Discourse-doctor - 항생제가 작동하지 않음

제품 지원 자체 호스팅

Ed_S (Ed S) 2월 7, 2024, 9:11오전 5

그 링크된 게시물의 채택된 해결책은 요즘 기준으로 완전히 틀렸습니다. 해당 설정을 수정하는 것이 현명합니다. 최근 사례 중 하나에 대해서는 여기를 참고하세요.

글		댓글	조회수
Unable to boostrap Discourse since last upgrade Self-hosting	4	850	1월 22, 2023
Failed to Bootstrap, due to discourse-alt-logo theme component Self-hosting	7	1472	6월 30, 2021
Discourse update error Self-hosting	35	2618	1월 30, 2023
I can't start Discourse Self-hosting	11	782	9월 23, 2024
Latest site upgrade not working Self-hosting	10	1955	2월 22, 2022

설치 후 오류 발생 - Discourse-doctor - 항생제가 작동하지 않음

Related topics