Hi, I’m not sure what this could be, and I think running Discourse on 1GB of memory plus 1GB of swap is probably below minimum spec at this point so I’d understand if this is outright unsupported, but I’m having a weird issue where my site goes down at exactly the same time every day (at around 2:4…

I don’t think the nginx inside the container has diverged from stock at all, I use the provided launcher script for all the docker stuff. This is what the host nginx config for the site looks like if you’re curious, but I don’t think this is the problem: root@selectbutton:/etc/nginx/sites-enabled#…

I’m on a server with 2 GB of ram and I’m seeing the same behavior as of a few days ago. Seems to happen around backup time.

[Bild] axfelix: I don’t think the nginx inside the container has diverged from stock at all, I use the provided launcher script for all the docker stuff. Well you would be using this: templates/web.ratelimited.template.yml master params: reqs_per_second: 12 burst_per…

Ah, OK, good to know. So I should add that to the host nginx or the container nginx (which is to say, that to: block in the app.yml?)

You need to run a replace command in the internal NGINX. After making the changes, look at the actual file on disk to confirm that you got what you wanted. A trick I use is: ./launcher enter app cd /etc/nginx/conf.d/ edit the discourse.conf file sv restart nginx see that my desired effect was ac…

Yeah, the strict periodicity (in the absence of scheduled backups) is a very confusing aspect to this. Seems like a heck of a big clue, if you can figure out what’s running at that exact time, I think you’ll be 90% done.

Same problem for me :frowning: I’m tired of rebuild after every crash.

Check your /sidekiq and see if anything is running at that time. What also might help is to start psql to take a look at what is going on in your database at that time. SELECT pid, age(query_start, clock_timestamp()), usename, query FROM pg_stat_activity;

[Bild] RGJ: Check your /sidekiq and see if anything is running at that time. Sidekiq is idle :thinking:

Site goes down at the same time every day in memory-constrained environment

Support

axfelix (Alex Garnett) 19. Dezember 2017 um 00:38 15

OK, will test if it goes down again tomorrow despite increasing swap. Any other ideas if this turns out not to be it? The timeliness still makes me quite skeptical.

Thema		Antworten	Aufrufe
429 too many requests good or bad ? (please help) Self-hosting	14	291	25. August 2026
Is 1GB RAM enough for both WordPress and Discourse? Self-hosting server-resources	21	4967	3. März 2017
Bursts of 502 Service Unavailable, pointers to debug Self-hosting	15	1796	18. Februar 2018
Troubleshooting a 429 (rate limit) Self-hosting	19	6184	10. Oktober 2018
Discourse overloaded real traffic or DDOS? 100% CPU usage despite of decent traffic and high specs server Self-hosting server-resources	18	2625	25. September 2021

Site goes down at the same time every day in memory-constrained environment

Verwandte Themen