Hi guys, For the past few days I had a problem that DO server CPU spike for unknown reason. Here’s the $ top command. It seems the postmaster was busy. [image] I only had 509 users on DO 2GB memory.

Are you using any third-party plugins? Any unusual settings? I am not aware of any persistent out of memory issues on our Docker based DO installs. Do you have a swapfile? It shouldn’t matter except for upgrades, but given the problems you’re having, I would set a 2GB swapfile up quickly.

No. I use Mailgun. What I did after that was ./lanucher rebuild app. now It’s error 502 bad gateway.

Sorry, I totally misread your issue as postfix and not postmaster. :slight_smile:

I got his error from my log. After ran rebuild again. FAILED -------------------- RuntimeError: su postgres -c 'psql discourse -c "alter schema public owner to di scourse;"' failed with return # Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' exec failed with the params "su postgres -c 'psql $db_name -c \"alter schema pub lic owner to $db_user;\"'" 8c5331f9905f986b28e3c6fe278f3a4a876ccb3caea9c42341cba440295a1e71 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one root@forum:/var/discourse# ./launcher rebuild app Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container

Yep, you will need to read what is on the screen there, “scroll up and look for error”. Edit: check free disk space and free memory.

I have found out that every couple of days. The disk will be full. [image] It was /var/discourse/shared/standalone/log/rails/unicorn.stderr.log that got 20+ GB in 9 hours. I deleted the log but some context of the log was Failed to report error: EXECABORT Transaction discarded because of previous errors. 3 Job exception: MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.

[image] rsoutar: Please check Redis logs for details about the error. … and what did the Redis logs have to say?

Sorry, I have no idea where Redis log is.

It looks like there is something broken about your install. Did you follow our official install guide, to the letter? Did you deviate from any steps in the install in any way, however small?

I use a one-click installation from Digital Ocean. It’s been running fine since December '15. This started to occur for the past 2 weeks.

Ok, then try the following to free up some disk space: apt-get autoclean apt-get autoremove cd /var/discourse ./launcher cleanup See how much space that clears first. Something is causing massive numbers of errors in your logs, I presume? Hard to say without looking at them. You’ll need to poke around.

Server not response (DO SGP1)

Product Support Self-hosting

sam (Sam Saffron) May 17, 2016, 5:40am 17

Please try

cd /var/discourse
./launcher rebuild app
./launcher cleanup

We had a rather urgent fix related to tagging that could cause disks to fill up

Topic		Replies	Views
Discourse Bad Gateway after reboot Self-hosting	15	2402	July 2, 2020
Need support with discourse Update Self-hosting	4	244	October 9, 2024
Memory is running out and Discourse stops working Bug	74	15301	February 17, 2015
Discourse not using much RAM Self-hosting server-resources	30	2212	August 8, 2021
Error while doing discourse setup Self-hosting	11	3358	October 6, 2017

Server not response (DO SGP1)

Related topics