I tried to do a backup and the backup failed. I tried to do an upgrade. [upgrade screen] At first, the upgrade screen had everything disabled. I rebooted and then I was able to select the docker_manager upgrade. That failed with: rake aborted! NoMethodError: undefined method `path' for nil:Ni…

What does free tell you? Personally, if a backup failed, I would not try an update. A backup - including having a copy downloaded - is for me a prerequisite. This may not be a helpful comment at this time, but I think it has to be said.

In your other post you give a little more info about the rake aborted: [Bild] Update Problem rake aborted! NoMethodError: undefined method `path' for nil:NilClass /var/www/discourse/lib/discourse_ip_info.rb:48:in `mmdb_download' /var/www/discourse/lib/tasks/assets.rake:281:in `block (3 levels) i…

That’s not the problem. That looks like there isn’t a key to download max mind db. The problem is above.

If the problem is a failure to spawn, then not only do we care about RAM and swap usage, but we care about the kernel configuration. If this appears in the logs # WARNING overcommit_memory is set to 0! Background save may fail under low memory condition. To fix this issue add 'vm.overcommit_memory…

My installation of Discourse is very generic. After a reboot I got a clean backup. So, ultimately I decided to do a from scratch installation. The installation failed with the same errors I posted above. I have been running Discourse with 6GB of memory in a LXD container the past four years wit…

I have maybe 40 users and 150 posts. The system uses 1.8GB of memory and I gave it 6GB of memory. How much memory is required to have a rebuild work? That’s always been adequate in the past.

Can you share your app.yml file? I’m afraid you have an invalid API key for MaxMind.

Here’s my app.yml. ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR AL…

When I did a new build, I tried a new Maxmind key and I got the same error.

Update von 3.0.0.beta16 auf 3.1.0.beta2

Unterstützung Installation

Falco (Falco) 10. März 2023 um 15:15 14

Kommentieren Sie die Zeile mit DISCOURSE_MAXMIND_LICENSE_KEY aus oder löschen Sie sie und bauen Sie neu.

Rebuild is failing with a wrong MaxMindDB API key

Thema		Antworten	Aufrufe
Setting DISCOURSE_MAXMIND_LICENSE_KEY breaks docker image/container build Self-hosting maxmind	22	1389	16. Mai 2024
Upgrade discourse fails from 3.3.0 beta1 to beta2 via admin panel Self-hosting	4	447	14. Juni 2024
ERROR: You are running an old version of the Discourse image Self-hosting	12	1628	3. Juni 2021
Discourse down after failed web update, rebuild & doctor not helping Self-hosting	8	678	16. April 2023
Rebuilding always fails when the MAXMIND daily limit is exhausted Bug maxmind , dev-ops , fixed	63	1161	5. August 2024

Update von 3.0.0.beta16 auf 3.1.0.beta2

Verwandte Themen