Hi, The one-click browser upgrade from 2.6.0.beta5 to 2.7.0.beta3 failed with the following error: 89591216.5834941 Compressing: browser-update-92cd9b3599f62ca785b6cbf3d8d3afb080d6cd463034e2fccefd5455b0f5fff6.js uglifyjs '/var/www/discourse/public/assets/_browser-update-92cd9b3599f62ca785b6cbf3d8d…

Running ./launcher rebuild app fixed the issue, but I’m still curious about what the error was about.

I experienced the same issue, the automated update failed "base='/var/www/discourse/public/assets',root='/assets',url='/assets/browser-update-92cd9b3599f62ca785b6cbf3d8d3afb080d6cd463034e2fccefd5455b0f5fff6.js.map'" Parse error at _browser-update-92cd9b3599f62ca785b6cbf3d8d3afb080d6cd463034e2fccefd…

Success! I managed to get my site up and running by disabling all the plugins # - git clone https://github.com/discourse/docker_manager.git # - git clone https://github.com/discourse/discourse-tagging.git # - git clone https://github.com/discourse/discourse-solved.git # …

[immagine] glynhudson: The error seems to be createdb: error: database creation failed: ERROR: database "discourse" already exists No that is not the reason. The problem is [immagine] glynhudson: undler::GemNotFound: Your bundle is locked to msgpack (1.4.1), but that version could not…

Thanks, that’s good to hear the issue has been fixed. So I should be able to re-enable my plugins and rebuild again? Presumably I need to wait for a new docker hub discourse base image to be released that includes this fix which could be a few days?

[immagine] glynhudson: So I should be able to re-enable my plugins and rebuild again? Yes. The plugins thing was a complete red herring. [immagine] glynhudson: Presumably I need to wait for a new docker hub discourse base image to be released that includes this fix which could be a few d…

Thanks, all sorted now. Re-enabled plugins, rebuild and now everything is back up and running the way it was. Thanks for your help :+1:

I got this issue too, from 2.7.0 beta5 to 2.7.0 beta7 in Ubuntu 20.4 with almost similar error message above. The message: Spinning up 1 Unicorn worker(s) that were stopped initially Failed to cd /var/discourse git pull ./launcher rebuild app My solution: Restore my droplet/back up Update the …

Aggiornamento automatico da 2.6.0.beta5 a 2.7.0.beta3 fallito

Supporto Installazione

Falco (Falco) 1 Febbraio 2021, 1:46pm 6

No, non è quello il motivo.

Il problema è

L’autore di msgpack lo ha rimosso, quindi @tgxworld ha risolto questo problema tramite

https://github.com/discourse/discourse/commit/7e4dad3c565a6839f4a0e0e8ef1e4c86e639f3f7

6 Mi Piace

Argomento		Risposte	Visualizzazioni
Latest site upgrade not working Self-hosting	11	1767	Febbraio 22, 2022
Upgrade to 2.7.0.beta8 Self-hosting	9	1315	Giugno 4, 2021
Production install on 3.4.0.beta2-dev failing to update to 3.4.0.beta2 Self-hosting	12	271	Dicembre 2, 2024
Discourse offline after failed upgrade "bootstrap failed with exit code 5" Self-hosting	24	1403	Febbraio 22, 2024
Bootstrap failure during most recent upgrade Self-hosting	7	592	Febbraio 3, 2023

Aggiornamento automatico da 2.6.0.beta5 a 2.7.0.beta3 fallito

Argomenti correlati