I get an AWS cloud watch alert at 9:09pm ET, along with some friends who text me “hey is discourse down?” I can’t ssh into the AWS lightsail instance, and all the metrics are hung/not reporting. Eventually I give up and stop/restart the lightsail instance. Service recovered. I check the logs pos…

What are the server specs? Sounds like it’s running out of resources? Most likely CPU. Perhaps there is some daily task running at that time?

Its a 1 vCPU, 1GB RAM, 40 GB SSD lightsail instance. Storage is about 60% consumed, and when I do cleanups it drops quite a bit. AWS shows I am out of burstable CPU credits, which is only odd because the other metrics don’t support that. It’s a pretty small community (20-30 active participants) s…

1GB with swap is the absolute minimum to run discourse. How long has this instance been up? How big is the database?

I’ll check the db size, not expecting it to be large (backups are all about 57 MB). Uptime of the instance is not quite ten hours now since recovery required stopping and restarting the virtual server- I could not get a shell or console connection. Been running fine on this instance type since I b…

This sounds like what happens when AWS moves your VM from one host to another and leaves it in a weird state because of it. Usually a reboot solves it.

Overall db size is 423MB. Largest tables are Posts 66MB Post_timings 60MB

Second similar “high load” failure occurred. Going to guess resource contention. Has anyone tried to use the Lightsail snapshot to snapshot the instance, and restore it to a larger instance as an upgrade method?

You can try rebooting the AWS instance, that can fix a lot of issues.

I’ve moved using Lightsail snapshot from a 1 CPU, 1GB RAM 40GB SSD to a 2 CPU, 4GB RAM 80 GB SSD. Aside from having to detach the public IP and reattach, which was straightforward enough, my remaining concerns is “what have I missed”? Is there anything (backups, email, S3 bucket config, etc) that …

I’m thinking based on this link I could bump the db_shared_buffer to at least 1GB. Current app.yml says 128MB, also indicates auto adjust at bootstrap. [이미지] Configure Discourse Docker on servers with more RAM and CPU Self-Hosting When you install Discourse o…

또 다른 디스커스 미스터리

제품 지원 자체 호스팅

fuse (Geoff Hughes) 10월 16, 2022, 6:49오후 11

이 링크를 참고하면 db_shared_buffer를 최소 1GB까지 늘릴 수 있을 것 같습니다.
현재 app.yml에는 128MB로 설정되어 있으며, 부팅 시 자동으로 조정된다는 내용도 명시되어 있습니다.

글		댓글	조회수
Problem installing Discourse on AWS EC2 instance Self-hosting server-resources	3	561	11월 21, 2023
Connection timed out while connecting to upstream on AWS Self-hosting hosting	12	4012	6월 28, 2016
Suddenly my server got crashed out of nowhere Self-hosting	8	534	5월 15, 2023
Discourse unavailable with high load average Product Support	19	2656	9월 5, 2018
Due to extreme load, this is temporarily being shown to everyone... when it's not really the case Self-hosting server-resources	19	1996	7월 21, 2023

또 다른 디스커스 미스터리

Related topics