Our server was showing some users 500 errors, so I went to update Discourse to the latest version (I hadn’t updated in a month or so). The update failed. It stopped for about 20 or 30 minutes when installing a Redis gem, so I tried SSH’ing in and pulling master from discourse-docker. After doing t…

Nothing we can see in those logs. Please check disk space, and if possible paste a log from a rebuild.

We have almost 10 gigs free. Is there some sort of swap file that would take up more than that? I could go in and manually delete one or more of the backups (we keep 2 or 3 days backups, but we probably don’t need to since we also send them to s3). Do you know where these backups would be located?

[image] ossia: Do you know where these backups would be located? By default at /var/discourse/shared/standalone/backups/default/

Thanks. The backups are only a few hundred megabytes. I am trying to run ./launcher rebuild app again and It hangs on this: /var/discourse# ./launcher rebuild app Ensuring launcher is up to date Fetching origin Launcher is up-to-date Stopping old container + /usr/bin/docker stop -t 10 app Is this…

[image] ossia: Is this normal? How long does this usually take? Less than 10 seconds, if you have a long running transation on the DB this can be problematic (we had this a few commits ago), you can log and try to find the problematic PID and kill it.

I ran top and saw this: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 1428 root 20 0 4236 364 292 R 98.1 0.0 13:36.66 runsv 1429 root …

Well, there’s ./launcher start app, which will just fire up the already-built container if it isn’t already running, but your container appears somewhat hosed, based on the consumption of a full core by each of two runsv processes. I’d jump straight into strace -p 1428 -f -s 10000, but I’m weird li…

I restarted the droplet and now runsv isn’t running anymore, but it’s still not up and we’re still having the original problem with our logs.

perl is chewing 100% cpu on this machine … upgraded docker and trying to reboot the box, then will have a look at cpu to see that whatever perl script you were running is properly not running.

Emergency help - freeCodeCamp Discourse down

Support Self-hosting

sam (Sam Saffron) February 22, 2017, 2:23am 15

cool … old image is nuked, did a cleanup … it is bootstrapping just fine

1 Like

Topic		Replies	Views
Need support with discourse Update Self-hosting	4	129	October 9, 2024
Forum Full Crash (Test Pressing) Self-hosting	9	189	September 4, 2024
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	17	1965	November 26, 2021
Rebuild taking ~3hours Self-hosting server-resources	35	1714	March 16, 2025
PostgreSQL Stuck During Rebuilding Self-hosting	52	1114	October 4, 2024

Emergency help - freeCodeCamp Discourse down

Related topics