I’ve got a 2-container install on a DO 8GB droplet that is behaving very strangely. There is a postmaster (EDIT: now there are two of them) processing eating 100% CPU. Sidekiq is running, but the Dashboard complains that it’s not checking for updates. There are some logs like PG::ConnectionBad…

The postgresql connection limit needs to be increased. That will cause the database as a whole to use more memory, but based on the free output you’ve got plenty that could be used if required. I’d double the current value, and review errors and resource consumption.

Uh. Where is that changed? You mean this? db_work_mem: "80MB" I did that, but I’m still getting a 502 error on the admin dashboard. The other issue is that this site is using cloudflare with no caching (I’m told). I have included the cloudflare template, but I still suspect something is wrong …

[이미지] pfaffman: Where is that changed? It’s the max_connections parameter in postgresql.conf. I don’t see a tunable for that in discourse_docker, so I suspect you’ll need to play games with a pups exec stanza to make the edit. As for Cloudflare, all the cloudflare template does it make it s…

[이미지] mpalmer: It’s the max_connections parameter in postgresql.conf. I don’t see a tunable for that in discourse_docker, so I suspect you’ll need to play games with a pups exec stanza to make the edit. Not one for playing games when they’re not necessary, I went into the data container, edi…

Sorry to bump an old thread. @pfaffman Did this solve the postmasters gone wild high CPU usage issue for you? I modified max connections directly in postgresql.conf (/var/discourse/shared/standalone/postgres_data/postgresql.conf) and used ./launcher rebuild app. Haven’t noticed a difference though…

The problem seems to have gone away I tried giving postgres more memory and less. Adding swap seemed to have helped (hence trying giving pg less memory) . One thing that I did that might have helped was to backup and restore the database. Or it could be that it did nothing. I don’t have a silver b…

It now started happening for me, too, after installing the update to 2.5.0.beta5. One by one I get more postmaster processes that use as much CPU as they can get and it takes them sometimes a few minutes before they complete. Slowly this eats up all AWS credits for the server and makes the whole for…

We updated our forum to 2.5.0.beta5 yesterday, and since then it has been slow and unresponsive. There are a few postmaster jobs right at the top that eat 90-100% of the CPU. It’s causing many parts of the forum to timeout and return a 502 for the users. The jobs come and go, but while they are act…

Wouldn’t this be the finalization steps of the Postgres 12 upgrade? I think there’s some internal cleanup it needs to do after migrating from PG10 to PG12? Does the situation persist for a day or more?

It has been 13 hours thus far. Also, to confirm: I did go from PG 10 to 12 (I know you can optionally stay on 10, so just want to clarify). I’m not sure if this is relevant, but going to a user’s summary consistently spikes CPU usage to 90%+ and it always ends in a 502. The other sections of the p…

Primary Postgres database process (postmaster) eating all CPU

지원 자체 호스팅

markersocial 5월 28, 2020, 6:00오전 13

Just a heads up, I had the same issue and it was fixed by doing this:

글		댓글	조회수
Slow Sidekiq + Postmaster using 95%+ CPU (32 cores) after Postgresql Version Upgrade Self-hosting server-resources	22	3459	5월 29, 2020
Discourse Crash due to PSQL connection issue Self-hosting	9	535	3월 17, 2024
Unusually high CPU usage Self-hosting	31	1242	2월 18, 2026
Too many connections to DB, how to optimize Support	17	4001	7월 27, 2017
Discourse Bad Gateway after reboot Self-hosting	15	2269	7월 2, 2020

Primary Postgres database process (postmaster) eating all CPU

Related topics