Today after several months of not upgrading, I upgraded docker manager successfully and then tried to upgrade docker, which failed during bundling. I tried to rebuild the container using ./launcher rebuild app but it failed on exactly the same place. Now when I start the app, I get this error on th…

I didn’t abort the upgrade. Have seen this same error 3 times now.

Same thing again just now, with slightly more info: [176] 23 Sep 16:33:25.034 * Background saving started by pid 967 [967] 23 Sep 16:33:25.326 * DB saved on disk [967] 23 Sep 16:33:25.327 * RDB: 4 MB of memory used by copy-on-write [176] 23 Sep 16:33:25.335 * Background saving terminated with succe…

The error seems to be related to message bus killing another process. I’m not so familiar with that gem but maybe @sam can jump in and give some advice?

What’s your server environment? This looks like somehow some strange supervisor tool kills processes that run too long or cause too high CPU loads…

$ cat /etc/issue Ubuntu 14.04.1 LTS Running on Rackspace Cloud.

They don’t seem to enforce something like that by default - can you send me a ps auxf output (if you like, via PM)?

Are you running out of memory? Do you have at least 1GB RAM + 1GB swap, or 2GB RAM?

Getting SIGTERM is a real curiosity. Ctrl-C sends SIGINT, and the OOM killer sends SIGKILL. SIGTERM is the default signal sent by the kill command, if you don’t specify a different signal. Looking at the message_bus code, I’m about 99% sure the problem is something to do with the communication be…

Yeah, message bus has an optional default on keepalive test, when enabled it ships messages to itself on a regular basis, if it stops hearing echoes it knows that it is messed up internally, it can not recover, so it kills itself which is the only reasonable thing it can do You can not kill threads…

Sounds to me like redis has gone belly up, my guess, not enough memory

Upgrade failed due to process terminating

Product Support Self-hosting

shadowhand (Woody Gilk) 24.Сентябрь.2015 15:43:06 20

After upgrading to the latest discourse_docker and updating OS packages, I was able to run rebuild app without issues.

Consider the issue resolved.

Тема		Ответов	Просм.
Down after Docker Update Self-hosting server-resources	6	746	06.11.2020
Docker Manager: FAILED TO UPGRADE Self-hosting docker-manager , server-resources	6	1422	04.11.2020
"Waiting for unicorn to reload", then update stops Product Support	30	5098	20.06.2021
Automatic upgrade from 2.6.0.beta5 to 2.7.0.beta3 failed Self-hosting	8	1575	26.04.2021
Error while updating through launcher rebuild Self-hosting	2	654	16.04.2024

Upgrade failed due to process terminating

Связанные темы