Hi, I just received an email from discourse, proposing to upgrade from 2.7.0.beta1 to 2.7.0.beta2. I went to the admin page and clicked on upgrade, and it seems like something has failed. As a result, it is not possible to access my dicourse instance anymore (Error 500). I include here the final …

My apologies @geoff777 - without much thinking I reclassified your “like” comment (my intent was to keep the number of my posts small, thus lowering the chance of miscommunication) I believe that I have enough space: System information as of Fri Jan 22 20:56:56 UTC 2021 System load: 0.02 …

Thanks. You can check on your forum’s dashboard that you have successfullu upgraded. I hope it worked.

Your wish / hope @geoff777 did not help. I tried to login - and the discourse server was not responding. I decided to run discourse-doctor from the DO console, launched from PuTTY tool (I am running on a Windows 10 machine), - and my console stopped at the same place. Note this beginning of this r…

Both times you got that PuTTY Fatal Error? That seems like a putty problem, though I can’t imagine why.

Yes, @pfaffman I do get that same error. If the execution of the ./discourse-doctor causes some catastrophic failure is it not possible that this failure results with the PuTTY fatal error - at least for my own (remote) view of his failure? It does not seem very likely, but I will create a support …

I guess I world try the digital ocean console next (actually, I would use a terminal in Ubuntu, but that’s not what I’d recommend to you).

Since yesterday, I observed a lot of weird behavior. Before sharing them here, please do let me know if continuing this thread is useful for anyone (the alternative is that I am just stepping on my own d… and this is all a waste of everyone’s time). I found that: resetting the root password (from …

Could you be running out of RAM and then having oom killer knock off some random processes such as sshd, thus disconnecting you and causing problems? There should be something in dmesg output, /var/log/messages or the journalctl output if oom killer is running.

I doubt that running out of RAM is my problem, it’s rather me stubbornly using PuTTY console instead of the DO console . So, I am going to switch to @pfaffman ’s suggestion above , particularly since my discovery that PuTTY console gets disconnected even when I am using it for something completely dif…

Ram could be it. Do you have swap?

2.7.0.beta2 업그레이드 실패

제품 지원 자체 호스팅

pfaffman (Jay Pfaffman) 1월 23, 2021, 3:14오후 19

다음에는 Digital Ocean 콘솔을 시도해 볼 것 같습니다 (사실 저는 Ubuntu에서 터미널을 사용하지만, 그건 여러분에게 추천하지 않는 방법입니다).

글		댓글	조회수
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2397	11월 26, 2021
Latest site upgrade not working Self-hosting	10	1955	2월 22, 2022
An upgrade knocked my site offline; how long until it's restored? Self-hosting	15	660	7월 10, 2025
2.6.0 beta 3 update failed on disk and/or memory space Self-hosting server-resources	28	3016	9월 26, 2020
3.1.x to 3.2.0 upgrade hangs/fails on 1GB instance Self-hosting	34	2140	2월 23, 2024

2.7.0.beta2 업그레이드 실패

Related topics